Content
92%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.
An exceptionally disciplined orchestration skill body: lean invariant-first prose, a strictly ordered tick workflow with real validation gates and recovery loops, and clean one-level-deep progressive disclosure into a well-organized reference bundle. The only soft spot is that a handful of execution mechanics (atomic marks, snapshot invocation details) live entirely in reference files, leaving minor gaps if the body is read alone.
Suggestions
Inline one-line examples of the two most-used mechanics — the pr-snapshot invocation and the shared atomic mark syntax — so a reader can execute the core tick without opening references/tick.md first.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is extremely lean: no concept explanations, no padding, and every clause encodes a real rule or boundary (e.g. 'never merges; offer stack-wide once if a confirmed managed stack needs work'). It fully assumes Claude's competence, matching anchor 5 ('every token earns its place') rather than 4, which requires trimmable over-explanation that is essentially absent. | 5 / 5 |
Actionability | Concrete commands and skill invocations appear at decision points ('gh repo view', 'gh pr checkout <ref>', 'ce-resolve-pr-feedback mode:pipeline', 'gh stack merge') alongside exact state conditions ('manager_status == "confirmed"', 'open_needs_human == 0'). A few mechanics are deferred to reference files without inline specifics ('the shared atomic mark', the pr-snapshot invocation syntax), leaving minor gaps that fit anchor 4 ('mostly executable, minor gaps') rather than the fully copy-paste-ready anchor 5. | 4 / 5 |
Workflow Clarity | A clearly sequenced four-step process with a strict 7-step ordering invariant per tick, explicit validation checkpoints (terminal check first, stale-SHA cancellation, checkout gate with 'no push access or dirty checkout → stop, say so'), exact stop-condition guards, and error-recovery loops (CI routed by cause with re-run/needs-human/ce-debug, detector re-arming). This matches anchor 5; the mutation-heavy workflow has its validation and feedback loops in place. | 5 / 5 |
Progressive Disclosure | The body serves as an overview of invariants and routing, with twelve one-level-deep reference files each cited at the point of need and with a statement of what that file owns (e.g. branch-currency.md 'owns who updates a BEHIND branch'). All cited reference paths and the bundled pr-snapshot script exist in the bundle, and content is appropriately split — matching anchor 5. | 5 / 5 |
Total | 19 / 20 Passed |