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

82%

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

The canonical home for this skill is worktree-cleanup in agranado2k/google-books-clojure

SKILL.md
Quality
Evals
Security

Quality

Content

82%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 well-structured, actionable skill body: exact commands, explicit safety guardrails, documented configuration, and a clear procedure with a dry-run checkpoint. The only notable issues are minor — slightly ambiguous dry-run skip conditions, small narrative padding, and a script reference that is not present in the bundle as provided.

DimensionReasoningScore

Conciseness

The body is efficient and assumes competence — it documents only project-specific facts (diary protocol, env vars, squash-merge rationale) rather than concepts Claude already knows. Minor narrative flourishes like "Closes the lifecycle the root AGENTS.md's first hard rule opens" and "pays a merge-reconciliation tax later" could be trimmed, so it fits 'efficient; minor instances of over-explanation' rather than the every-token-earns-its-place bar of a 5.

4 / 5

Actionability

Gives copy-paste-ready commands ("sh scripts/worktree-cleanup.sh --dry-run", "sh scripts/worktree-cleanup.sh"), exact env vars with defaults, and a concrete diary-edit rule including the empty case ("or 'None.' if empty"). As an instruction-only skill whose guidance is fully executable and covers the common cases, it matches the top anchor.

5 / 5

Workflow Clarity

The four-step procedure is clearly sequenced with an explicit dry-run checkpoint and error-path handling ("If the script reports the root as dirty, surface that to the operator"; stale diary row handling), so the destructive-operation cap does not apply. It falls short of a 5 because the step-2 parenthetical "skip step 1's pause if the operator invoked the skill with a clear 'clean up' intent" introduces ambiguity about when the dry-run checkpoint is mandatory, and there is no post-run verification of the diary edit.

4 / 5

Progressive Disclosure

Sections are well-organized and the split is appropriate — "The git mechanics live in scripts/worktree-cleanup.sh" delegates mechanics one level deep while the SKILL.md holds policy, with a clear Cross-references section. However, no scripts/ (or references/, assets/) directory exists in the bundle, so the referenced script path is dangling as presented — a minor organization gap that keeps this at 'good structure; most content appropriately placed' rather than a 5.

4 / 5

Total

17

/

20

Passed

Description

75%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 highly specific, well-scoped description with comprehensive concrete actions and minimal conflict risk. Its main weakness is the absence of an explicit 'Use when...' trigger clause — it states how to invoke but not when the skill applies — which caps completeness and leaves a few natural trigger phrasings uncovered.

Suggestions

Add an explicit trigger clause, e.g., "Use when a feature PR has merged and its worktree is left behind, when the root checkout's base branch is stale, or when the diary's 'Active worktrees' row needs refreshing after a merge."

Include natural phrasing variations users would actually say, such as "clean up worktrees", "remove old/stale worktrees", or "git worktree prune", to strengthen trigger matching.

State the timing context explicitly (e.g., "typically run after a merge batch lands, as /merge-train's final step") so the 'when' is stated rather than implied.

DimensionReasoningScore

Specificity

"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" lists four concrete actions covering the skill's full lifecycle. This matches the anchor for multiple specific concrete actions with comprehensive coverage; score 4 would require minor gaps in coverage, which are absent.

5 / 5

Completeness

The 'what' is explicit and thorough, but the only usage guidance is "Invoke as /worktree-cleanup (or /worktree-cleanup --dry-run to preview)", which is invocation syntax rather than an explicit trigger clause. Per the rubric guideline, a missing 'Use when...' clause or equivalent trigger guidance caps completeness at 3; it is not a 4 because 'when' is at best weakly implied by the skill's name.

3 / 5

Trigger Term Quality

Includes natural terms users would say — "worktree", "prune", "merged", "dry-run" — plus the /worktree-cleanup invocation. A few natural phrasings are missing (e.g., "clean up worktrees", "remove stale/old worktrees"), so it fits 'good keyword coverage; a few natural terms missing' rather than the comprehensive synonym coverage of a 5.

4 / 5

Distinctiveness Conflict Risk

"Prune merged feature worktrees", "the root checkout's base branch", and "refresh the 'Active worktrees' row in docs/diary.md" carve out a clear post-merge cleanup niche with distinct triggers and virtually no overlap risk with other skills. This matches the anchor for a clear niche with minimal conflict risk.

5 / 5

Total

17

/

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/tic-tac-toe-with-agentic-sdlc

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.