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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

77%

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

The body is highly actionable with a clear, well-validated multi-step release workflow, but it is a monolithic single file that could benefit from splitting reference material out and trimming content Claude already knows.

Suggestions

Move the section-title translation table, the project hook contract, and the .releaserc.yml reference into separate reference files (e.g. references/TRANSLATIONS.md, references/HOOKS.md) and link to them one level deep from SKILL.md to improve progressive disclosure.

Remove the conventional-commit type definition table ('feat = New features', 'fix = Bug fixes', etc.) — Claude already knows these — and keep only the project-specific section-mapping behavior.

Delete the trailing 'When to Use' section since its trigger phrases duplicate the frontmatter description, which already specifies when to invoke the skill.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with actionable tables and commands, but ~570 lines include concepts Claude already knows (the conventional-commit type table 'feat = New features, fix = Bug fixes...') and a 'When to Use' section that duplicates the frontmatter triggers. Not a 3 because some padding could be trimmed; not a 1 because the bulk is concrete guidance rather than explanatory prose.	2 / 3
Actionability	Provides copy-paste executable commands ('git tag -a v{VERSION} -F <release-notes-file>', 'gh release create ... --verify-tag'), a version-path-by-file-type table, and concrete multi-language changelog examples. Not a 2 because the guidance is complete and executable rather than pseudocode.	3 / 3
Workflow Clarity	Clear 10-step sequence with explicit validation checkpoints: user confirmation in Step 8, dry-run preview, and explicit confirmation before rewriting published lightweight tags in backfill. Not a 2 because feedback loops and checkpoints are explicit for the destructive/batch operations (tag rewriting, releases).	3 / 3
Progressive Disclosure	No bundle files exist; the entire ~570-line spec is a single monolithic SKILL.md with section-translation, hook-contract, and config-reference content that could live in separate reference files. Not a 3 because content that should be split is inline with no one-level-deep references; not a 1 because sections are well-organized rather than an undifferentiated wall of text with nested references.	2 / 3
	Total	10 / 12 Passed

Description

100%

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 third-person, concise, and clearly states both capabilities and explicit bilingual trigger phrases. It distinguishes the skill well and answers what and when without padding.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities — 'Auto-detects version files and changelogs', 'Supports Node.js, Python, Rust, Claude Plugin, GitHub Releases, annotated tags, historical release backfill, and generic projects' — matching the anchor for listing several specific actions.	3 / 3
Completeness	Explicitly answers both what ('Universal release workflow...') and when ('Use when user says...'), with an explicit 'Use when' trigger clause, satisfying the top anchor. Not a 2 because the when is explicit rather than implied.	3 / 3
Trigger Term Quality	Broad natural trigger coverage in two languages — 'release', '发布', 'new version', 'bump version', 'push', '推送', 'release notes', 'GitHub Release', '回填 Release' — terms users would actually say. Not a 2 because common variations are well represented rather than partially covered.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear niche (version releasing) with distinct, release-specific triggers unlikely to fire for unrelated skills. Not a 2 because the triggers are specific to release activity rather than overlapping with general skills.	3 / 3
	Total	12 / 12 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
Commit: c9a50cc

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.