CtrlK
BlogDocsLog inGet started
Tessl Logo

worktree-hygiene

Reap merged git worktrees and branches safely across the warp, codex, opencode, and conductor harnesses. Use when worktrees pile up, after a branch merges, when cleaning up `git worktree list`, removing an orphaned or detached worktree, or deciding whether a worktree is safe to delete. Not for creating branches or authoring commits (use the git skill).

69

Quality

85%

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 dense, executable procedure for a destructive operation, with strong validation gates and feedback loops that justify a high workflow-clarity score. The only soft dimension is progressive disclosure, where the skill is self-contained with no external references to structure.

DimensionReasoningScore

Conciseness

Lean and assumes git competence (no basics explained), with tight code blocks and decision tables; a few justifying sentences like the merge-base containment note are slightly more than minimal but earn their place, keeping it just below a 5.

4 / 5

Actionability

Fully executable: a complete copy-paste audit bash script, exact per-worktree reap commands ('git worktree remove <path>; git branch -d/-D <branch>'), and concrete recovery commands ('git worktree prune', 'rm -rf <path>') cover the common cases.

5 / 5

Workflow Clarity

Clear sequence (signal → audit → decide → gate → final checks) with explicit validation checkpoints and feedback loops — re-run the audit, never reap on self-report, approve-list before destructive commands — satisfying the destructive/batch validation requirement rather than hitting the cap of 3.

5 / 5

Progressive Disclosure

Single self-contained file with well-organized, clearly headed sections and one-level-deep Related Skills links; no bundle files exist to reference, and the body slightly exceeds the under-50-lines simple-skill threshold, so it stops short of a 5.

4 / 5

Total

18

/

20

Passed

Description

82%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 well-crafted description with explicit what/when triggers and a clear negative boundary against the sibling git skill. Its only weak spot is specificity, which rests on a single action verb rather than an enumerated action list.

DimensionReasoningScore

Specificity

Names the domain (git worktrees/branches) and the core concrete action ('Reap merged git worktrees and branches safely') but coverage is essentially one action verb rather than a comprehensive list; it does not reach the multiple-specific-actions bar of a 5.

3 / 5

Completeness

Explicitly answers both what ('Reap merged git worktrees and branches safely across... harnesses') and when ('Use when worktrees pile up, after a branch merges...') with concrete trigger phrases, plus a negative boundary clause.

5 / 5

Trigger Term Quality

Strong natural triggers — 'worktrees pile up', 'after a branch merges', 'cleaning up git worktree list', 'orphaned or detached worktree', 'safe to delete' — are phrases a user would actually say; just shy of comprehensive synonym/extension coverage for a 5.

4 / 5

Distinctiveness Conflict Risk

Clear niche (worktree/branch reaping) with an explicit disambiguator — 'Not for creating branches or authoring commits (use the git skill)' — minimizing conflict with the related git 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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 3 suspicious

Warning

Total

15

/

16

Passed

Repository
EpicenterHQ/epicenter
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.