CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

77

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

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.

An exemplar guarded-release workflow: concise, fully actionable, and built around explicit approval gates and a feedback loop. No bundle files are present or needed.

DimensionReasoningScore

Conciseness

Seven lean numbered steps with no padding and no explanation of concepts Claude already knows; every line earns its place.

5 / 5

Actionability

Provides concrete, executable guidance including a copy-paste-ready agent prompt ('Proceed with the approved release PR exactly as drafted. Prefix any approved mutating gh command with WCS_GITHUB_APPROVED=1.') and explicit delegation instructions.

5 / 5

Workflow Clarity

Clear sequenced steps with explicit validation checkpoints (user approval in step 4, a change-revise-represent feedback loop in step 5, and an approval gate before any mutation in step 6), so the destructive-operation cap does not apply.

5 / 5

Progressive Disclosure

Under 50 lines, single-purpose, and well-organized as a numbered list with no need for external references; satisfies the simple-skill exception for progressive disclosure.

5 / 5

Total

20

/

20

Passed

Description

92%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, repo-scoped description that clearly conveys both capability and trigger conditions with concrete, natural phrasing. The only minor gap is a few missing synonyms in the trigger-term coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete release-prep actions — 'target version, changelog drafting, a manifest bump, or a release pull request' — giving comprehensive coverage of the release workflow rather than vague language.

5 / 5

Completeness

Explicitly states the 'what' ('Prepare a guarded release of hacs_waste_collection_schedule') and the 'when' ('Use when a maintainer asks for...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural maintainer phrases like 'next release', 'changelog drafting', 'manifest bump', and 'release pull request' are present, but a few common synonyms (e.g. 'release notes', 'version bump', 'tag') are missing.

4 / 5

Distinctiveness Conflict Risk

Scoped to a named repository and a narrow set of release tasks, giving it a clear niche with minimal overlap risk against other skills.

5 / 5

Total

19

/

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.