CtrlK
BlogDocsLog inGet started
Tessl Logo

switch-worktree

Switch the current session to work in an existing git worktree

60

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/switch-worktree/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a tight, well-structured workflow with concrete commands and explicit validation checkpoints, scoring near the top; the only gap is unresolved path placeholders and the absence of an error-recovery loop.

DimensionReasoningScore

Conciseness

The body is lean and direct with no over-explanation of what a worktree is or how git works; every line is an actionable instruction, matching 'lean and efficient; assumes Claude's competence; every token earns its place.'

5 / 5

Actionability

Provides concrete, real commands (git worktree list, cd, pwd, git branch --show-current) but leaves placeholders such as '<repo-root>' and unsubstituted 'WORKTREE'/'NAME', so it is not fully copy-paste ready — fitting 'mostly executable guidance; minor gaps' rather than the fully executable score 5.

4 / 5

Workflow Clarity

A clear three-step sequence (Resolve, Switch cwd, Report) with explicit validation stops in steps 1 and 2, but the validation 'stop with an error' lacks a fix-and-retry feedback loop, so it falls short of the score 5 anchor.

4 / 5

Progressive Disclosure

A sub-50-line, single-purpose skill with no need for external references and clean section organization (## Steps, numbered ### subsections), which the simple-skill exception allows to score 5 on progressive disclosure.

5 / 5

Total

18

/

20

Passed

Description

53%Weight 40%Scale 1-5

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 concise and clearly names a distinct niche, but it omits any explicit 'Use when...' trigger guidance and offers only a single concrete action, leaving it mid-pack on completeness and trigger coverage.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user wants to switch the session into an existing git worktree.'

Mention natural variations such as 'git worktree' and 'change directory / cd into worktree' to broaden trigger-term coverage.

Optionally note a second concrete action (e.g. listing worktrees when no name is given) to lift specificity toward 4-5.

DimensionReasoningScore

Specificity

Names the domain (git worktree) and one concrete action ('Switch the current session to work in an existing git worktree'), matching the '1-2 concrete actions, not comprehensive' anchor rather than the multi-action list of score 4 or the generic single action of score 2.

3 / 5

Completeness

Clearly states what the skill does but provides no 'Use when...' clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

Includes natural terms 'worktree' and 'switch', but lacks common variations such as 'git worktree', 'change directory', or 'cd into worktree', fitting 'some relevant keywords but missing common variations' rather than the broader coverage of score 4.

3 / 5

Distinctiveness Conflict Risk

Targets a clear niche (switching to an existing worktree) with only minor overlap risk against related worktree create/manage skills; not 5 because it lacks explicit trigger phrases that would fully minimize conflict.

4 / 5

Total

13

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
dlt-hub/dlt
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.