switch-worktree
Switch the current session to work in an existing git worktree
70
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
32%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 is too minimal, providing only a basic action statement without trigger guidance or comprehensive capability coverage. While it correctly identifies the git worktree domain, it fails to help Claude understand when to select this skill over others and lacks the explicit 'Use when...' clause required for effective skill selection.
Suggestions
Add a 'Use when...' clause with trigger terms like 'switch worktree', 'change worktree', 'move to worktree', 'work in different worktree'
Expand the capability description to include related actions like listing available worktrees or validating the target worktree exists
Include natural language variations users might say such as 'switch to another branch worktree' or 'change working directory to worktree'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (git worktree) and a specific action (switch session), but only describes one action rather than multiple concrete capabilities. | 2 / 3 |
Completeness | Describes what it does (switch to a worktree) but completely lacks any 'Use when...' clause or explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes 'git worktree' which is relevant, but misses common variations users might say like 'change worktree', 'switch branch', 'working directory', or abbreviations. | 2 / 3 |
Distinctiveness Conflict Risk | 'Git worktree' is fairly specific and wouldn't conflict with general git skills, but could overlap with other worktree-related skills (create, delete, list worktrees) without clearer differentiation. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
85%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, concise skill that clearly guides Claude through switching worktrees with appropriate validation checkpoints. The main weakness is the use of placeholder syntax rather than showing executable command construction, which slightly reduces actionability. Overall, it's an effective skill that respects token budget while providing clear workflow guidance.
Suggestions
Show concrete command construction, e.g., `cd "$(git rev-parse --show-toplevel)/.worktrees/${NAME}"` instead of placeholder `cd WORKTREE`
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, with no unnecessary explanations. Every line serves a purpose—Claude doesn't need to be told what a worktree is or how git works. | 3 / 3 |
Actionability | Provides clear steps and specific commands, but uses placeholder syntax (e.g., `cd WORKTREE`) rather than showing how to actually construct and execute the command. The verification steps are good but could be more concrete. | 2 / 3 |
Workflow Clarity | Clear three-step sequence with explicit validation checkpoints: verify worktree exists before switching, verify pwd after switching, and stop with errors if validation fails. Good feedback loop for error recovery. | 3 / 3 |
Progressive Disclosure | For a simple, single-purpose skill under 50 lines, the content is well-organized with clear sections. No external references needed; the skill is self-contained and appropriately scoped. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- 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.