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.

76

Quality

93%

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

100%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 an exemplary lean, single-purpose instruction skill: concrete, executable, and tightly sequenced with explicit validation checkpoints for destructive operations. It assumes Claude's competence and avoids unnecessary explanation.

DimensionReasoningScore

Conciseness

The body is lean: five numbered steps, no padding, and no explanation of concepts Claude already knows. Every token earns its place.

5 / 5

Actionability

Provides concrete, executable guidance — an exact agent-spawn task string, an explicit list of files to preserve, and a specific list of destructive actions to confirm — copy-paste ready.

5 / 5

Workflow Clarity

A clear five-step sequence with explicit validation: step 4 requires separate confirmation of the merged PR, branch deletions, force deletions, remote deletions, and origin/master overwrite, and step 5 demands final-state proof before declaring the repository clean.

5 / 5

Progressive Disclosure

A simple single-purpose skill under 50 lines with no external references needed; the five-step structure is well-organized and self-contained, fitting the simple-skill exception.

5 / 5

Total

20

/

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.

The description is precise, action-oriented, and explicitly states both capability and trigger conditions in third person. It clearly names the target repository and several concrete maintainer scenarios, with minimal overlap risk.

DimensionReasoningScore

Specificity

Names the concrete domain (post-merge cleanup of the hacs_waste_collection_schedule repository) and several specific actions ('clean merged branches, resync master, prune remotes, or prepare the checkout'), with only minor gaps in coverage.

4 / 5

Completeness

Explicitly answers both 'what' (clean the 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').

5 / 5

Trigger Term Quality

Includes natural maintainer phrases like 'clean merged branches', 'resync master', 'prune remotes', and 'prepare the checkout for the next ticket' that a user would plausibly say, though a few common synonyms are absent.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (post-merge repo cleanup for a specific repository) with distinct triggers, making it unlikely to fire for unrelated 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.