typescript-advanced-types
Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications. Use when implementing complex type logic, creating reusable type utilities, or ensuring compile-time type safety in TypeScript projects.
74
67%
Does it follow best practices?
Impact
82%
1.02xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/javascript-typescript/skills/typescript-advanced-types/SKILL.mdQuality
Discovery
92%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly articulates specific capabilities (generics, conditional types, mapped types, etc.) and includes an explicit 'Use when' clause with relevant trigger scenarios. The trigger terms are natural and comprehensive for the domain. The only minor weakness is potential overlap with general TypeScript skills, though the focus on advanced type system features provides reasonable differentiation.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete capabilities: generics, conditional types, mapped types, template literals, utility types, and specific actions like 'building type-safe applications', 'creating reusable type utilities', and 'ensuring compile-time type safety'. | 3 / 3 |
Completeness | Clearly answers both 'what' (master TypeScript's advanced type system including generics, conditional types, etc.) and 'when' (explicit 'Use when implementing complex type logic, creating reusable type utilities, or ensuring compile-time type safety in TypeScript projects'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'TypeScript', 'generics', 'conditional types', 'mapped types', 'template literals', 'utility types', 'type-safe', 'type logic', 'compile-time type safety'. These cover the main terms a developer would use when seeking help with advanced TypeScript types. | 3 / 3 |
Distinctiveness Conflict Risk | While it focuses on advanced TypeScript types specifically, it could overlap with a general TypeScript skill or a broader programming/coding skill. The 'advanced type system' focus helps distinguish it, but terms like 'type-safe applications' and 'TypeScript projects' are broad enough to potentially conflict with general TypeScript skills. | 2 / 3 |
Total | 11 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill reads like a comprehensive TypeScript type system reference/tutorial rather than a targeted skill for Claude. It extensively explains concepts Claude already knows (generics, built-in utility types, type guards, discriminated unions) and is far too verbose for its purpose. While the code examples are high quality and executable, the document would benefit enormously from being trimmed to only novel patterns and non-obvious techniques, with content split across referenced files.
Suggestions
Remove sections covering concepts Claude already knows well (basic generics, built-in utility types, type guards, discriminated unions, best practices, common pitfalls) and focus only on non-obvious advanced patterns and project-specific conventions.
Split the monolithic document into a concise SKILL.md overview with references to separate files like PATTERNS.md (event emitter, API client, builder), INFERENCE.md (infer keyword, type testing), and FORMS.md (validation pattern).
Add a workflow section with guidance on when to choose specific patterns, how to debug complex type errors, and validation steps (e.g., 'run tsc --noEmit to verify types compile before proceeding').
Reduce the main SKILL.md to under 100 lines focusing on the 2-3 most non-obvious patterns and key decision points, rather than cataloging all TypeScript type features.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~500+ lines. Explains basic concepts Claude already knows well (generics, utility types like Partial/Readonly, discriminated unions, type guards). The 'When to Use This Skill' section, 'Best Practices' list, and 'Common Pitfalls' are all things Claude inherently understands. Much of this is a TypeScript handbook rewrite rather than novel instruction. | 1 / 3 |
Actionability | All code examples are fully executable TypeScript with concrete types, complete implementations, and clear expected outputs shown in comments. The patterns (event emitter, API client, builder, form validator) are copy-paste ready and demonstrate real-world usage. | 3 / 3 |
Workflow Clarity | The content is organized into logical sections with clear progression from basics to advanced patterns, but there's no workflow for actually applying these types in a project. No validation steps, no guidance on when to choose one pattern over another, and no error recovery guidance for common type errors. | 2 / 3 |
Progressive Disclosure | Monolithic wall of text with no references to external files. All content is inline in a single massive document. The advanced patterns, type inference techniques, and type testing sections could easily be split into separate referenced files to keep the main skill lean. | 1 / 3 |
Total | 7 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (718 lines); consider splitting into references/ and linking | Warning |
Total | 10 / 11 Passed | |
- Repository
- wshobson/agents
- Commit
34632bc
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.