CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

worktree

Load to create, list, remove, push, or repair a git worktree.

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/worktree/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 dense, well-structured overview that assumes Claude's intelligence, points to real reference files one level deep, and puts explicit validation gates on its destructive operations. Its main weaknesses are the absence of worked command examples for common flows and a dead reference to a missing workflows/repair-agent-links.md file.

Suggestions

Fix the broken reference: either restore workflows/repair-agent-links.md to the bundle or inline/remove the pointer in the "Recovering a broken `.agents` entry" section.

Add one copy-paste-ready example invocation for the dominant flow, e.g., `.agents/skills/worktree/scripts/worktree create ISSUE-123 --base main`, so the common case does not require a help lookup first.

Break up the longest multi-clause sentences (session-guard and merged/rebase paragraphs) into shorter statements to reduce re-reading cost.

DimensionReasoningScore

Conciseness

The body assumes Claude's competence throughout ("Every command's contract is its `--help`", exit codes 75/76 cited without explanation) and contains no padding of known concepts. It is not a 5 because several long multi-clause sentences (e.g., the session-guard paragraph and the merged/rebase policy restatements) could be tightened without losing content.

4 / 5

Actionability

Concrete guidance dominates: the exact script invocation path, a fully executable cat command for resolving the main checkout, specific flag names, and precise exit codes. It is not a 5 because no worked example invocation (e.g., `worktree create <ISSUE-ID>`) appears in the body for the most common flows; details are delegated to `--help`.

4 / 5

Workflow Clarity

The destructive workflows carry explicit validation gates: removal recovery requires proving identity, path containment, and ancestry with "Failed or unread proof stops recovery", and build-output pruning previews by default and deletes only under `--apply`. It is not a 5 because the everyday create/push sequence is deferred to `--help` and the recovery steps are prose-embedded rather than listed.

4 / 5

Progressive Disclosure

The body is a genuine overview with clearly signaled, one-level-deep references to real bundle files ([references/hooks.md](references/hooks.md) and [references/session-guard.md](references/session-guard.md) both exist, and both reference only back to SKILL.md or `--help`). It is not a 5 because [workflows/repair-agent-links.md](workflows/repair-agent-links.md) is referenced but absent from the bundle, and most command detail lives in runtime `--help` output rather than navigable files.

4 / 5

Total

16

/

20

Passed

Description

66%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, concrete, and names the right domain with natural trigger terms, but it is missing an explicit "when to use" clause and omits several major commands the body documents (restack, cleanup, merged). Adding a trigger clause and a couple of the missing capabilities would lift it substantially.

Suggestions

Add an explicit trigger clause, e.g., "Use when creating, listing, pushing, or removing git worktrees, or when repairing broken worktree links or finishing a paused restack."

Mention one or two high-value omitted capabilities such as restack completion or merged-branch cleanup so the description covers the command surface.

Add a natural synonym such as "parallel branch checkout" or "isolated working copy" to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

"Load to create, list, remove, push, or repair a git worktree" names five concrete actions (create, list, remove, push, repair), matching the anchor for several specific actions with minor coverage gaps. It is not a 5 because the body's command table exposes major capabilities (restack, cleanup, merged, check, fix-links, hook setup) that the description omits.

4 / 5

Completeness

The "what" is clear (create, list, remove, push, or repair a git worktree) but there is no "Use when..." clause or equivalent explicit trigger guidance, which the guidelines cap at 3. The "Load to..." phrasing only weakly implies when to invoke it.

3 / 5

Trigger Term Quality

"git worktree" plus the natural action verbs (create, list, remove, push, repair) are exactly what a user would say when needing this skill. It falls short of a 5 because no synonyms or related natural phrases appear (e.g., parallel branch, isolated checkout, working copy, .worktrees).

4 / 5

Distinctiveness Conflict Risk

"git worktree" names a clear, specific niche that is unlikely to trigger for unrelated skills. It is a 4 rather than 5 because the broad git action verbs (create, push, remove) leave minor overlap risk with general git-branch or PR-management skills.

4 / 5

Total

15

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 1 possibly missing (workflows/repair-agent-links.md)

Warning

Total

13

/

16

Passed

Repository

vanillagreencom/kendex

Path

.agents/skills/worktree/SKILL.md

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.