release

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

Quality

75%

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

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/release/SKILL.md

Quality

Content

81%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 a tightly written, validation-heavy runbook for an immutable release, with executable commands, explicit checkpoints, and clear error-recovery guidance. Its only notable gap is progressive disclosure: all detail is inlined with no companion files for the longer procedural sections.

Suggestions

Extract the two large bash blocks or the companion-repository versioning rules into reference files (e.g. publish-procedure.md) and link them one level deep to improve progressive disclosure.

Define or point to where VERSION, SUMMARY, PREVIOUS_TAG, and RUN_ID are established so the Publish block is fully self-contained.

Consider a short preflight checklist summary at the top so the high-level flow is scannable before the detail.

Dimension	Reasoning	Score
Conciseness	The body is dense and assumes Claude's competence without explaining basics, with every bash block earning its tokens via embedded validation; a few explanatory sentences could be trimmed, so it sits just below 'lean and efficient'.	4 / 5
Actionability	It provides concrete, executable bash commands with exact assertions (test -s, wc -l -eq 7, grep -qF) that are largely copy-paste ready; minor gaps (e.g. VERSION/SUMMARY/PREVIOUS_TAG are referenced without being set inline) keep it below fully executable.	4 / 5
Workflow Clarity	Thirteen numbered steps are sequenced across Preflight/Prepare/Publish/Verify with explicit validation checkpoints and recovery guidance for this destructive, immutable operation ('If release creation fails after tag push, keep the signed tag...'), matching the 'clear sequence with explicit validation and feedback loops' anchor.	5 / 5
Progressive Disclosure	The single file has well-organized section headers and no nested references, but it inlines substantial procedural detail that could live in companion files; structure is good with minor organization gaps, so just below 'clear overview with well-signaled references'.	4 / 5
	Total	17 / 20 Passed

Description

70%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 concrete, specific, and clearly distinguishable, using proper third-person voice and naming six real release actions. Its main weakness is the absence of an explicit 'Use when...' trigger clause, which caps completeness.

Suggestions

Add an explicit trigger clause, e.g. 'Use when preparing or publishing a Fallow release, cutting a version, or publishing to a registry.'

Include common user-facing synonyms beyond 'release'/'publish' (e.g. 'cut a release', 'ship a version') to broaden natural trigger coverage.

Optionally note file extensions or registry names (npm, crates.io, VS Code Marketplace) to improve trigger term specificity.

Dimension	Reasoning	Score
Specificity	The description lists several concrete actions ("version, changelog, generated contracts, companion repositories, registry publication, and post-release verification") with only minor coverage gaps, fitting the 'several specific actions' anchor; not a 5 because coverage is not exhaustive of the full release lifecycle nuances and not a 3 because more than 1-2 actions are named.	4 / 5
Completeness	It clearly states what the skill does but contains no explicit 'Use when...' or equivalent trigger clause for when to invoke it, so per the guideline a missing trigger clause caps completeness at 3.	3 / 5
Trigger Term Quality	It includes natural terms a user would say ("release", "publish", "version", "changelog", "registry") with good coverage, but leans on the project-specific name "Fallow" and omits common synonyms/variations, placing it just below comprehensive.	4 / 5
Distinctiveness Conflict Risk	It carves a clear niche ("Fallow release") with distinct, project-scoped triggers and minimal overlap risk with other skills, matching the 'clear niche with distinct triggers' anchor.	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: .claude/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.