worktree-from-issue
Create a git worktree with a new branch for implementing a fix or feature for a GitHub issue
77
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 identifies a specific technical capability (git worktree creation for GitHub issues) but lacks completeness due to missing explicit trigger guidance. It would benefit from a 'Use when...' clause and additional trigger terms that users would naturally say when needing this functionality.
Suggestions
Add a 'Use when...' clause with trigger phrases like 'work on issue', 'start implementing issue #', 'create worktree for issue', or 'parallel development'
Include common user phrasings such as 'work on GitHub issue in isolation', 'separate workspace for feature', or 'worktree for PR'
Expand specific actions to include related capabilities like 'sets up isolated workspace' or 'links branch to issue number'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (git worktree) and a specific action (create with new branch for GitHub issue), but doesn't list multiple concrete actions or variations of what can be done. | 2 / 3 |
Completeness | Describes what it does (create git worktree with new branch for GitHub issue) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes relevant keywords like 'git worktree', 'branch', 'GitHub issue', 'fix', 'feature', but missing common variations users might say like 'work on issue', 'start feature', 'parallel development', or 'isolated branch'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'git worktree' and 'GitHub issue' is fairly specific, but could overlap with general git branching skills or GitHub issue management skills without clearer boundaries. | 2 / 3 |
Total | 7 / 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 setting up a git worktree for issue implementation. It demonstrates excellent workflow clarity with numbered steps, validation checkpoints, and clear delegation to related skills. The branch naming convention is concrete with regex validation and multiple examples.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, providing only necessary information without explaining concepts Claude already knows. Every section serves a clear purpose with no padding or unnecessary context. | 3 / 3 |
Actionability | Provides concrete, executable commands and clear patterns. The branch naming regex, gh CLI commands, and git commands are all copy-paste ready with specific examples. | 3 / 3 |
Workflow Clarity | Clear 7-step sequence with explicit validation checkpoints: verifying issue exists (step 2), verifying cwd after setup (step 6), and clear error handling guidance. The workflow includes a feedback loop for cwd verification. | 3 / 3 |
Progressive Disclosure | Appropriately delegates to other skills (/create-worktree, /worktree-make-dev) rather than duplicating content. References are one level deep and clearly signaled. The skill stays focused on its specific task. | 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 | |
- 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.