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

85%

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

90%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 lean, highly actionable skill body that assumes Claude's competence while supplying only repo-specific knowledge, with a conservative dry-run-first workflow appropriate to its destructive nature. The only structural improvement would be a post-run verification step for the diary edit and slightly tighter reference navigation.

DimensionReasoningScore

Conciseness

Every section carries project-specific facts Claude cannot know (the AGENTS.md lifecycle rule, the diary update protocol, env var defaults and their rationale) with no generic git or worktree concept explanations and no padding — every token earns its place.

5 / 5

Actionability

Copy-paste-ready commands ('sh scripts/worktree-cleanup.sh --dry-run', 'sh scripts/worktree-cleanup.sh'), documented env vars with defaults, and exact diary-edit semantics including the 'already stale' edge case fully cover the common cases.

5 / 5

Workflow Clarity

For a destructive/batch skill, validation is present — a mandatory dry-run shown to the operator, conservative script behavior, an explicit dirty-root error path, and a report step — so the score-3 cap does not apply; however there is no post-run verification of the diary edit, leaving a minor checkpoint gap between anchors 4 and 5.

4 / 5

Progressive Disclosure

Well-organized sections with git mechanics correctly delegated to scripts/worktree-cleanup.sh and all cross-references (AGENTS.md, docs/diary.md, /merge-train, constitution/local-workflow.md) one level deep and clearly signaled; at ~75 lines with all instructional content inline rather than split into navigable reference files, it sits just below the anchor-5 structure.

4 / 5

Total

18

/

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, distinctive description that clearly enumerates what the skill does, undermined only by the absence of explicit when-to-use trigger guidance and a few natural keyword synonyms. Adding a 'Use when...' clause would raise completeness to the top band.

Suggestions

Add an explicit trigger clause, e.g. 'Use when a pull request has just merged or when the "Active worktrees" row in docs/diary.md is stale.'

Include natural synonyms users would actually say, such as 'remove', 'delete', or 'clean up' merged worktrees, and 'sync the base branch'.

State the timing context (after a merge lands) in the description itself so the 'when' is explicit rather than implied by the command name.

DimensionReasoningScore

Specificity

Four distinct concrete actions are listed — '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' — giving comprehensive coverage of the skill's behavior with no gaps.

5 / 5

Completeness

The 'what' is explicit and concrete, but there is no 'Use when...' clause or equivalent trigger guidance — 'Invoke as /worktree-cleanup' is invocation syntax, not when-to-use guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Natural phrases like 'prune merged feature worktrees' and '--dry-run to preview' are present, but common user variations such as 'remove/delete worktrees', 'clean up', or 'sync the base branch' are missing.

4 / 5

Distinctiveness Conflict Risk

A clear niche (post-merge worktree lifecycle for this repo kit) with unique artifacts like docs/diary.md and the /worktree-cleanup command name; minimal conflict risk with any other skill.

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-haskell

Path

.agents/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.