Content
72%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body is a well-structured, efficient overview with a concrete decision framework for replacing any and exemplary progressive disclosure to a real, well-organized reference file. Its main gaps are the absence of any inline verification step in the body and no worked code example, both of which are deferred entirely to the reference file.
Suggestions
Add a brief verification step to the Fix section, e.g., 'After fixing, run tsc --noEmit and re-run ESLint to confirm no no-explicit-any warnings remain', rather than leaving verification only in the reference file.
Include one compact before/after inline example (any vs. unknown narrowing) so the replacement pattern is anchored without opening the reference.
Trim the intro paragraph's explanation of why any is unsafe, since that is a TypeScript concept Claude already knows.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is a lean ~45 lines with terse, purposeful sections (Check/Fix/Explain/Code Review), but the intro paragraph ('a function returning any propagates unchecked types to every caller') and bullets like 'unknown is the safe alternative — it requires a type check before use' partially re-explain TypeScript basics Claude already knows. These are minor over-explanations that could be trimmed, matching anchor 4 rather than the fully lean anchor 5. | 4 / 5 |
Actionability | Concrete decision guidance throughout: 'Replace the any types... with unknown (for values of unknown shape), appropriate generics (for type-consistent operations), or Zod validation (for external data)' and 'Flag every explicit or implicit any, any type assertion that lacks a preceding type guard'. As an instruction-only skill the guidance is specific and actionable, though no inline code example anchors the patterns (those are deferred to references/rule.md), so it stops short of anchor 5's copy-paste readiness. | 4 / 5 |
Workflow Clarity | The four modes (Check/Fix/Explain/Code Review) are clearly delineated with unambiguous single actions, but the check-to-fix sequence is only implicit and there is no verification step in the body — verification lives solely in references/rule.md. Since fixing any types across a file is a batch code-modification without inline validation, this matches anchor 3 ('checkpoints missing or implicit') and the batch-operation cap holds it at 3. | 3 / 5 |
Progressive Disclosure | The body is a well-organized overview (~45 lines, clear sections) that appropriately splits detail out of itself, ending with a clearly signaled one-level-deep reference: 'For full implementation details, code examples, and framework-specific guidance, see references/rule.md'. The referenced file exists, is well-structured with code examples and an ESLint config, and there is no nested-referencing indirection — matching anchor 5 exactly. | 5 / 5 |
Total | 16 / 20 Passed |