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.
68
82%
Does it follow best practices?
Impact
—
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), names the specific library involved, and provides an explicit 'Use when' clause with multiple natural trigger terms. The description is distinctive enough to avoid conflicts 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 strong natural trigger terms: 'shoehorn', 'replace `as` in tests', 'partial test data', 'migrate test files', and 'type assertions'. 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. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides solid, actionable migration patterns with clear before/after examples and a useful reference table. Its main weaknesses are some verbosity in the explanatory sections and examples, and a workflow that lacks explicit validation commands and error recovery steps. Tightening the content and adding a feedback loop would elevate it significantly.
Suggestions
Add an explicit type-check command (e.g., `npx tsc --noEmit`) to the workflow's verification step, and include a feedback loop: 'If type errors remain, check import paths and ensure fromPartial vs fromAny is correct, then re-run.'
Consolidate the 'Large objects with few needed properties' and '`as Type` → `fromPartial()`' examples into a single pattern since they demonstrate the same transformation, reducing redundancy.
Remove or significantly trim the 'Why shoehorn?' section—Claude doesn't need to be told why `as` is problematic; a single line like 'Replaces `as` assertions in tests with type-safe partial data helpers' suffices.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The 'Why shoehorn?' section explains problems with `as` that Claude already understands, and the 'Large objects with few needed properties' example is overly verbose with comments like '...20 more properties'. The migration patterns section could be tighter by combining the first two examples since they illustrate the same transformation. | 2 / 3 |
Actionability | Provides fully executable code examples for each migration pattern, a concrete install command, a grep command to find targets, and a clear mapping table. Every pattern shows complete before/after with real 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 a feedback loop for error recovery caps this at 2. | 2 / 3 |
Progressive Disclosure | Content is reasonably structured with clear sections, but for a standalone skill with no bundle files, the inline content is somewhat long. The 'Large objects' example could be separated or condensed since it overlaps with the `as Type → fromPartial()` pattern. Organization is decent but not optimal. | 2 / 3 |
Total | 9 / 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
aaf2453
- 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.