Content
75%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 well-structured, efficient instruction skill: concrete card schema and Kanban criteria make the operating model actionable, and the failure-modes section adds genuine value. Weaknesses are mild — a redundant opening paragraph, high-level execution-mode steps without commands, and validation expressed as criteria rather than explicit feedback loops.
Suggestions
Drop or compress the opening paragraph that repeats the frontmatter description, and let the body start at 'When To Activate'.
Add one worked example of a single orchestration pass (board shaping through merge) to make the high-level flow steps concrete.
Make validation feedback loops explicit, e.g., 'if the merge gate fails, return the card to Blocked with the failing check recorded' rather than stating gates only as exit criteria.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is list- and table-driven with no explanations of concepts Claude already knows, but the opening paragraph restates the frontmatter description almost verbatim, and phrases like "Merge readiness by gate, not vibes" could be tightened — efficient with minor trim opportunities rather than fully lean. | 4 / 5 |
Actionability | Concrete artifacts are provided — a copy-paste JSON card schema, a Kanban table with per-column exit criteria, and a named failure-mode checklist — but the flow steps remain high-level ("Shape the board", "Pick execution mode") without specific commands or a worked example, leaving minor gaps for an otherwise actionable instruction skill. | 4 / 5 |
Workflow Clarity | The 7-step orchestration flow is clearly sequenced with an explicit review order ("tests first, then diff review, then security/risk checks, then content/product polish") and merge gates with exit criteria, but validation is expressed as criteria rather than explicit validate-fix-retry commands, leaving minor checkpoint gaps. | 4 / 5 |
Progressive Disclosure | Self-contained ~100-line body with well-organized, clearly headed sections and no nested or buried references; it is slightly over the size where inline-only structure would earn top marks, and sections like the card schema or control-pane requirements could arguably live in reference files. | 4 / 5 |
Total | 16 / 20 Passed |