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 good structure with an explicit 'Use when' clause and clearly answers both what and when. Its main weaknesses are moderate vagueness in describing specific capabilities (e.g., 'smart directory selection') and missing some natural trigger terms users might use when needing this functionality. The niche is well-defined and distinctive.
Suggestions
List more concrete actions such as 'creates git worktrees, selects parent directories, verifies branch availability, and sets up isolated development environments'
Add more natural trigger terms users might say, such as 'worktree', 'parallel development', 'branch isolation', or 'separate working directory'
| 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 | The description 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 a clear 'Use when' clause. | 3 / 3 |
Trigger Term Quality | Includes relevant terms like 'feature work', 'git worktrees', 'workspace', 'implementation plans', and 'isolation', but misses common variations users might say like 'branch', 'parallel development', 'worktree', 'new feature branch', or 'separate workspace'. | 2 / 3 |
Distinctiveness Conflict Risk | Git worktree creation is a very specific niche that is unlikely to conflict with other skills. The triggers around 'feature work isolation' and 'worktrees' are distinct enough to avoid overlap with general git skills or branching 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 workflows and proper validation checkpoints for a multi-step process involving potentially destructive operations (gitignore management, worktree creation). Its main weakness is moderate redundancy—the 'Common Mistakes', 'Red Flags', and 'Quick Reference' sections repeat guidance already embedded in the workflow steps, inflating token cost without proportional value. The actionability and workflow clarity are strong, with executable commands and explicit error-handling paths throughout.
Suggestions
Consolidate 'Common Mistakes' and 'Red Flags' into the Quick Reference table or remove them entirely, as the main workflow steps already encode these constraints with their validation checkpoints.
Consider trimming the 'Example Workflow' section since it essentially restates the creation steps in a slightly different format.
| 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 'Quick Reference' table is helpful but partially redundant with the main content. | 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. Copy-paste ready commands with clear conditionals. | 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 sections and a quick reference table, but everything is inline in a single file that runs fairly long. The 'Common Mistakes' and 'Red Flags' sections could be trimmed or consolidated. The Integration section nicely references related skills but the main content could benefit from being more compact. | 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.