Content
96%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 dense, operational single-file skill: every line teaches gh-stack-specific behavior Claude could not guess, commands are executable with exit codes and recovery paths, and the main workflow is validated at each step. The only structural reservation is that the bundled scripts it references are unverifiable here and some reference-grade material (exit codes, TUI prompts) is inlined.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Nearly every sentence carries non-obvious, tool-specific operational knowledge — "Half of `gh stack` opens a full-screen TUI", "`--auto` creates every PR as a draft unless `--open` is passed", exit-code semantics — with zero padding and no explanation of concepts Claude already knows. It matches the lean anchor; not 4 because there is no identifiable over-explanation to trim. | 5 / 5 |
Actionability | Copy-paste-ready commands cover every common case: `bash <skill-dir>/status.sh [target]`, `gh stack rebase --continue`, `gh stack submit --auto --open`, `gh run rerun <run-id> --failed`, `gh pr edit <pr> --title <title> --body-file <file>`, with placeholders, exit codes, and flags spelled out. Fully executable rather than mostly executable, so it sits above the 4 anchor. | 5 / 5 |
Workflow Clarity | The sync workflow is a numbered sequence with an explicit validation checkpoint ("Rerun `status.sh` and show it. That is the proof the sync landed"), a conflict feedback loop (resolve, `git add`, "repeat until it exits 0"), a watch loop for pending checks, confirmation gates for the destructive `merge`/`unstack`, and `--dry-run` gating for the batched approval. Explicit validation plus error-recovery loops matches the 5 anchor; the destructive/batch cap at 3 does not apply because validation and confirmation are present. | 5 / 5 |
Progressive Disclosure | Good structure: well-signaled one-level-deep references (`status.sh`, `watch.sh`, `approve.sh` by path, "Every flag list lives in `gh stack <command> --help`... Read it there instead of guessing", the `pr` skill) and clearly headed sections. Not 5 because the referenced script files are not present in the bundle to verify, and at ~185 lines the exit-code table and TUI-prompt details are inlined where a separate reference file could carry them. | 4 / 5 |
Total | 19 / 20 Passed |