CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

worktree-cleanup

Prune merged feature worktrees, fast-forward the root checkout's base branch, run the project's post-sync command, and refresh the "Active worktrees" row in docs/diary.md. Invoke as `/worktree-cleanup` (or `/worktree-cleanup --dry-run` to preview). Conservative — never removes dirty or unmerged worktrees.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

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

A tightly written, well-structured instruction skill: concrete commands, explicit safety rules, a sensible dry-run checkpoint, and project-specific edge-case knowledge (the squash-merge ancestry caveat) that genuinely adds value. The main gap is external: the script the whole procedure depends on is not part of the reviewed bundle, and the diary/report outputs lack worked examples.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence: it never explains what git worktrees or fast-forwarding are, and every section carries project-specific information Claude could not infer (hard rules, the two-test merged predicate, env vars and where to persist them). The few rationale sentences (e.g., the merge-reconciliation tax) justify the constraints rather than pad, matching the 'every token earns its place' anchor.

5 / 5

Actionability

The procedure gives copy-paste-ready commands ("sh scripts/worktree-cleanup.sh --dry-run", "sh scripts/worktree-cleanup.sh") plus concrete instructions for the diary edit and report contents. It stops short of the top anchor because the diary row edit and the report step are described but not exemplified (no sample row or summary block format), and the referenced script is not present in the reviewed bundle to confirm executability.

4 / 5

Workflow Clarity

The sequence is explicit with validation checkpoints appropriate to a destructive batch operation: dry-run preview shown to the operator first, an error-recovery path ("If the script reports the root as dirty, surface that to the operator; don't stash or commit"), the script's own skipping of dirty/unmerged worktrees, and a closing report of base before → after, removed, and kept-and-why. This satisfies the feedback/checkpoint expectations the rubric reserves for the top anchor.

5 / 5

Progressive Disclosure

Sections are well organized and the git mechanics are appropriately split into a one-level-deep, clearly signaled reference ("The git mechanics live in `scripts/worktree-cleanup.sh`") with no nested reference chains. It does not reach 5 because the referenced script (and any references/ or scripts/ files) is absent from the bundle as provided, so the primary external reference cannot be verified, and cross-references point to project files outside the skill bundle.

4 / 5

Total

18

/

20

Passed

Description

83%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: it enumerates the full procedure as concrete third-person actions, states an explicit invocation trigger with a dry-run variant, and delineates a safety boundary that makes the skill highly distinguishable. The only improvement space is adding natural-language situational triggers and synonyms beyond the slash-command name.

DimensionReasoningScore

Specificity

The description lists four concrete, distinct actions — "Prune merged feature worktrees", "fast-forward the root checkout's base branch", "run the project's post-sync command", "refresh the 'Active worktrees' row in docs/diary.md" — which comprehensively cover the skill's procedure. This matches the anchor for multiple specific concrete actions with comprehensive coverage, not the level below (which allows minor gaps).

5 / 5

Completeness

The 'what' is explicit and detailed, and the 'when/how' is addressed via "Invoke as `/worktree-cleanup` (or `/worktree-cleanup --dry-run` to preview)" — explicit trigger guidance equivalent to a 'Use when' clause for a command-style skill. It is not a 5 because no concrete situational trigger phrase (e.g., "use after a pull request merges") is given; it is not a 3 because explicit invocation guidance is present rather than merely implied.

4 / 5

Trigger Term Quality

Strong natural domain keywords are present ("worktrees", "merged", "prune", "cleanup" via the command name, "dry-run", "base branch"), giving good coverage a user would plausibly say. It falls short of the top anchor because common synonyms and variations (e.g., "remove/delete old worktrees", "clean up after a merge") are missing, but it is well above the 'some relevant keywords, missing variations' anchor.

4 / 5

Distinctiveness Conflict Risk

"Prune merged feature worktrees" plus the boundary statement "Conservative — never removes dirty or unmerged worktrees" carves out a clear niche with distinct triggers and minimal conflict risk with other skills. No neighboring skill domain plausibly overlaps this exact lifecycle-cleanup job.

5 / 5

Total

18

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 possibly missing (scripts/worktree-cleanup.sh)

Warning

Total

15

/

16

Passed

Repository

agranado2k/google-books-clojure

Path

.claude/skills/worktree-cleanup/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.