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 exemplary orchestration-style skill body: dense, declarative rules with no filler, a checkpointed five-step workflow, and disciplined progressive disclosure into real reference files loaded exactly when needed. The only notable gap is that a handful of mechanics live solely in the references, so the body alone is not fully self-sufficient for execution.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean rule-based orchestration with zero explanation of git/PR concepts Claude already knows; every sentence carries a directive ("Pass the body via `--body-file <path>`, never stdin — `gh` exits 0 with an empty body"). It matches 'assumes Claude's competence; every token earns its place'; the small restatement of two context.md rules is intentional surfacing, not padding. | 5 / 5 |
Actionability | Concrete, executable guidance is frequent: exact command semantics ("`git add -A`", "`--body-file <path>`", "`gh pr edit`", "`-R`" targeting on forks), exit-code-to-control-flow rules, and explicit stop conditions. Score 4 rather than 5 because the body itself contains few complete command sequences — the bulk of mechanics is deliberately deferred to reference files, leaving minor gaps when read alone. | 4 / 5 |
Workflow Clarity | A clear Steps 1-5 sequence with explicit validation checkpoints: "Re-verify branch, remote, and PR state right before each consequential action", the pre-create PR-presence re-check with exit-code handling (exit-0 `[]` creates, non-zero blocks), the project publishing gate before external writes, and error-recovery paths (resolve auth/connectivity, stop on ambiguous match). This matches the anchor with feedback loops and checkpointed risky operations, so the destructive-operation cap does not apply. | 5 / 5 |
Progressive Disclosure | The body is a well-structured overview that defers detail to eight real, clearly signaled one-level-deep references, each loaded at its point of use ("Read `references/context.md` before Step 1", "load `references/stack-submit.md` before Step 3"). The single chained file (`references/gh-stack-cli.md` reached via stack-submit.md) is a clearly signaled, stack-mode-only exception, so the structure still fits the anchor for well-organized one-level-deep references. | 5 / 5 |
Total | 19 / 20 Passed |