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
Install with Tessl CLI
npx tessl i github:obra/superpowers --skill using-git-worktrees90
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
75%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description effectively communicates when to use the skill with explicit trigger conditions upfront, and has a clear distinctive niche around git worktrees. However, it could benefit from more specific concrete actions beyond 'creates' and more natural trigger terms that users commonly say when needing this functionality.
Suggestions
Add more specific concrete actions like 'sets up worktree directories', 'configures branch tracking', or 'validates repository state' to improve specificity
Include additional natural trigger terms users might say such as 'parallel development', 'separate workspace', 'work on multiple branches', or 'git worktree'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (git worktrees) and some actions ('creates isolated git worktrees', 'smart directory selection', 'safety verification'), but lacks comprehensive concrete actions like specific commands or detailed capabilities. | 2 / 3 |
Completeness | Explicitly answers both what ('creates isolated git worktrees with smart directory selection and safety verification') and when ('when starting feature work that needs isolation' or 'before executing implementation plans') with clear trigger guidance at the start. | 3 / 3 |
Trigger Term Quality | Includes relevant terms like 'feature work', 'worktrees', 'implementation plans', but misses common variations users might say like 'branch', 'parallel development', 'separate workspace', or 'git worktree' as a phrase. | 2 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on git worktrees for feature isolation - distinct from general git skills, branching skills, or workspace management. The combination of 'worktrees' + 'isolation' + 'implementation plans' creates a unique trigger profile. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent skill that demonstrates best practices: it's concise yet comprehensive, provides executable commands with clear validation checkpoints, and handles edge cases explicitly. The safety verification workflow with feedback loops (check ignored → fix if not → proceed) is particularly well-designed. The Quick Reference table and Common Mistakes sections add value without bloat.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, assuming Claude's competence with git and shell commands. No unnecessary explanations of what worktrees are or how git works - jumps straight to actionable guidance. | 3 / 3 |
Actionability | Provides fully executable bash commands throughout, with specific examples for directory detection, worktree creation, and project setup. The example workflow demonstrates exact expected behavior. | 3 / 3 |
Workflow Clarity | Clear numbered steps with explicit validation checkpoints: verify ignored status before creation, run tests to establish baseline, report failures and ask before proceeding. The 'Red Flags' section reinforces critical validation points. | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections (Overview, Directory Selection, Safety Verification, Creation Steps, Quick Reference, Common Mistakes). The Quick Reference table provides scannable summary. Integration section clearly signals relationships to other skills. | 3 / 3 |
Total | 12 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- 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.