Content
88%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 an exemplary operational skill: fully concrete commands and tool names, a clearly phased workflow with validation and retry loops at every risky step, and no wasted tokens. Its only weakness is that the Hand-off section concentrates five long decision paths plus issue-labeling housekeeping into one monolithic block that a well-signaled reference file could offload.
Suggestions
Split the five Hand-off path bullets and the completed-phase labeling housekeeping into a reference file (e.g. references/handoff.md), keeping a short decision summary in SKILL.md.
Break the very long first Hand-off bullet into shorter sub-steps so the open-change-request path is scannable.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and operational with no explanations of concepts Claude already knows, and every section earns its tokens; only minor tightening is possible in a few run-on sentences ('Say plainly in your messages which of these are done and which remain, so the judge can tell') and the very long Hand-off bullets. | 4 / 5 |
Actionability | Guidance is near copy-paste ready: concrete commands ('git rev-parse --show-toplevel', 'gh pr list --head <your branch> --state open', the full 'gh label create' invocation with flags), named tools with arguments ('factory_transition_work_item', 'source_control_create_change_request', 'ask_user'), and explicit retry policies ('sleep 20'... 'retry, up to three times') covering all the common paths. | 5 / 5 |
Workflow Clarity | Phases are clearly sequenced (Find the plan → Implement → Verify and push → Hand-off) with explicit validation checkpoints (repository guard before edits and pushes, gates must pass before push, 'A regression test must fail without the fix') and feedback loops for error recovery (rejected transitions: 'read the reason, address it... and retry once'; plan proven wrong → move back to Planning). | 5 / 5 |
Progressive Disclosure | A single-file skill (~60 lines) with well-organized sections and no external references needed, so no bundle is required; however, the five dense Hand-off path bullets push it past the under-50-line simple-skill guideline, and the branch-specific labeling/transition rules are plausible candidates for a reference file. | 4 / 5 |
Total | 18 / 20 Passed |