mcollina/typescript-magician
Designs complex generic types, refactors `any` types to strict alternatives, creates type guards and utility types, and resolves TypeScript compiler errors. Use when the user asks about TypeScript (TS) types, generics, type inference, type guards, removing `any` types, strict typing, type errors, `infer`, `extends`, conditional types, mapped types, template literal types, branded/opaque types, or utility types like `Partial`, `Record`, `ReturnType`, and `Awaited`.
97
97%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%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 an excellent skill description that clearly articulates specific capabilities, provides comprehensive trigger terms covering both common and advanced TypeScript type system concepts, and explicitly states when to use the skill. It uses proper third-person voice throughout and is well-scoped to avoid conflicts with broader programming skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: designing complex generic types, refactoring `any` types to strict alternatives, creating type guards and utility types, and resolving TypeScript compiler errors. | 3 / 3 |
Completeness | Clearly answers both 'what does this do' (designs generic types, refactors any types, creates type guards, resolves compiler errors) AND 'when should Claude use it' with an explicit 'Use when...' clause listing extensive trigger scenarios. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'TypeScript', 'TS', 'types', 'generics', 'type inference', 'type guards', 'removing any types', 'strict typing', 'type errors', 'infer', 'extends', 'conditional types', 'mapped types', 'template literal types', 'branded/opaque types', and specific utility types like 'Partial', 'Record', 'ReturnType', 'Awaited'. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to TypeScript's type system specifically, not general TypeScript development or general coding. The focus on generics, type guards, utility types, and compiler errors creates a distinct niche unlikely to conflict with broader coding or JavaScript skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill with strong actionability, clear workflow with validation checkpoints, and excellent progressive disclosure through categorized rule file references. The main weakness is some unnecessary verbosity in the capabilities list and generic instructions (e.g., 'explain the type theory') that don't add value for Claude. Overall, it's a solid skill that effectively balances overview content with detailed references.
Suggestions
Remove or significantly trim the 'Capabilities include' bullet list — Claude already knows these TypeScript features; listing them wastes tokens without adding actionable guidance.
Tighten the 'For every TypeScript challenge' section — instructions like 'Explain the type theory behind the problem' and 'Ensure full IntelliSense support' are vague and don't provide concrete guidance on how to do so.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The 'Capabilities include' bullet list largely restates things Claude already knows. The instruction to 'Explain the type theory behind the problem' and 'Provide multiple solution approaches when applicable' are somewhat generic. However, the examples are lean and the reference section is well-structured without excessive prose. | 2 / 3 |
Actionability | The workflow starts with a concrete command (`tsc --noEmit`), provides fully executable before/after code examples for two common scenarios, and ends with a verification step. The examples are copy-paste ready and demonstrate real patterns. | 3 / 3 |
Workflow Clarity | The 5-step workflow is clearly sequenced with explicit validation checkpoints: run `tsc --noEmit` before changes, identify root cause, craft solution, validate replacements satisfy call sites, and confirm with a second `tsc --noEmit` pass. This is a proper feedback loop for a potentially destructive refactoring operation. | 3 / 3 |
Progressive Disclosure | The skill provides a concise overview with quick examples, then cleanly delegates to 14 well-organized, categorized rule files with descriptive one-line summaries. All references are one level deep and clearly signaled with descriptive labels. | 3 / 3 |
Total | 11 / 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 |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
Total | 10 / 11 Passed | |
Reviewed
Table of Contents