release

Prepare and publish a Fallow release with version, changelog, generated contracts, companion repositories, registry publication, and post-release verification.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

96%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 release runbook: executable, tightly sequenced, and rich in validation gates and error-recovery guidance, with only minor room to split detailed sub-procedures into bundled reference files.

Dimension	Reasoning	Score
Conciseness	Lean, dense runbook that assumes Claude's competence — every line is actionable project-specific procedure with no padding explaining generic release concepts.	5 / 5
Actionability	Provides fully executable, copy-paste-ready bash blocks (gh API checks, workflow dispatch, tag creation, artifact verification) covering the concrete release cases.	5 / 5
Workflow Clarity	Clearly sequenced Preflight/Prepare/Publish/Verify phases with explicit validation checkpoints, feedback loops ('If the workflow fails, repair and rerun it without burning a tag'), and an immutability-aware close-out checklist.	5 / 5
Progressive Disclosure	Well-organized into clearly signaled phases with one-level-deep references to repo docs; no bundle files exist, and the single-file runbook is appropriately sectioned, though some sub-procedures could conceivably live in separate references.	4 / 5
	Total	19 / 20 Passed

Description

67%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 specific, action-oriented, and well-scoped to a distinct niche, but lacks an explicit 'when to use' trigger clause and natural-language synonyms, which cap completeness and trigger-term quality.

Suggestions

Add an explicit 'Use when...' clause stating when Claude should invoke this skill (e.g., 'Use when cutting or publishing a Fallow release').

Include natural user phrasings and synonyms such as 'cut a release', 'ship a release', or 'bump the version' to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'version, changelog, generated contracts, companion repositories, registry publication, and post-release verification' — giving comprehensive coverage of the release process.	5 / 5
Completeness	The 'what' is clear and concrete, but there is no 'Use when...' clause or equivalent explicit trigger guidance, which per the guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	Contains relevant keywords ('release', 'publish', 'version', 'changelog', 'registry') but leans technical and omits common natural synonyms a user might say; no file extensions or phrasing variants.	3 / 5
Distinctiveness Conflict Risk	Scoped to a 'Fallow release' — a clear niche with distinct triggers and minimal risk of firing for unrelated skills.	5 / 5
	Total	16 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	15 / 16 Passed

Repository: fallow-rs/fallow
Path: .agents/skills/release/SKILL.md
Commit: 7e1e075

Reviewed: 3 days 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.