Content
80%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 lean, well-structured skill body with concrete commands and no wasted tokens. The main gap is the absence of validation in the batch worktree-creation loop and the destructive cleanup steps, which caps workflow clarity despite otherwise clear sequencing.
Suggestions
Add a validation step after the batch creation loop (e.g., run "git worktree list" to confirm all N worktrees were created, and check "git branch --list '<feature>_*'" before creating to avoid name collisions).
Guard the cleanup section against data loss: note that "git branch -d" fails on unmerged branches and when to inspect or use "git branch -D" deliberately, and mention "git worktree remove --force" trade-offs.
Make the multi-worktree script executable as written by using shell variables for the feature name and count (e.g., FEATURE="$1"; COUNT="${2:-1}") instead of the literal placeholders N and <feature>.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body never explains what a worktree is or how git works — it assumes Claude's competence and spends every token on conventions and commands ("git worktree add <path> -b <branch>", the directory tree, the naming pattern). It matches 'lean and efficient; every token earns its place'. | 5 / 5 |
Actionability | Commands are concrete and mostly executable ("git worktree remove <path>", "git branch -d <branch>", "mkdir -p \"$WORKTREES_DIR\""), but the multi-worktree script is not copy-paste ready: "$(seq 1 N)" and "<feature>_${i}" are placeholders the reader must substitute. This fits 'concrete code or commands with minor gaps' rather than the fully copy-paste-ready anchor at 5. | 4 / 5 |
Workflow Clarity | The Workflow section lists a coherent 3-step sequence, but the batch loop that creates N worktrees has no validation or error handling — no check that a branch or worktree name already exists, no post-run "git worktree list" verification, and the destructive cleanup ("git branch -d <branch>") has no caution about unmerged work. Per the rubric, a batch operation without validation caps workflow clarity at 3, which matches the 'sequence present but checkpoints missing' anchor. | 3 / 5 |
Progressive Disclosure | The skill is a short (~50-line), single-purpose document with no bundle files and no need for external references; its five well-labeled sections (Directory Convention, Branch Naming, Workflow, Creating Multiple Worktrees, Cleanup) are easy to navigate. This matches the rubric's exception allowing a 5 for compact, well-organized skills without external file references. | 5 / 5 |
Total | 17 / 20 Passed |