Content
73%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 delivers a clear, well-sequenced workflow with strong validation checkpoints and mostly copy-paste-ready commands, making it highly actionable. Its main cost is token efficiency: foundational explanation and three overlapping rule sections could be consolidated without losing clarity, and one shell snippet has a tilde-expansion flaw.
Suggestions
Consolidate 'Quick Reference', 'Common Mistakes', and 'Red Flags' into a single section - they currently restate the same rules (ignore verification, directory priority, failing tests, auto-detect setup) in three different formats.
Drop the Overview sentence explaining what git worktrees are and the 'Per Jesse's rule' personal aside; both spend tokens on context Claude already has or does not need.
Fix the creation-path snippet to be executable: quoted '~' does not expand in 'git worktree add "$path"', and $LOCATION/$BRANCH_NAME are never defined - use $HOME explicitly and show how the variables are set.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient and command-dense, but the Overview explains what git worktrees are (already known to Claude), and the same rules are restated three times across 'Quick Reference', 'Common Mistakes', and 'Red Flags', which is more than the minor trimming the level-4 anchor tolerates. | 3 / 5 |
Actionability | Nearly all guidance is executable (git check-ignore, git worktree add, auto-detected setup commands), but the creation-path 'case $LOCATION' snippet uses undefined variables and a quoted '~' that will not expand in 'git worktree add "$path"', leaving minor gaps versus copy-paste-ready level 5. | 4 / 5 |
Workflow Clarity | The process is clearly sequenced (directory priority order, safety verification, creation steps 1-5) with explicit validation checkpoints (git check-ignore, SQLite helper exit-code check, baseline test run), error-recovery handling for each failure, and checklists. Not a destructive/batch operation, so no cap applies. | 5 / 5 |
Progressive Disclosure | No bundle files exist, and the single-file structure with clear numbered sections and a quick-reference table is well organized for a ~240-line skill. It falls short of level 5 because there is no reference signaling at all and some inline content (the duplicated rule sections) reflects minor organization gaps. | 4 / 5 |
Total | 16 / 20 Passed |