CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

he-prune-branches

Review and prune stale branches safely. Use when branch cleanup needs evidence, protected-branch caution, PR awareness, and non-destructive recommendations.

Quality

72%

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

Fix and improve this skill with Tessl

tessl review fix ./Plugins/harness-engineering/fixtures/budget-archive/2026-04-21/deferred-store/skills/team_automation/he-prune-branches/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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.

The body is a lean, well-sectioned runbook with explicit confirmation and fail-fast validation for a destructive batch operation — stronger than typical. Its main gaps are mechanical: the referenced discovery script and asset files are absent from the bundle, and the per-branch deletion block omits the branch-to-worktree mapping and conditional guards that the surrounding prose promises.

Suggestions

Ship the discovery script in the skill's scripts/ directory (or inline the git commands it wraps, e.g. `git branch -vv` / `git for-each-ref` filtering for gone upstreams) so the core step is executable from the bundle.

Show how to resolve a branch to its worktree path (e.g. `git worktree list --porcelain`) and make non-root-worktree exclusion a condition on the `git worktree remove` command instead of relying on step 7 prose.

Remove or honor the dangling asset links and the reference pointer; either add the files or drop the "Full Context" section and the "Use references only..." line so every path in SKILL.md resolves.

DimensionReasoningScore

Conciseness

The body is terse and imperative throughout with zero explanation of git concepts Claude already knows. It is not a 5 because the confirmation rule is restated across Philosophy, Procedure, Validation, Constraints, and Anti-Patterns, and the "Inputs" section ("Request, artifacts, repo context, and linked Linear issues") adds almost no value.

4 / 5

Actionability

Concrete, executable commands are given for every phase (discovery script invocation, `git worktree list`, `git worktree remove --force "<worktree_path>"`, `git branch -D "<branch>"`). It is not a 5 because the core discovery script is not shipped in the bundle, and how to map a candidate branch to its `<worktree_path>` is never shown, leaving the deletion block not fully copy-paste ready.

4 / 5

Workflow Clarity

The numbered procedure has real validation checkpoints (`__NONE__` exit, one yes/no gate before any destructive action, a dedicated fail-fast Validation checklist) plus failure-mode recovery including continuing after a per-branch failure. It is not a 5 because the per-branch block runs `git worktree list` inside the loop and applies `--force` unconditionally, leaving the root-worktree and active-branch guards as post-hoc prose in steps 7 and Validation rather than explicit conditions in the destructive sequence.

4 / 5

Progressive Disclosure

Sections are well-organized, but scored against the actual bundle structure the references do not resolve: there is no scripts/, references/, or assets/ directory, so `Plugins/harness-engineering/.../scripts/clean-gone`, `./assets/icon-small.png`, and `./assets/icon-large.png` are dangling, and "Use references only when additional edge handling is needed" points at nothing. This matches the anchor for structure present but references not clearly backed/organized.

3 / 5

Total

15

/

20

Passed

Description

62%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.

The description answers both what and when with a serviceable trigger clause, and it uses third person without padding. Its weaknesses are a thin action list (only review and prune) and a when-clause framed as cleanup qualities rather than natural user phrases, which limits trigger coverage and distinctiveness.

Suggestions

Expand the what-clause with the skill's other concrete actions, e.g. "remove associated worktrees and delete confirmed branches in one batch".

Rewrite the when-clause around situations users actually describe, e.g. "Use when asked to clean up stale local branches, delete branches whose remote tracking refs are gone, or remove old worktrees".

Include the words "git" and "local" so the skill is distinguishable from remote branch or PR management skills.

DimensionReasoningScore

Specificity

"Review and prune stale branches safely" names the domain and two concrete actions, but coverage stops there — worktree cleanup, batch confirmation, and deletion reporting are not mentioned. It is not a 4 because the remaining phrases ("protected-branch caution", "non-destructive recommendations") are qualifiers, not additional concrete actions.

3 / 5

Completeness

Both parts are present: a clear what ("Review and prune stale branches safely") and an explicit "Use when..." clause. It is not a 5 because the when-clause describes qualities of the cleanup rather than concrete user situations or trigger phrases, so it could be more explicit.

4 / 5

Trigger Term Quality

Natural phrases like "prune stale branches" and "branch cleanup" are present, but common variations users would actually say are missing: "delete", "local branches", "merged", "old", or "git". It is not a 4 because the when-clause conditions ("evidence", "PR awareness", "non-destructive recommendations") are not language a user would naturally utter.

3 / 5

Distinctiveness Conflict Risk

Branch pruning with safety emphasis is a fairly distinct niche with minor overlap risk against generic git-cleanup or repo-hygiene skills. It is not a 5 because "branches" and "PR awareness" alone could collide with merged-branch-deletion or PR-management skills since "git" and "local" are never stated.

4 / 5

Total

14

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

relative_links

Relative link issues: 2 missing

Warning

Total

14

/

16

Passed

Repository

jscraik/Agent-Skills

Path

Plugins/harness-engineering/fixtures/budget-archive/2026-04-21/deferred-store/skills/team_automation/he-prune-branches/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.