CtrlK
BlogDocsLog inGet started
Tessl Logo

ce-worktree

Set up isolated git worktrees — create a new branch for fresh work, or attach a worktree to an existing branch, PR, or commit. Use when starting isolated work or isolating an existing ref.

73

Quality

90%

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

SKILL.md
Quality
Evals
Security

Quality

Content

92%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.

An excellent instruction-only skill body: every step carries non-obvious operational gotchas, commands are copy-paste ready across all modes, and the workflow includes validation and explicit error-recovery paths. The only weakness is slight repetition in the final paragraph about host question tools.

DimensionReasoningScore

Conciseness

Lean and dense with genuinely non-obvious operational knowledge (absolute-vs-relative git-dir mixing, trailing-slash check-ignore probe, one-branch-one-worktree rule) rather than concepts Claude already knows, but the closing paragraph repeats its point about host tool discovery twice and could be trimmed, matching the minor-trimmable-instances anchor.

4 / 5

Actionability

Fully executable, placeholder-complete commands cover every mode: `git rev-parse --absolute-git-dir`, `git worktree add -b <branch-name> .worktrees/<branch-name> origin/<from-branch>`, `git fetch origin pull/<n>/head:pr-<n>`, and the detached-then-`gh pr checkout <n>` variant, plus concrete detection and cleanup commands.

5 / 5

Workflow Clarity

Explicit order of operations (detect -> native tool -> git fallback) with a clear decision tree, validation before creation (`git check-ignore -q .worktrees/`), a "Done when" checkpoint, and error-recovery loops for already-checked-out refs and sandbox/permission failures that report and offer options rather than retrying.

5 / 5

Progressive Disclosure

The skill is under 50 lines, single-purpose, and needs no external references; its sections (Step 0/1/2, the two modes, the done-when statement) are well-organized and easy to navigate, satisfying the simple-skill exception.

5 / 5

Total

19

/

20

Passed

Description

87%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.

A strong description: concise, in third person, with concrete actions covering both operation modes and an explicit "Use when" trigger clause. Trigger terms are natural and the niche is clearly distinct from related git skills.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions — "create a new branch for fresh work", "attach a worktree to an existing branch, PR, or commit" — with only minor coverage gaps (no mention of detection or cleanup verbs), matching the several-specific-actions anchor rather than fully comprehensive coverage.

4 / 5

Completeness

Explicitly answers both: "what" via concrete action verbs ("Set up isolated git worktrees — create a new branch... or attach a worktree...") and "when" via the trigger phrase "Use when starting isolated work or isolating an existing ref", matching the anchor for both clearly present with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural terms users would say ("git worktrees", "branch", "PR", "isolated work", "existing ref") alongside an explicit "Use when" trigger clause, but misses common synonyms such as "parallel checkout" or "second working directory".

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (git worktree isolation) with distinct, unambiguous triggers; overlap risk with generic git-branch skills is minimal because the description is scoped to isolated worktrees specifically.

5 / 5

Total

18

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
EveryInc/compound-engineering-plugin
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.