CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

using-git-worktrees

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

73%Weight 40%Scale 1-5

Reviews 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.

DimensionReasoningScore

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

Description

78%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A well-constructed description that explicitly answers both what and when with an explicit 'Use when...' clause and concrete trigger conditions. Its weaknesses are mild: two of the three capability descriptors are vague ('smart directory selection', 'safety verification') and the plan-execution trigger slightly overlaps with related skills.

DimensionReasoningScore

Specificity

The description names the domain ('creates isolated git worktrees') plus two semi-concrete actions, but 'smart directory selection' is buzzword-flavored and 'safety verification' is generic, so coverage is not comprehensive as the level-4 anchor requires.

3 / 5

Completeness

Both parts are explicit: 'Use when starting feature work that needs isolation... or before executing implementation plans' answers when with two concrete trigger conditions, and 'creates isolated git worktrees with smart directory selection and safety verification' answers what. It is not the level-4 anchor because the 'when' clause is already explicit and specific rather than needing more detail.

5 / 5

Trigger Term Quality

Natural terms like 'worktrees', 'isolation', 'workspace', 'feature work', and 'implementation plans' give good keyword coverage; a few common phrasings users would actually say ('parallel branches', 'without switching branches') are missing, matching the level-4 rather than level-5 anchor.

4 / 5

Distinctiveness Conflict Risk

The git-worktree isolation niche is distinct with specific triggers, but the trigger 'before executing implementation plans' overlaps with plan-execution skills (e.g. executing-plans), giving minor overlap risk with closely related skills per the level-4 anchor rather than the minimal-conflict level-5 anchor.

4 / 5

Total

16

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

lucianghinda/superpowers-ruby

Path

skills/using-git-worktrees/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.