release-bump-changelog

Use this skill when preparing a release bump or updating release notes. It writes a launch-style release story from the actual change set, then runs `cargo bump` so the generated GitHub notes and the marketing copy land together in `CHANGELOG.md`.

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

78%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 well-structured, actionable release workflow with concrete commands and an explicit verification step. Its main gap is the absence of an explicit failure-recovery loop in the verification step for a destructive operation.

Suggestions

Add an explicit 'if verification fails, fix the missing files/tag and re-run the bump' feedback loop to satisfy the destructive-operation validation requirement.

Show the exact command for writing the marketing file (e.g., a heredoc into $marketing_file) so the draft step is fully copy-paste-ready.

Trim editorial lines like the v0.2.0 style reference and the standalone-sync-script note to tighten conciseness.

Dimension	Reasoning	Score
Conciseness	The body is lean with no padding over concepts Claude already knows and tight imperative sections, but a few lines ('Target style: similar to the v0.2.0 narrative', 'Do not use a standalone changelog sync script') are slightly editorial and could be trimmed, fitting anchor 4 rather than the pristine 5.	4 / 5
Actionability	Provides copy-paste-ready commands (cargo bump with explicit level forms, SPACEBOT_RELEASE_MARKETING_COPY_FILE env var, mktemp, gh auth status, git show/tag verification), but only narrates 'write markdown content to $marketing_file' without an explicit write command, a minor gap keeping it at anchor 4 rather than 5.	4 / 5
Workflow Clarity	A clear four-step sequence with an explicit verify step and checklist (Cargo.toml/Cargo.lock/CHANGELOG.md plus tag confirmation) for a destructive release operation, but it lacks an explicit validate->fix->retry recovery loop when verification fails, so it fits anchor 4 rather than the 5 with feedback loops.	4 / 5
Progressive Disclosure	No bundle files exist and the ~52-line single-file body is cleanly organized into well-labeled sections (Goal, Workflow, Requirements, Release Story Format, Notes) with no nested references, meeting the simple-skill exception for a 5 on well-organized structure with no external references needed.	5 / 5
	Total	17 / 20 Passed

Description

83%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 clearly states what the skill does and when to use it, with concrete actions and natural triggers tied to a specific cargo-based release workflow. Minor improvements would come from adding common synonyms and slightly sharper capability wording.

Suggestions

Add common trigger synonyms such as 'version bump', 'changelog', or 'tagging a release' so users who phrase the need differently still match.

Make the 'marketing copy' capability slightly more concrete (e.g., 'drafts a launch-style release narrative') to push specificity toward comprehensive coverage.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('writes a launch-style release story from the actual change set', 'runs cargo bump', notes and marketing copy 'land together in CHANGELOG.md'), but 'marketing copy' is slightly generic with minor coverage gaps, fitting anchor 4 rather than the comprehensive 5.	4 / 5
Completeness	Explicitly answers 'when' ('Use this skill when preparing a release bump or updating release notes') and 'what' (writes a release story, runs cargo bump, lands generated GitHub notes and marketing copy in CHANGELOG.md) with concrete trigger phrases, matching anchor 5; not 4 because both halves are explicit and concrete.	5 / 5
Trigger Term Quality	Natural triggers 'release bump' and 'updating release notes' are phrases a user would say, but common synonyms like 'version bump', 'changelog', or 'tagging a release' are missing, matching anchor 4 (good coverage, a few natural terms missing) rather than the comprehensive 5.	4 / 5
Distinctiveness Conflict Risk	The cargo-release-with-marketing-copy niche is mostly distinct with minimal conflict risk, though 'release notes' could loosely overlap with generic changelog skills, fitting anchor 4 rather than the fully-distinct 5.	4 / 5
	Total	17 / 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: spacedriveapp/spacebot
Path: .agents/skills/release-bump-changelog/SKILL.md
Commit: ab2c160

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