Content
63%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, actionable research-workflow skill with a concrete schema, gated steps, and strong examples. Its main weaknesses are some framework over-explanation Claude does not need, and dead references to template/example files that are not actually bundled.
Suggestions
Ship the missing bundle files referenced in the body (template.md, examples/sample.md, examples/sample-industrial.md) or remove the links — dead references break the skill's progressive-disclosure promises.
Tighten the 'Key Concepts' section: drop the teaching of what the Ansoff Matrix and its risk gradient are (Claude already knows) and keep only the operational rules the skill enforces (signal-or-don't-ship, gradient sets evidence burden, do-not-invent list).
Add one explicit validation step to the Application sequence — e.g. 'before emitting, confirm every quadrant move carries a labeled signal or is marked empty' — to convert the woven discipline into a hard checkpoint.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly operational (Input, Application, schema, Final Step, Pitfalls) but spends tokens teaching the Ansoff framework and risk gradient Claude already knows ('The framework (Ansoff, 1957)...', 'The risk gradient is law...'), which could be tightened into bare operational rules. | 3 / 5 |
Actionability | Concrete, copy-paste-ready output schema, numbered Application steps, and worked quadrant/sequence examples make the guidance mostly executable; the gap is that the cited fill-in template and worked samples (template.md, examples/sample.md, examples/sample-industrial.md) do not exist, so a follower hits dead ends. | 4 / 5 |
Workflow Clarity | A clear sequence (check session → credit context + ask ≤3 → search-plan gate → populate + emit schema → 4-option Final Step) with a revision gate and an 'Assumptions to Validate' checkpoint, but validation is woven into discipline rather than an explicit hard verify step, leaving a minor gap below anchor 5. | 4 / 5 |
Progressive Disclosure | References are clearly signaled and one level deep, but all three referenced files (template.md, examples/sample.md, examples/sample-industrial.md) are missing and no references/scripts/assets directories exist, so the disclosed navigation leads nowhere — structure is present but the bundle does not back it. | 3 / 5 |
Total | 14 / 20 Passed |