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.
The body is concise, well-structured, and gives actionable routing and a sequenced run procedure with a verification checkpoint. Its main weakness is progressive disclosure: it points to docs/WORKFLOWS.md and data/workflows.json that are not bundled, leaving the detailed playbooks inaccessible.
Suggestions
Bundle the referenced docs/WORKFLOWS.md and data/workflows.json (or remove the references and inline the essential playbook content) so the one-level-deep references actually resolve.
Replace the generic 'Verify completion criteria' checkpoint with concrete, per-workflow validation steps or a feedback loop (validate -> fix -> retry) for batch or destructive operations.
Trim the five near-identical 'Copy-Paste Prompts' to one or two representative examples to tighten token efficiency.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean with well-organized sections and no explaining of concepts Claude already knows; not a 5 because the 'Copy-Paste Prompts' section repeats five near-identical examples and the 'When to Use' list re-states the description's scenarios. | 4 / 5 |
Actionability | Provides a concrete routing table ('Default Workflow Routing'), named workflow IDs (e.g. ship-saas-mvp), and an executable step-by-step run procedure; not a 5 because verification guidance is generic rather than specific commands or criteria. | 4 / 5 |
Workflow Clarity | 'How to Run This Skill' is a clear five-step sequence with an explicit verification checkpoint ('Verify completion criteria before moving to next step'); not a 5 because the validation is abstract and there is no error-recovery/feedback loop. | 4 / 5 |
Progressive Disclosure | Sections are clearly organized and references are signaled ('docs/WORKFLOWS.md', 'data/workflows.json'), but those referenced files are not present in any bundle directory, so the core detailed playbooks are unresolvable; not a 4 because the one-level-deep references do not resolve to actual files. | 3 / 5 |
Total | 15 / 20 Passed |