Create or reuse a git worktree for a pull request or branch so reviews and work happen in isolation
85
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
57%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 adequately identifies its specific domain (git worktrees) and purpose (isolated PR/branch work), making it reasonably distinctive. However, it lacks an explicit 'Use when...' clause and could benefit from more natural trigger terms that users would actually say when needing this functionality.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user wants to review a PR, work on multiple branches simultaneously, or needs isolated development environments'
Include common trigger term variations like 'PR', 'code review', 'parallel branches', 'isolated checkout', or 'separate working directory'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (git worktree) and mentions two actions (create or reuse), but lacks comprehensive detail about what specific operations are performed beyond basic worktree management. | 2 / 3 |
Completeness | Describes what it does (create/reuse worktrees for PRs or branches) and implies when (for reviews and isolated work), but lacks an explicit 'Use when...' clause with clear trigger guidance. | 2 / 3 |
Trigger Term Quality | Includes relevant terms like 'git worktree', 'pull request', 'branch', and 'reviews', but misses common variations users might say like 'PR', 'checkout', 'isolated environment', or 'parallel development'. | 2 / 3 |
Distinctiveness Conflict Risk | Git worktree is a specific niche feature distinct from general git operations. The focus on worktrees for PR isolation creates clear differentiation from other git-related skills. | 3 / 3 |
Total | 9 / 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 a well-crafted skill that efficiently guides Claude through git worktree setup with clear decision logic for various scenarios. It excels at providing executable commands, handling edge cases (existing worktrees, branch conflicts), and includes proper validation steps. The structure is clean and the content respects Claude's intelligence without over-explaining.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, providing only necessary information without explaining basic git concepts. Every section serves a clear purpose with no padding or unnecessary context. | 3 / 3 |
Actionability | Provides specific, executable commands throughout (mkdir -p, git worktree add, gh pr checkout, etc.) with concrete examples like the path example. Commands are copy-paste ready with clear variable substitution patterns. | 3 / 3 |
Workflow Clarity | Clear 4-step sequence with explicit validation (pwd check after cd), decision trees for existing worktrees, and user confirmation flow via AskUserQuestion. Includes explicit error handling and stop conditions for branch conflicts. | 3 / 3 |
Progressive Disclosure | For a skill of this scope (~60 lines, single focused task), the content is well-organized with clear sections. No external references needed; the hierarchical structure with numbered steps and nested conditionals is appropriate and easy to navigate. | 3 / 3 |
Total | 12 / 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 | |
Table of Contents
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.