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", "推送".
77
72%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./.claude/skills/release-skills/SKILL.mdQuality
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 term coverage (including multilingual terms) and a clear 'Use when' clause. Its main weakness is that the 'what' portion could be more specific about the concrete actions performed during the release workflow — it says it auto-detects version files but doesn't specify what it does with them (e.g., bumps versions, creates tags, publishes packages).
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 that 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 description carves out a clear niche around release/versioning workflows with specific trigger terms. The inclusion of 'push' could potentially overlap with git-related skills, but the overall context of release workflow and version bumping makes it quite distinct. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
55%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill has excellent actionability and workflow clarity with concrete commands, clear step sequencing, and proper validation checkpoints. However, it is severely over-engineered for a single SKILL.md file — the extensive translation tables, triple-language changelog examples, full configuration file examples, and detailed dry-run output make it extremely verbose. Much of this content should be split into reference files, and concepts Claude already knows (conventional commits, semver, basic git) should be trimmed significantly.
Suggestions
Extract the translation tables, hook contract details, and configuration examples into separate reference files (e.g., TRANSLATIONS.md, HOOKS.md, CONFIG.md) and link to them from the main skill.
Remove explanations of concepts Claude already knows: conventional commit types, semver bump rules, git tag/push commands. Replace with brief references or just the project-specific conventions.
Consolidate the three-language changelog examples into a single example with a note that the same pattern applies to all detected languages, rather than showing full English/Chinese/Japanese versions.
Trim the dry-run output example significantly — a 2-3 line summary of what dry-run does is sufficient rather than a 30-line mock output.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~350+ lines. It includes extensive translation tables, multiple detailed examples in three languages, lengthy configuration file examples, and dry-run output examples that could be significantly condensed. Much of this (conventional commit types, semver rules, git commands) is knowledge Claude already has. | 1 / 3 |
Actionability | The skill provides fully executable git commands, specific file paths, concrete examples of commit messages, changelog formats, and clear command-line flags. Every step includes copy-paste ready commands and specific tool invocations like `gh pr view`. | 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 preview, breaking change detection with warnings, and a clear feedback loop in the hook contract. The workflow handles error cases and includes a confirmation gate before destructive operations. | 3 / 3 |
Progressive Disclosure | Everything is crammed into a single monolithic file with no references to external files. The translation tables, configuration examples, hook contract details, and multi-language changelog examples could easily be split into separate reference files. The content is a wall of text that would benefit greatly from splitting into overview + detailed references. | 1 / 3 |
Total | 8 / 12 Passed |
Validation
90%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 (502 lines); consider splitting into references/ and linking | Warning |
Total | 10 / 11 Passed | |
- Repository
- JimLiu/baoyu-skills
- Commit
8be98c5
- Reviewed
Table of Contents
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.