Content
100%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 efficient, executable reference with sequenced workflows, validation/recovery for risky operations, and well-signaled one-level-deep references that match real bundle files.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and assumes competence: it skips generic git/PR concepts and reserves its tokens for skill-specific facts (TTY detection, --remote requirements, exit codes), with tables instead of prose. Not a 4 because there is no over-explanation to trim. | 5 / 5 |
Actionability | Copy-paste-ready bash commands with required flags throughout — e.g. 'gh stack submit --auto', 'gh stack merge 42 --yes', 'gh stack rebase --upstack' — covering the common creation, edit, sync, and merge cases. | 5 / 5 |
Workflow Clarity | The core loop and branch-placement flow are explicitly sequenced with checkpoints (view --json, inspect git log, checkout owner, rebase upstack, return to top), and destructive/batch ops (merge, sync, rebase) have a feedback loop via the Exit 3 recovery section. | 5 / 5 |
Progressive Disclosure | A concise overview points to three one-level-deep references, each with a clear task trigger ('read before creating a stack', 'read when a command fails', 'read on a rebase conflict') and the explicit instruction not to preload all three; all referenced files exist. | 5 / 5 |
Total | 20 / 20 Passed |