migrate-to-shoehorn
Migrate test files from `as` type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace `as` in tests, or needs partial test data.
89
86%
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 is concise, specific, and well-structured. It clearly identifies the concrete action (migrating type assertions to shoehorn), provides an explicit 'Use when' clause with multiple natural trigger terms, and occupies a distinct niche that minimizes conflict risk with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description lists a concrete action: 'Migrate test files from `as` type assertions to @total-typescript/shoehorn.' This is a specific, well-defined task with clear technical details about what is being replaced and what it's being replaced with. | 3 / 3 |
Completeness | Clearly answers both 'what' (migrate test files from `as` type assertions to @total-typescript/shoehorn) and 'when' (explicit 'Use when' clause with three trigger scenarios: mentioning shoehorn, replacing `as` in tests, or needing partial test data). | 3 / 3 |
Trigger Term Quality | Includes natural trigger terms users would say: 'shoehorn', 'replace `as` in tests', 'partial test data', 'type assertions', and 'migrate test files'. These cover the main ways a user would describe this need. | 3 / 3 |
Distinctiveness Conflict Risk | This is a very specific niche skill targeting a particular library (@total-typescript/shoehorn) and a specific migration pattern (`as` assertions in test files). It is highly unlikely to conflict with other skills due to its narrow, well-defined scope. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable migration skill with clear before/after code examples and a useful reference table. Its main weaknesses are some verbosity in the motivation section and examples, and a workflow that lacks an explicit validation command and error recovery loop. The migration patterns are well-structured and immediately usable.
Suggestions
Trim the 'Why shoehorn?' section to 1-2 lines—Claude doesn't need motivation, just the constraint ('Test code only') and the pattern mapping.
Add the specific type-check command (e.g., `npx tsc --noEmit`) to the workflow's verification step, and include a feedback loop: 'If type errors remain, check for missing `fromAny` conversions where data is intentionally wrong.'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The 'Why shoehorn?' section explains motivations that are somewhat unnecessary for Claude (e.g., 'Trained not to use it'). The 'Large objects with few needed properties' example is verbose with comments about '20 more properties' that pad the content. The core patterns could be tighter. | 2 / 3 |
Actionability | Provides fully executable code examples with clear before/after patterns, a concrete install command, a grep command to find targets, and a specific migration checklist. All code is copy-paste ready with proper imports. | 3 / 3 |
Workflow Clarity | The workflow section has a clear sequence with a checklist, but the validation step is just 'Run type check to verify' without specifying the command (e.g., `npx tsc --noEmit`) or what to do if it fails. Missing feedback loop for error recovery caps this at 2. | 2 / 3 |
Progressive Disclosure | For a skill of this size and scope (single-purpose migration task under ~80 lines of meaningful content), the structure is well-organized with clear sections: motivation, install, patterns, reference table, and workflow. No need for external file references. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- mattpocock/skills
- Commit
651eab0
- 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.