Content
71%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.
A lean, well-structured troubleshooting skill whose diagnostic table and retry template make it genuinely actionable, with a coherent repair sequence and escalation loop. Its main weakness is progressive disclosure: the body routes to roughly a dozen reference files that are not present in the bundle and are addressed via '../..' paths outside the skill directory.
Suggestions
Ship the referenced files in a skill-local references/ directory and use relative links from SKILL.md (e.g. references/model-mechanics.md) instead of '../../references/...', or inline the small ones and cut the rest.
Add a worked example of the Conservative Retry Pattern showing one filled-in prompt for a common failure (e.g. identity drift in I2V).
Trim the 'Intent' section to one sentence and fold the tone guidance into the Output Contract to save tokens.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and nearly free of concept explanation Claude already knows; the 20-row diagnostic table delivers high information per token. The 'Intent' section ('A failed generation feels personal... The soul of this skill is rescue without blame...') and some abstract framing ('Remove conflicts rather than adding complexity') are minor over-explanation that could be trimmed, placing it one notch below 'every token earns its place'. | 4 / 5 |
Actionability | The diagnostic tree (symptom → likely cause → first repair) and the fill-in 'Conservative Retry Pattern' template are concrete, executable guidance with minor gaps, matching the 'mostly executable with minor gaps' anchor. It is not a 5 because there is no worked example (e.g. a filled retry prompt) and some repairs stay generic ('Add preservation constraints') without showing what a constraint looks like. | 4 / 5 |
Workflow Clarity | The Repair Process section gives a clear ordered sequence (quote failing phrase → state hypothesis with uncertainty → remove conflicts → one primary repair → one conservative retry), with escalation rules forming an error-recovery loop. This matches 'clear sequence with most checkpoints present; minor validation gaps' — the sequence is spread across several sections and there is no explicit validation checkpoint confirming the diagnosis before retry. | 4 / 5 |
Progressive Disclosure | References are clearly signaled with conditional load instructions ('load [model-mechanics] when the diagnostic tree has no row'), which is good practice, but the body points to ~11 files at '../../references/*.md' and no references/ directory (or any bundle files) exist in the skill directory — the links are dangling and the paths point two levels outside the skill rather than to a skill-local bundle. Per the judging guideline to score against the actual bundle structure, the structure cannot be verified and navigation is not reliable, fitting the mid anchor rather than 'most content appropriately placed' at 4. | 3 / 5 |
Total | 15 / 20 Passed |