CtrlK
BlogDocsLog inGet started
Tessl Logo

he-prune-branches

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

59

Quality

68%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./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

62%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill has strong workflow clarity with a well-sequenced procedure, explicit confirmation gates, and validation checkpoints appropriate for destructive operations. Its main weaknesses are incomplete actionability (vague inputs/outputs, missing script bundle, no concrete output schema example) and moderate conciseness issues with some low-value sections. The structure is reasonable but would benefit from providing the referenced script and a concrete output example.

Suggestions

Provide the referenced script `clean-gone` in the bundle or inline its logic so the skill is self-contained and fully actionable.

Replace the vague 'Inputs' and 'Outputs' sections with a concrete example showing actual input context and the expected structured output JSON schema.

Remove the 'Full Context' section listing icon assets, as it adds no instructional value to the skill.

DimensionReasoningScore

Conciseness

Generally efficient but includes some sections that could be tightened—'Inputs' is vague and adds little value, 'Full Context' listing icon assets is irrelevant to the skill's purpose, and 'Examples' are natural language prompts rather than concrete input/output pairs. The Failure Modes and Anti-Patterns sections are useful but slightly verbose.

2 / 3

Actionability

The procedure references a concrete script path and provides executable bash commands for worktree/branch deletion, which is good. However, the script itself is not provided in the bundle, the 'Inputs' section is entirely vague ('Request, artifacts, repo context'), and the 'Outputs' section describes a schema without showing its actual structure. Key details like how to verify PR status (mentioned in examples) are missing.

2 / 3

Workflow Clarity

The procedure is clearly sequenced with explicit validation checkpoints: discovery → check for __NONE__ → present candidates → single confirmation gate → worktree removal before branch deletion → report outcomes. The Validation section adds a fail-fast gate and specific checks (active branch protection, root worktree protection). The feedback loop for partial failures is explicitly addressed.

3 / 3

Progressive Disclosure

The content is well-structured with clear section headers and logical organization. However, no bundle files are provided despite referencing a script path, and the 'Full Context' section references icon assets that don't contribute to the skill. The skill is moderately long but keeps everything inline rather than splitting detailed validation or anti-patterns into separate references.

2 / 3

Total

9

/

12

Passed

Description

75%

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 has good structure with an explicit 'Use when...' clause and a distinctive niche, but the specificity of concrete actions is limited and trigger terms could be expanded to cover more natural user phrasings. The 'when' clause lists conditions rather than user-facing trigger terms, which slightly weakens discoverability.

Suggestions

Add more concrete actions such as 'list branches by last commit date, check merge status, identify unmerged work, generate safe delete commands'.

Include additional natural trigger terms users might say, such as 'git branches', 'old branches', 'delete branches', 'merged branches', 'remote branches', 'branch management'.

DimensionReasoningScore

Specificity

It names the domain (branch cleanup) and some actions ('review and prune stale branches'), but lacks concrete specifics about what actions are performed—e.g., listing branches by age, checking merge status, generating delete commands. 'Non-destructive recommendations' is somewhat vague.

2 / 3

Completeness

It answers both 'what' (review and prune stale branches safely) and 'when' (Use when branch cleanup needs evidence, protected-branch caution, PR awareness, and non-destructive recommendations), with an explicit 'Use when...' clause.

3 / 3

Trigger Term Quality

Includes relevant terms like 'branches', 'branch cleanup', 'stale branches', and 'PR', but misses common natural variations users might say such as 'git branches', 'old branches', 'delete branches', 'merged branches', or 'remote branches'.

2 / 3

Distinctiveness Conflict Risk

The description carves out a clear niche—stale branch pruning with specific qualifiers (protected-branch caution, PR awareness, non-destructive). This is unlikely to conflict with general git skills or other repository management skills.

3 / 3

Total

10

/

12

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

10

/

11

Passed

Repository
jscraik/Agent-Skills
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.