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", "推送".
Overall
score
85%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
90%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 strong skill description with excellent trigger term coverage including multilingual support, and a clear 'Use when' clause. The main weakness is that the capabilities could be more specific about what concrete actions the skill performs (e.g., updating version numbers, creating tags, generating changelog entries) rather than just describing what it auto-detects.
Suggestions
Add specific concrete actions like 'updates version numbers', 'creates git tags', 'generates changelog entries' to improve specificity
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (release workflow) and mentions auto-detection of version files and changelogs, plus lists supported project types. However, it doesn't list specific concrete actions like 'update version numbers', 'generate changelog entries', 'create git tags', etc. | 2 / 3 |
Completeness | Clearly answers both what (universal release workflow, auto-detects version files/changelogs, supports multiple project types) and when (explicit 'Use when user says...' clause with specific trigger phrases). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including 'release', 'new version', 'bump version', 'push', and even Chinese equivalents '发布' and '推送'. These are terms users would naturally say when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused on release/versioning workflows with distinct triggers. The combination of 'release', 'bump version', and specific project type support makes it unlikely to conflict with other skills like general git or deployment skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted, highly actionable release workflow skill with excellent workflow clarity and concrete executable guidance. The main weaknesses are verbosity (particularly in repeated multi-language examples and translation tables) and the monolithic structure that could benefit from splitting reference material into separate files. The skill excels at providing clear decision logic and validation checkpoints.
Suggestions
Move the section title translation table and language detection rules to a separate REFERENCE.md file, keeping only a brief summary in the main skill
Consolidate the three multi-language changelog examples into one example with a note that the same pattern applies to all languages
Consider extracting the .releaserc.yml configuration documentation to a separate CONFIG.md file
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some redundant information like the full section title translation table and extensive examples that could be condensed. The multi-language changelog examples repeat similar patterns three times when one with a note would suffice. | 2 / 3 |
Actionability | Provides fully executable bash commands, specific git operations, clear file paths, and concrete examples throughout. The workflow includes copy-paste ready commands like `git tag --sort=-v:refname | head -1` and specific JSONPath/TOML paths for version files. | 3 / 3 |
Workflow Clarity | Excellent 9-step workflow with clear sequencing, explicit validation through dry-run mode, user confirmation checkpoint before release commit, and clear decision trees for version bump logic. Includes feedback loops for breaking change detection and README update verification. | 3 / 3 |
Progressive Disclosure | Content is well-structured with clear sections and tables, but the entire skill is monolithic at ~350 lines. The configuration section, language detection rules, and section title translations could be split into separate reference files to improve scannability. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
88%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 14 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
Total | 14 / 16 Passed | |
- 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.