release

Prepare a guarded release of hacs_waste_collection_schedule. Use when a maintainer asks for the next release, a target version, changelog drafting, a manifest bump, or a release pull request.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

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

An exemplary instruction-only skill body: terse, correctly sequenced, and safety-gated around an explicit approval checkpoint with a built-in revision loop. The only minor gap is that a few downstream specifics (tag/release commands, version validation) are alluded to but not stated.

Dimension	Reasoning	Score
Conciseness	The body is a lean 7-step list with zero padding and no explanation of concepts Claude already knows; every step adds operational information. This matches the anchor "Lean and efficient; assumes Claude's competence; every token earns its place".	5 / 5
Actionability	Guidance is mostly executable: the exact approval message to send ("Proceed with the approved release PR exactly as drafted. Prefix any approved mutating gh command with WCS_GITHUB_APPROVED=1.") is copy-paste ready. It falls short of 5 because the post-merge tag/release commands and the version-validation method are referenced but never specified.	4 / 5
Workflow Clarity	The sequence is explicit with strong validation checkpoints for a risky operation: mutations are prohibited during drafting (step 3), drafts must be presented verbatim with explicit user approval (step 4), a revision feedback loop exists (step 5), and execution is gated on approval (step 6). This matches the top anchor with feedback loops and gating for a release workflow.	5 / 5
Progressive Disclosure	The skill is under 50 lines, single-purpose, has no bundle files, and needs no external references; the numbered-list structure is well-organized. Per the rubric's simple-skill guideline, this earns the top score with just well-organized sections.	5 / 5
	Total	19 / 20 Passed

Description

73%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 with an explicit, well-phrased trigger clause and excellent distinctiveness from a named repository. Its main weakness is that the capability statement ("Prepare a guarded release") stays high-level while the concrete artifacts it produces are only implicit in the when-clause.

Suggestions

Promote the concrete deliverables into the capability statement, e.g. "Draft the changelog section, bump the manifest version, and open a release pull request for hacs_waste_collection_schedule".

Add common synonyms to the trigger clause such as "version bump", "cut a release", or "tag a release" to broaden natural keyword coverage.

Dimension	Reasoning	Score
Specificity	The description names a concrete domain ("hacs_waste_collection_schedule") and one action ("Prepare a guarded release"), which matches the anchor for 1-2 concrete actions without comprehensive coverage. It is above score 2 because the domain is specific rather than generic, but below score 4 because the actual deliverables (changelog, manifest bump, release PR) appear only in the when-clause rather than as stated capabilities.	3 / 5
Completeness	Both what ("Prepare a guarded release of hacs_waste_collection_schedule") and when (an explicit "Use when a maintainer asks for..." clause with concrete triggers) are present. It does not reach 5 because the what is high-level — "guarded release" is not decomposed into the concrete actions performed.	4 / 5
Trigger Term Quality	Phrases like "next release", "a target version", "changelog drafting", "a manifest bump", or "a release pull request" are natural terms a maintainer would say. It falls short of score 5 because common synonyms such as "version bump", "cut a release", "publish", or "tag a release" are missing.	4 / 5
Distinctiveness Conflict Risk	The description is pinned to a single named repository and maintainer-specific triggers ("a maintainer asks for the next release..."), giving it a clear niche with minimal conflict risk against other skills.	5 / 5
	Total	16 / 20 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: mampfes/hacs_waste_collection_schedule
Path: .agents/skills/release/SKILL.md
Commit: b081073

Reviewed: 5 hours ago

Table of Contents

Discovery Implementation Validation

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.