Content
82%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 a concise, well-structured, actionable workflow with concrete commands and meaningful validation checkpoints. Its main gaps are minor: a few steps lack explicit success checks and some actions delegate to other skills with placeholders to fill.
Suggestions
Add an explicit success check after worktree/branch creation (e.g. verify the branch exists with git branch) before proceeding to dev setup.
Briefly note the expected outputs or failure signals of the delegated /create-worktree and /worktree-make-dev skills so the agent can detect when they fail.
Consider a short 'Prerequisites' line stating required upstream state (repo cloned, gh authenticated) to make the entry conditions explicit.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and efficient: it jumps straight into parsing, commands, and a numbered workflow with no padding or explanation of concepts Claude already knows (e.g. no primer on what a worktree is). Every section earns its place, matching the lean-and-efficient anchor. | 5 / 5 |
Actionability | It provides concrete, executable commands (gh issue view, git fetch origin devel, git -C <worktree-path> checkout --no-track -b, pwd) with explicitly defined placeholders, but several steps delegate to other skills (/create-worktree, /worktree-make-dev) and placeholders require substitution. This fits mostly-executable with minor gaps rather than fully copy-paste ready. | 4 / 5 |
Workflow Clarity | A clear 7-step sequence includes explicit validation checkpoints (validate branch name pattern, verify the issue exists, verify cwd with re-check and error-stop), but a few steps (e.g. worktree/branch creation) lack an explicit success check. This matches clear-sequence-with-most-checkpoints rather than the fully-checkpointed level above. | 4 / 5 |
Progressive Disclosure | Content is well organized into clearly labeled sections and delegates detail to one-level-deep skill invocations (/create-worktree, /worktree-make-dev) that are clearly signaled, with no nested file references. No bundle files exist to verify, and the structure is good with minor organization gaps, fitting the good-structure anchor. | 4 / 5 |
Total | 17 / 20 Passed |