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

87%

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

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 well-structured, highly actionable procedure body: executable commands in every step, an explicit dry-run validation gate before destructive action, and clear delegation of mechanics to the script. The only weaknesses are slight narrative padding and an inline conceptual section that pushes past the ideal lean-overview structure.

DimensionReasoningScore

Conciseness

Nearly all content is project-specific (the kit's lifecycle, the script's keep/prune semantics, diary protocol) that Claude could not know, so no tokens are spent re-teaching known concepts. Minor narrative flourishes ("Closes the lifecycle the root AGENTS.md's first hard rule opens", "pays a merge-reconciliation tax") could be trimmed, fitting the efficient-with-minor-over-explanation anchor rather than the every-token-earns-its-place anchor at 5.

4 / 5

Actionability

Every step carries copy-paste-ready commands — `sh scripts/worktree-cleanup.sh --dry-run`, the real run, and a fully parameterized `sh scripts/trace.sh emit kind=worktree.prune ... || :` line — plus a concrete diary-edit instruction with the "None." empty-case. Specific executable guidance covers the common cases, matching the fully-executable anchor.

5 / 5

Workflow Clarity

Four steps clearly sequenced with an explicit validation checkpoint up front (dry-run and show the operator), error-recovery paths (dirty root surfaced rather than stashed, stale diary row reported in a dated entry), and per-worktree outcome reporting. Because this is a destructive/batch operation, the missing-validation cap was checked and does not apply — validation is present at multiple points.

5 / 5

Progressive Disclosure

The git mechanics are appropriately delegated to `scripts/worktree-cleanup.sh` and all references (script, AGENTS.md, docs/diary.md, constitution file, /merge-train) are clearly signaled one level deep. Minor gaps: the "What 'merged' means here" section carries reference-style semantic detail inline, and the bundle itself contains no supporting files, so the referenced scripts cannot be verified as navigable resources. Fits the good-structure-with-minor-gaps anchor rather than the ideal split at 5.

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 specific, distinctive description that names concrete actions and explicit invocation syntax. Its main weakness is the absence of a "Use when..." trigger clause spelling out the condition under which the skill is needed, leaving the "when" to be inferred from "merged feature worktrees".

DimensionReasoningScore

Specificity

Lists four concrete, specific 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" — with a named file path and a behavior guarantee ("never removes dirty or unmerged worktrees"). This matches the comprehensive-coverage anchor and exceeds the several-actions-with-minor-gaps anchor below it.

5 / 5

Completeness

The "what" is explicit (four named actions) and "when/how" guidance exists via "Invoke as `/worktree-cleanup` (or `/worktree-cleanup --dry-run` to preview)", but the triggering condition (post-merge cleanup need) is implied rather than stated in a "Use when..." clause. Fits the both-present-but-when-could-be-more-explicit anchor, not the fully explicit concrete-trigger-phrases anchor at 5.

4 / 5

Trigger Term Quality

Good natural keyword coverage (worktree, merged, prune, dry-run, base branch, fast-forward) that a kit user would plausibly say, but common variations like "clean up worktrees" or "remove worktree" are absent. Not 5 because synonym coverage is not comprehensive; not 3 because the terms present go well beyond "some relevant keywords".

4 / 5

Distinctiveness Conflict Risk

Clear niche — merged-worktree lifecycle cleanup tied to this kit's diary and worktree conventions — with distinct triggers unlikely to fire for any other skill. No meaningful overlap with the generic-domain anchors at 3 or below.

5 / 5

Total

18

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

metadata_version

'metadata.version' is missing

Warning

referenced_paths_exist

Referenced path issues: 2 possibly missing (scripts/trace.sh, scripts/worktree-cleanup.sh)

Warning

Total

13

/

16

Passed

Repository

agranado2k/agentic-sdlc

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.