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
81
76%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/using-git-worktrees/SKILL.mdQuality
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.
The description effectively communicates when to use the skill with explicit trigger conditions and targets a clear niche (git worktrees). Its main weakness is that the specific capabilities could be more concrete - terms like 'smart directory selection' and 'safety verification' are somewhat vague and could be expanded. The trigger terms are adequate but could include more natural user language variations.
Suggestions
Replace vague phrases like 'smart directory selection' and 'safety verification' with concrete actions, e.g., 'selects parent directories for worktree placement, verifies clean git state, and creates linked worktrees'
Add more natural trigger terms users might say, such as 'branch', 'parallel development', 'worktree add', or 'separate working copy'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description mentions 'creates isolated git worktrees with smart directory selection and safety verification' which names the domain (git worktrees) and some actions, but doesn't list multiple concrete actions comprehensively - 'smart directory selection' and 'safety verification' are somewhat vague. | 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 from current workspace or before executing implementation plans') with clear trigger conditions. | 3 / 3 |
Trigger Term Quality | Includes relevant terms like 'git worktrees', 'feature work', 'isolation', 'workspace', and 'implementation plans', but misses common variations users might say like 'branch', 'parallel development', 'worktree add', or 'separate working directory'. | 2 / 3 |
Distinctiveness Conflict Risk | Git worktrees is a very specific niche - this is clearly distinguishable from general git skills, branching skills, or workspace management. The triggers are specific enough to avoid conflicts with other skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill with clear workflows and good validation checkpoints. Its main weakness is redundancy across sections - the Quick Reference, Common Mistakes, Red Flags, and main workflow steps cover much of the same ground, inflating token cost without proportional value. The executable code examples and explicit safety verification steps are strong points.
Suggestions
Consolidate the Quick Reference table, Common Mistakes, and Red Flags sections into a single concise reference section to reduce redundancy and token usage
The 'Why critical' explanation after gitignore verification is unnecessary - Claude understands why committing worktree contents is bad
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but has some redundancy - the Quick Reference table, Common Mistakes, Red Flags, and Example Workflow sections overlap significantly in content. The 'Never/Always' lists largely restate what was already covered in the workflow steps and common mistakes. | 2 / 3 |
Actionability | Provides fully executable bash commands throughout, with concrete code for every step including directory detection, gitignore verification, worktree creation, project setup auto-detection, and test verification. Commands are copy-paste ready. | 3 / 3 |
Workflow Clarity | Clear sequential process with explicit validation checkpoints: verify directory is ignored before creating, run tests after setup, report failures and ask before proceeding. The feedback loop for gitignore (detect → fix → commit → proceed) and test failures (report → ask) are well-defined. | 3 / 3 |
Progressive Disclosure | Content is well-structured with clear headers and a logical flow, but everything is inline in a single file that runs fairly long. The Quick Reference table, Common Mistakes, Red Flags, and Example Workflow sections could potentially be trimmed or consolidated since they repeat earlier content rather than adding new information. | 2 / 3 |
Total | 10 / 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.
- Repository
- lucianghinda/superpowers-ruby
- Commit
cb03f92
- 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.