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.
An exceptionally disciplined instruction-only skill body: a tight 4-step workflow with an explicit per-tick ordering invariant, built-in validation guards (terminal check, stale-SHA cancellation, stop-condition checklist, budget backstop), and zero padding. The two weaknesses are minor: the core pr-snapshot invocation is deferred to references rather than shown once in the body, and the reference web nests two levels deep with one file (stack-commands.md) not surfaced from SKILL.md.
Suggestions
Include one minimal executable example of the pr-snapshot invocation (or a pointer to its interface) directly in Step 2, so the skill's core action is runnable without first opening references/tick.md.
Surface stack-commands.md from the body (e.g. in the posture or stack-maintenance bullet) so every bundle file is reachable one level deep from SKILL.md.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The ~50-line body is lean and assumes Claude's competence: no known-concept explanation, no padding, and every rule is novel domain content ("Settled ≠ merged", "a push that restarts green CI without a claimed item is a defect"). It matches 'every token earns its place'; a 4 would require minor trimmable over-explanation, of which there is none. | 5 / 5 |
Actionability | Mostly executable: copy-paste commands appear for key operations ("gh run rerun <run-id> --failed -R <host>/<owner>/<repo>", "gh pr checkout <ref>", "gh stack merge") and delegate invocations are exact ("ce-resolve-pr-feedback mode:pipeline", "ce-debug mode:pipeline"). It is not a 5 because the central pr-snapshot invocation that drives every tick is never shown in the body — the reader must open references/tick.md or watch-loop.md to execute the skill's core action. | 4 / 5 |
Workflow Clarity | The sequence is explicit with validation checkpoints and feedback loops: a numbered 4-step arc, an ordering invariant inside each tick (terminal check first, stale-SHA cancellation guard, "mark each check acted on", "unfixed checks stay red residuals"), enumerated true-stop conditions with a budget backstop, and defect reporting for unauthorized actions. This matches 'clear sequence with explicit validation steps; feedback loops for error recovery'. | 5 / 5 |
Progressive Disclosure | The body is a well-organized overview that points to topical reference files at the exact step where each is needed (tick.md, envelope.md, settle.md, branch-currency.md, stack.md, watch-loop.md, pipeline.md, report.md, setup.md), all of which exist in references/. It is not a 5 because reference files cross-reference each other (e.g. settle.md → stack.md → stack-commands.md, two levels deep) and stack-commands.md is unreachable from the body, a minor navigation gap; it is well above a 3 since the SKILL.md-level structure is clean and every split is appropriate. | 4 / 5 |
Total | 18 / 20 Passed |