release-skills

Universal release workflow. Auto-detects version files and changelogs. Supports Node.js, Python, Rust, Claude Plugin, and generic projects. Use when user says "release", "发布", "new version", "bump version", "push", "推送".

Quality

76%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./.claude/skills/release-skills/SKILL.md

Quality

Discovery

89%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a solid skill description with excellent trigger terms (including multilingual support) and a clear 'Use when' clause. Its main weakness is that the 'what' portion is somewhat vague — it says it's a 'universal release workflow' that 'auto-detects version files and changelogs' but doesn't specify the concrete actions performed (e.g., bumping versions, creating tags, publishing). Despite this, it would perform well in skill selection scenarios.

Suggestions

Add specific concrete actions the skill performs, e.g., 'Bumps version numbers, updates changelogs, creates git tags, and publishes packages' to improve specificity.

Dimension	Reasoning	Score
Specificity	Names the domain (release workflow) and mentions auto-detecting version files and changelogs, plus lists supported project types. However, it doesn't list multiple concrete actions beyond 'auto-detects version files and changelogs' — it doesn't specify what it actually does (e.g., bump version numbers, generate changelog entries, create git tags, publish packages).	2 / 3
Completeness	Clearly answers both 'what' (universal release workflow, auto-detects version files and changelogs, supports multiple project types) and 'when' (explicit 'Use when user says...' clause with specific trigger phrases). The 'Use when' clause is explicit and well-defined.	3 / 3
Trigger Term Quality	Includes strong natural trigger terms: 'release', 'new version', 'bump version', 'push', and even Chinese equivalents '发布' and '推送'. Also mentions specific ecosystems (Node.js, Python, Rust) which users might reference. Good coverage of terms users would naturally say.	3 / 3
Distinctiveness Conflict Risk	The combination of 'release workflow', specific language ecosystem support, and distinct trigger terms like 'release', 'bump version', and '发布' creates a clear niche. The term 'push' could potentially overlap with git-related skills, but the overall context makes it distinguishable.	3 / 3
	Total	11 / 12 Passed

Implementation

62%

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

The skill provides an extremely thorough and actionable release workflow with clear step sequencing and good validation checkpoints. However, it is significantly over-verbose — the multi-language translation tables, triple-language changelog examples, full configuration file examples, and detailed dry-run output could be moved to reference files or significantly condensed. The content explains many concepts Claude already knows (conventional commits, semver, basic git operations) rather than focusing only on the project-specific workflow logic.

Suggestions

Move the section title translation table, full .releaserc.yml example, and multi-language changelog examples into a separate REFERENCE.md file, keeping only the English example inline.

Remove explanations of concepts Claude already knows: conventional commit types table, semver bump rules, and basic git commands — instead just reference them briefly (e.g., 'Use conventional commit categorization').

Consolidate the dry-run output example to be much shorter — a 3-line summary rather than a full 30-line output block, since the format is already clear from the workflow steps.

Consider removing the 'Common README Updates Needed' table and language detection rules table, replacing them with a single sentence each since Claude can infer these patterns.

Dimension	Reasoning	Score
Conciseness	The skill is extremely verbose at ~400+ lines. It includes extensive translation tables, multiple lengthy examples in three languages, detailed configuration file examples, and dry-run output examples that significantly bloat the content. Much of this (conventional commit types, semver rules, git commands) is knowledge Claude already has.	1 / 3
Actionability	The skill provides fully executable bash commands, specific git operations, concrete examples of commit messages, changelog formats, and version file paths. Every step includes copy-paste ready commands and clear expected outputs.	3 / 3
Workflow Clarity	The 9-step workflow is clearly sequenced with explicit validation checkpoints: user confirmation before release commit (Step 8), dry-run mode for previewing, breaking change detection with warnings, and a clear feedback loop for README updates. The workflow handles destructive operations (git push) with explicit user confirmation.	3 / 3
Progressive Disclosure	The content is largely monolithic — all details are inline in a single file including full translation tables, multi-language changelog examples in three languages, complete .releaserc.yml configuration, and dry-run output. The translation tables, configuration reference, and detailed examples could be split into separate reference files to keep the main skill lean.	2 / 3
	Total	9 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (512 lines); consider splitting into references/ and linking	Warning

	Total	10 / 11 Passed

Repository: jimliu/baoyu-skills
Commit: 505a7e1

Reviewed: about 22 hours 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.