Content
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The content is well-structured with a clear process, safety checklist, and recovery protocol, and includes a concrete invocation prompt and example. Its main weakness is verbosity from cataloging concepts Claude already knows, with everything inlined in a single file rather than split across references.
Suggestions
Cut the explanatory catalogs of widely-known concepts (SOLID principle definitions, code-smell and design-pattern enumerations) down to the non-obvious guidance Claude would not already supply.
Move the long pattern/smell catalogs into reference files (e.g. references/patterns.md, references/code-smells.md) and link to them one level deep so SKILL.md stays a lean overview.
Keep the Task-tool prompt and before/after example as the actionable core and trim the surrounding boilerplate ('Use this skill when / Do not use this skill when' generic template).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is padded with well-known material Claude already knows (SOLID definitions, code-smell lists, design-pattern categories), but it also contains lean actionable elements like the Task-tool prompt and example, fitting 'mostly efficient but includes some unnecessary explanation'; not a 1 because the actionable core is genuinely lean. | 2 / 3 |
Actionability | It provides a concrete Task-tool invocation with a copy-paste prompt template and a worked before/after TypeScript example, but large portions are conceptual catalogs ('Apply Behavioral (Strategy, Observer, Command)') that describe rather than instruct, so it is not fully copy-paste ready throughout. | 2 / 3 |
Workflow Clarity | The numbered Core Process (Pre-Assessment through Safety Verification) plus a Safety Checklist and a Recovery Protocol with an explicit feedback loop (tests fail -> revert -> apply smaller changes) provides a clear sequence with validation checkpoints and error recovery. | 3 / 3 |
Progressive Disclosure | No bundle files exist (references/scripts/assets absent) and all content is inline in one monolithic file; pattern catalogs that should be split out are inline with no external references, matching 'content that should be separate is inline'; not a 1 because sections are at least organized. | 2 / 3 |
Total | 9 / 12 Passed |