Content
67%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 dense, actionable runbook: a clear 9-step process with concrete bash commands, explicit validation checkpoints (branch-name regex, branch-conflict check, .gitignore verification), flag semantics, and well-signaled pointers to companion commands and an external database-branch guide. Its main weaknesses are repetition — symlink/dependency rules are restated across four sections, and the Quick reference and Common mistakes tables largely restate earlier content — and small gaps such as the unhandled --from <base> argument and delegated error-recovery for background verification.
Suggestions
Consolidate the dependency/symlink logic: it currently appears in "Dependency optimization", "Auto-Detect setup", the Quick reference table, and "Common mistakes"; state it once and have the other sections point back, trimming the Quick reference rows that merely restate earlier rules.
Cut or compress the inlined database-provider detail ("neonctl branches create --name <branch> --parent main", "pscale branch create <db> <branch>", the .worktreeinclude listing) since the section already links to the full external workflow guide — a summary line plus the link would suffice.
Document the --from <base> argument promised in the argument-hint (how the base branch is resolved and passed to git worktree add), and briefly state what to do when a background verification check fails rather than only deferring to /git-worktree-status.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body never explains concepts Claude already knows and is command-dense, but the same rules are stated repeatedly — the symlink/dependency logic appears in "Dependency optimization", "Auto-Detect setup", the Quick reference table ("Node.js project | Symlink node_modules by default", "--fast flag | Skip install + tests"), and "Common mistakes", and the database section inlines provider tables while also pointing to an external guide. This matches "Mostly efficient but includes some unnecessary explanation or could be tightened". Not score 4, because the Quick reference and Common mistakes sections substantially duplicate earlier sections rather than trimming them. | 3 / 5 |
Actionability | Most guidance is concrete and executable — "git worktree add .worktrees/$BRANCH_NAME -b $BRANCH_NAME", "echo \"$BRANCH_NAME\" | grep -qE '^[a-zA-Z0-9/_-]+$'", "ln -s ... node_modules", "npx tsc --noEmit > .worktree-logs/typecheck.log 2>&1 &" — with tables of exact provider commands ("neonctl branches create --name <branch> --parent main"). Minor gaps keep it from 5: the argument-hint advertises "[--from <base>]" but the body never handles it, and comments like "# or npm/yarn based on lockfile detection" are hints rather than complete recipes; the fragments are illustrative rather than a single copy-paste script. | 4 / 5 |
Workflow Clarity | The 9-step numbered Process ("1. Validate Branch Name ... 9. Report Location") is expanded section-by-section with explicit validation checkpoints: regex rejection ("Reject invalid characters"), branch conflict check ("git show-ref --verify --quiet ... && exit 1"), and a .gitignore verification with an add-commit-proceed loop ("If NOT in .gitignore: 1. Add line ... 2. Commit ... 3. Proceed"). Not score 5 because error recovery for the background verification is delegated to a companion command ("check with /git-worktree-status") rather than including a validate-fix-retry loop inline; not capped at 3 since worktree creation is additive, not destructive or batch. | 4 / 5 |
Progressive Disclosure | The body is well-sectioned with clear headers, and external depth is signaled at one level: "**Companion commands:** /git-worktree-status | /git-worktree-remove | /git-worktree-clean" and "**See:** [Database Branch Setup Guide](../../workflows/database-branch-setup.md) for complete workflows", with the DB section kept as a summary table plus pointer. This fits "Good structure; most content is appropriately placed; references mostly clear; minor organization gaps". Not score 5: no bundle files are provided, references resolve outside the skill directory and cannot be verified, and some detail (DB provider commands, .worktreeinclude setup) that could live in a reference file is inlined. | 4 / 5 |
Total | 15 / 20 Passed |