Content
85%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 tightly written orchestrator skill: a lean body of operational rules, concrete commands and flags inline, a clearly sequenced 5-step workflow with explicit re-verification checkpoints around the risky external writes, and well-signaled one-level references that all exist in the bundle. The only room for improvement is trimming a few meta-explanatory sentences and slightly richer inline command coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The ~50-line body is dense operational rules with zero padding about concepts Claude already knows, but a few sentences could be trimmed — e.g. the meta-explanation "Presence in the current tool list is proof the tool exists" and re-stating rules from references ("Two of its rules belong here too"). This fits the efficient-with-minor-trims anchor at 4 rather than the every-token-earns-its-place anchor at 5. | 4 / 5 |
Actionability | Gives concrete, executable guidance: "Pass the body via `--body-file <path>`, never stdin", "Never use `git add -A` or `git add .`", "target the base with `-R` and pass the branch name only", plus exact `gh pr edit` / `gh pr create` usage and match-head-owner-branch resolution. As an instruction-only skill this is highly actionable, but the full probe recipes are delegated to references, leaving minor gaps that keep it below the copy-paste-complete anchor at 5. | 4 / 5 |
Workflow Clarity | Steps 1-5 are clearly sequenced with mode dispatch, and validation checkpoints are explicit for the external-write operations: "Re-verify branch, remote, and PR state right before each consequential action", "Before `gh pr create`, re-check PR presence... non-zero blocks", the pre-publish gate ("otherwise stop before the external write"), and unknown-state blocking ("stop until presence is known"). This matches the anchor with explicit validation and error-recovery handling. | 5 / 5 |
Progressive Disclosure | The body is a lean overview that signals each reference load with when and why ("Read `references/context.md` before Step 1. It defines...", "load `references/stack-submit.md` before Step 3"), and all cited paths exist in the bundle; the two uncited files (visual-evidence.md, gh-stack-cli.md) are reachable via lateral cross-links from cited references, so nothing nests beyond one level from SKILL.md. This matches the clear-overview, well-signaled one-level-deep anchor. | 5 / 5 |
Total | 18 / 20 Passed |