release

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

Quality

76%

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 ./.agents/skills/release/SKILL.md

Quality

Content

85%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is exceptionally concise and well-sequenced with an explicit completion guard, but the steps are procedural direction rather than executable commands, which limits actionability.

Suggestions

Add concrete, runnable commands or exact CLI invocations for the key steps (e.g., the tag/commit signing and package dry-run commands) so guidance is copy-paste ready rather than descriptive.

Insert per-phase validation checkpoints (e.g., after publication, after registry publication) instead of relying on a single end-of-process guard, to catch failures earlier in the batch/deploy workflow.

Dimension	Reasoning	Score
Conciseness	The body is lean (eight terse numbered steps plus a closing guard clause) with no padding and no explanation of concepts Claude already knows; every token earns its place.	3 / 3
Actionability	Steps name concrete artifacts and targets (e.g., "docs/development/quality-gates.md", "main", companion repos) but provide no executable commands or copy-paste-ready guidance, describing what to do rather than how to do it.	2 / 3
Workflow Clarity	A clearly numbered 1-8 sequence closes with an explicit verification guard ("Do not report a release complete while any required publication or verification workflow is pending"), giving a clear feedback/checkpoint.	3 / 3
Progressive Disclosure	Under 50 lines with no bundle files; references to "docs/development/quality-gates.md" and "task-context-map.md" are one level deep and clearly signaled, appropriate for a well-organized simple skill.	3 / 3
	Total	11 / 12 Passed

Description

67%Weight 40%Scale 1-3

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 and clearly niche-scoped, but lacks an explicit when-to-use trigger clause and relies on project jargon rather than natural user phrasing, capping completeness and trigger-term quality at 2.

Suggestions

Add a "Use when ..." clause stating when to invoke the skill, e.g. "Use when cutting or publishing a Fallow release."

Include natural trigger phrases users would actually say (e.g., "release", "publish", "cut a release", "ship a new version") alongside the project-specific terms.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions ("version, changelog, generated contracts, companion repositories, registry publication, and post-release verification") rather than vague language.	3 / 3
Completeness	Clearly answers what the skill does, but there is no "Use when..." clause or equivalent explicit trigger guidance, so when-to-use is only implied; per guidelines this caps completeness at 2.	2 / 3
Trigger Term Quality	Contains relevant domain keywords ("Fallow release", "registry publication", "changelog") but these are project-specific rather than the natural phrases a user would say (e.g., "cut a release", "publish"), and common variations are missing.	2 / 3
Distinctiveness Conflict Risk	Targets a clear niche ("Fallow release" with version/contracts/registry/companion repos) with distinct triggers unlikely to overlap with unrelated skills.	3 / 3
	Total	10 / 12 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: fallow-rs/fallow
Path: .agents/skills/release/SKILL.md
Commit: 55944e8

Reviewed: 10 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.