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
84
76%
Does it follow best practices?
Impact
100%
2.32xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./.opencode/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 has strong completeness with explicit 'Use when' triggers and a clear niche that minimizes conflict risk. However, the specific capabilities could be more concrete (e.g., what does 'smart directory selection' actually do?), and the trigger terms could include more natural user language variations like 'branch', 'parallel work', or 'git worktree'.
Suggestions
Add more concrete action descriptions - replace vague phrases like 'smart directory selection' with specifics like 'selects parent directory, creates worktree folder, checks out new branch'
Include additional natural trigger terms users might say, such as 'branch', 'parallel development', 'separate workspace', 'git worktree', or 'work on multiple branches'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (git worktrees) and some actions ('creates isolated git worktrees with smart directory selection and safety verification'), but doesn't list multiple concrete actions beyond creation. '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 'feature work', 'worktrees', 'implementation plans', and 'isolation', but misses common user phrases like 'branch', 'parallel development', 'git worktree', 'new branch workspace', or 'separate working directory'. | 2 / 3 |
Distinctiveness Conflict Risk | Git worktree creation is a very specific niche that is unlikely to conflict with other skills. The triggers around 'isolation from current workspace' and 'implementation plans' are distinct enough to avoid false matches with general git 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 well-structured, actionable skill with clear sequential workflows and proper validation checkpoints. Its main weakness is moderate verbosity—the 'Common Mistakes' and 'Red Flags' sections largely restate constraints already embedded in the workflow steps, consuming tokens without adding new information. The executable code examples and decision tables are strong points that make this immediately usable.
Suggestions
Consolidate 'Common Mistakes' and 'Red Flags' into a single compact checklist to reduce redundancy with the main workflow steps.
Remove explanatory text like 'Why critical: Prevents accidentally committing worktree contents to repository' since Claude understands gitignore implications.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some unnecessary sections like 'Common Mistakes' and 'Red Flags' that largely repeat information already covered in the workflow steps. The 'Why critical' explanation for gitignore verification is slightly verbose for Claude's level of understanding. | 2 / 3 |
Actionability | Provides fully executable bash commands throughout, with concrete code for directory detection, worktree creation, project setup auto-detection, and test verification. The quick reference table and example workflow make it copy-paste ready. | 3 / 3 |
Workflow Clarity | Clear sequential steps with explicit validation checkpoints: verify ignored → add to .gitignore if not → create worktree → run setup → verify tests → report or ask on failure. Includes proper feedback loops for error recovery (failing tests, missing gitignore). | 3 / 3 |
Progressive Disclosure | Content is well-structured with clear sections and a quick reference table, but it's somewhat long for a single file with no references to external documentation. The 'Common Mistakes' and 'Red Flags' sections could be consolidated, and the Integration section adds useful cross-references but the overall document could benefit from splitting detailed setup patterns into a separate file. | 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
- projectbluefin/dakota
- Commit
f062bf8
- 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.