CtrlK
BlogDocsLog inGet started
Tessl Logo

cleanup

Clean the local hacs_waste_collection_schedule repository after a pull request merges. Use when a maintainer asks to clean merged branches, resync master, prune remotes, or prepare the checkout for the next ticket.

71

Quality

86%

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

86%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 tight, well-structured delegation skill: lean instructions, a copy-ready agent prompt, an explicit preserve-list, and explicit per-step confirmation requirements for destructive actions. The only gaps are the absence of spawn syntax and an explicit error-recovery loop if a cleanup step is blocked.

DimensionReasoningScore

Conciseness

The 13-line body is lean and assumes Claude's competence: an explicit preserve-list ('CLAUDE.local.md', '.claude/settings.local.json', '.claude/worktrees/', ...) and pointed reporting rules with zero padding or explanation of known concepts. Matches the 'every token earns its place' anchor.

5 / 5

Actionability

Gives the verbatim agent task string ('Run the full post-merge cleanup workflow. Preserve all personal and tool-local files...') and concrete preserve/confirm lists, but no syntax for spawning the custom agent and it leans on the agent's own instructions. Mostly executable with minor gaps — anchor 4, not 5.

4 / 5

Workflow Clarity

Five clearly sequenced steps with explicit validation for the destructive operations: 'confirm the merged PR, uncommitted-change handling, branch deletions, force deletions, remote deletions, and origin/master overwrite separately' and 'do not imply the repository is clean unless the final checks prove it'. This avoids the destructive-operation cap of 3, but there is no fix-and-retry error-recovery loop, so anchor 4 rather than 5.

4 / 5

Progressive Disclosure

A simple, single-purpose skill under 50 lines with no bundle files and no external references needed; the numbered list is well organized. Per the simple-skill guideline, well-organized content alone earns the top score.

5 / 5

Total

18

/

20

Passed

Description

87%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 enumerated actions, an explicit third-person 'Use when' trigger clause naming the specific repository and workflow, and minimal overlap risk. The only room for improvement is adding common synonym triggers (e.g., 'delete merged branches', 'sync main').

DimensionReasoningScore

Specificity

The trigger clause enumerates several concrete actions ('clean merged branches, resync master, prune remotes, or prepare the checkout'), matching the 'several specific actions; minor gaps' anchor. Not 3 because coverage exceeds 1-2 actions; not 5 because the headline action ('Clean the... repository') itself remains generic.

4 / 5

Completeness

Explicitly answers both what ('Clean the local hacs_waste_collection_schedule repository after a pull request merges') and when ('Use when a maintainer asks to clean merged branches, resync master, prune remotes, or prepare the checkout for the next ticket') with four concrete trigger phrases, in third person voice. Clearly matches the top anchor.

5 / 5

Trigger Term Quality

Natural maintainer phrases like 'pull request merges', 'resync master', and 'prune remotes' are present and would be said by users needing this skill. Not 5 because common synonyms and variations (e.g., 'delete branches', 'sync main', 'git cleanup') are missing.

4 / 5

Distinctiveness Conflict Risk

It names a specific repository and a narrow post-merge-cleanup niche with distinct triggers, giving it a clear niche with minimal conflict risk against other skills.

5 / 5

Total

18

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
mampfes/hacs_waste_collection_schedule
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.