release-skills

Universal release workflow. Auto-detects version files and changelogs. Supports Node.js, Python, Rust, Claude Plugin, GitHub Releases, annotated tags, historical release backfill, and generic projects. Use when user says "release", "发布", "new version", "bump version", "push", "推送", "release notes", "GitHub Release", or "回填 Release".

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

71%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.

A highly actionable, well-sequenced release workflow with executable commands and a confirmation gate before destructive operations. Its main weaknesses are verbosity from repeated full multi-language examples and a monolithic structure with no progressive disclosure for the large reference material.

Suggestions

Move the 7-language section-title translation table and the full .releaserc.yml schema into a references/ file (e.g. references/translations.md and references/config.md) and link to them from SKILL.md to apply progressive disclosure.

De-duplicate the multi-language changelog examples: show one full example in Step 4 and reference it from the Dry-Run Mode section instead of re-rendering the en/zh previews verbatim.

Add a post-release verification step (e.g. confirm `gh release view v{VERSION}` succeeds and `git push` completed) with a short error-recovery note to raise workflow clarity.

Dimension	Reasoning	Score
Conciseness	Mostly actionable and free of generic-knowledge padding, but noticeably redundant: full tri-language changelog examples (en/zh/ja) are written out in Step 4 and then largely re-rendered in the Dry-Run Mode section, and the large section-title translation table could be tightened.	3 / 5
Actionability	Provides copy-paste-ready, executable commands throughout (git tag/log, gh release create/edit with --notes-file --verify-tag, git commit formats, .releaserc.yml schema) with concrete examples covering the common release cases.	5 / 5
Workflow Clarity	A clear 10-step sequence with an explicit user-confirmation checkpoint (Step 8) before destructive tag/push/release operations, plus dry-run preview and breaking-change warnings; falls short of 5 only because there are no explicit post-operation verification or error-recovery feedback loops.	4 / 5
Progressive Disclosure	The file is well-organized with clear section headers, but it is a ~570-line monolith with no bundle/reference files and large inline reference blocks (7-language translation table, full config schema, multi-language examples) that would be better split into separate referenced files.	3 / 5
	Total	15 / 20 Passed

Description

96%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, well-structured description that clearly states both capabilities and explicit trigger phrases including multilingual variants. The only weak point is the somewhat generic 'push' trigger, which introduces minor overlap risk with general git-push workflows.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities — 'Auto-detects version files and changelogs', 'GitHub Releases', 'annotated tags', 'historical release backfill' — alongside the supported ecosystems, giving comprehensive coverage of what the skill does.	5 / 5
Completeness	Explicitly answers both what ('Universal release workflow. Auto-detects version files and changelogs. Supports...') and when ('Use when user says...') with concrete trigger phrases, matching the anchor 5 example closely.	5 / 5
Trigger Term Quality	The 'Use when user says...' clause enumerates natural phrases users actually say ('release', 'new version', 'bump version', 'push', 'release notes', 'GitHub Release') plus multilingual synonyms ('发布', '推送', '回填 Release'), giving comprehensive coverage.	5 / 5
Distinctiveness Conflict Risk	The release niche is clear with distinct triggers, but listing the bare trigger 'push' / '推送' creates minor overlap risk with generic git-push skills, so it sits just below the minimal-conflict anchor 5.	4 / 5
	Total	19 / 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
skill_md_line_count	SKILL.md is long (579 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

Repository: JimLiu/baoyu-skills
Path: .claude/skills/release-skills/SKILL.md
Commit: 1567581

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