CtrlK
BlogDocsLog inGet started
Tessl Logo

prepare-release

Prepare a new release by collecting commits, generating bilingual release notes, updating version files, and creating a release branch with PR. Use when asked to prepare/create a release, bump version, or run `/prepare-release`.

72

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

82%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-structured release workflow with concrete commands, an exact output template, and a validation gate before destructive actions. The main gaps are a somewhat lengthy user-focus guidance section and the absence of an explicit error-recovery feedback loop.

Suggestions

Tighten the 'User-Focused Content Only' section: collapse the EXCLUDE/INCLUDE lists and keep one or two ❌/✅ pairs rather than four, since the principle is quickly grasped.

Add an explicit error-recovery loop after Step 5, e.g. 'If the user requests changes, revise the notes and re-present before proceeding to Step 6.'

Consider moving the bilingual release-note format template into a `references/release-note-template.md` file and referencing it one level deep, which would improve progressive_disclosure and reduce SKILL.md length.

DimensionReasoningScore

Conciseness

Mostly lean with concrete commands and an exact output template, but the EXCLUDE/INCLUDE guidance and the ❌/✅ example pairs (lines 101-124) run a bit long even though they are genuinely useful domain guidance rather than padding.

4 / 5

Actionability

Provides copy-paste-ready git commands, exact bilingual release-note format, specific file paths, and a concrete delegation to the gh-create-pr skill with a defined fallback — fully executable with clearly marked placeholders.

5 / 5

Workflow Clarity

A well-sequenced 6-step process with an explicit review/confirm checkpoint (Step 5), a --dry-run escape, and a PR review checklist; it avoids the destructive-operation cap of 3 but lacks a clearly stated 'if review finds issues, fix and re-present' error-recovery loop.

4 / 5

Progressive Disclosure

No bundle files exist and the content is well-organized into labeled sections (Arguments, Workflow, CI Trigger Chain, Constraints) with a clear one-level delegation to the gh-create-pr skill; it is appropriately self-contained, though slightly above the simple-skill threshold so not a maximal 5.

4 / 5

Total

17

/

20

Passed

Description

92%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, third-person description that pairs a concrete action list with an explicit trigger clause and a distinctive slash-command trigger. Only minor room for improvement in adding a few more colloquial trigger synonyms.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'collecting commits, generating bilingual release notes, updating version files, and creating a release branch with PR' — giving comprehensive coverage of the release workflow rather than vague abstraction.

5 / 5

Completeness

Explicitly answers both 'what' (the four release-preparation actions) and 'when' via a concrete 'Use when asked to prepare/create a release, bump version, or run `/prepare-release`' trigger clause.

5 / 5

Trigger Term Quality

Includes natural phrases users say ('prepare/create a release', 'bump version') plus the `/prepare-release` slash command, but a few colloquial synonyms ('cut/ship a release', 'release notes') are absent, keeping it just short of comprehensive.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (Cherry Studio release workflow) with the highly distinct `/prepare-release` trigger and 'bump version' phrasing, minimizing overlap with other skills.

5 / 5

Total

19

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
CherryHQ/cherry-studio
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.