CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

worktree-cleanup

Prune merged feature worktrees, fast-forward the root checkout's main from origin/main, reinstall deps, 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

89%

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 exemplary script-orchestration skill body: lean, concrete, with explicit dry-run validation and error handling for a destructive operation, and well-organized for its size. The only notable gap is that the bundled executable it drives is absent from the skill bundle, leaving the body to coordinate rather than implement the mechanics.

Suggestions

Bundle scripts/worktree-cleanup.sh (or summarize its behavior and flags in the body) so the skill's guidance is fully executable from the skill alone.

Clarify step 2's pause logic — specify exactly when to pause for operator confirmation versus proceeding (e.g., an explicit 'proceed only after the operator confirms the dry-run output' condition).

DimensionReasoningScore

Conciseness

The 42-line body is lean: every section (What this does, Hard rules, Procedure, What 'merged' means, Cross-references) earns its place, explains nothing Claude already knows, and cites ADRs by number without re-explaining them. No trimming opportunities identified.

5 / 5

Actionability

Concrete, copy-paste-ready commands (`scripts/worktree-cleanup.sh --dry-run`), specific diary-edit instructions including the empty-case text, and precise merged-detection criteria with the exact `gh pr list --head <branch> --state merged` fallback. Not 5 because the core git mechanics are delegated to an external script not present in the skill bundle, so the body alone cannot execute the actual cleanup operation.

4 / 5

Workflow Clarity

Clear four-step sequence with explicit validation for a destructive operation: dry-run first and show the operator, hard rules handling the dirty-root error case ('surface that to the operator'), and a report step covering main before/after, removed worktrees, and 'worktrees kept and why' as a feedback loop. The destructive-operation cap does not apply because validation checkpoints are explicit.

5 / 5

Progressive Disclosure

Under 50 lines with well-organized sections and no external references needed; per the simple-skill exception this warrants a 5. The pointers that do exist (scripts/worktree-cleanup.sh, docs/diary.md header protocol, ADR cross-references) are clearly signaled and one level deep.

5 / 5

Total

19

/

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: concrete, comprehensive, third-person, and tied to a distinct niche with explicit slash-command invocation. The main gap is the absence of natural-language situational trigger phrases and synonyms that would push trigger quality and completeness to the top anchor.

Suggestions

Add a 'when' clause naming the situations that call for the skill, e.g., 'Use after a PR merges or when worktree branches accumulate.'

Include natural user phrasings like 'clean up worktrees' or 'delete merged worktrees' alongside the slash-command invocation to broaden trigger coverage.

DimensionReasoningScore

Specificity

"Prune merged feature worktrees, fast-forward the root checkout's main from origin/main, reinstall deps, and refresh the 'Active worktrees' row in docs/diary.md" lists four concrete, comprehensive actions in third person. Not 4 because coverage of the skill's behavior is complete, including the safety posture ("never removes dirty or unmerged worktrees").

5 / 5

Completeness

The 'what' is explicit and concrete, and "Invoke as `/worktree-cleanup`" provides explicit trigger guidance (avoiding the cap), so both parts are answered. Not 5 because no situational 'when' phrasing exists (e.g., 'use after a PR merges' or 'when the user asks to clean up worktrees'); not 3 because invocation guidance is explicit rather than merely implied.

4 / 5

Trigger Term Quality

Natural keywords present ("worktrees", "merged", "prune", "main", "--dry-run") that a user needing this skill would plausibly say. Not 5 because common variations like "clean up worktrees", "delete worktrees", or "git worktree" are absent.

4 / 5

Distinctiveness Conflict Risk

The description targets a narrow niche (merged worktree pruning, root-checkout sync, diary row refresh) tied to repo-specific conventions. Distinct triggers via the `/worktree-cleanup` slash command; minimal overlap with any general-purpose skill.

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/ai-report-platform

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.