create-release

Create releases with proper versioning, release notes, and Git tags

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/create-release/SKILL.md

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 skill body is highly actionable and clearly sequenced with strong validation for an irreversible release operation. Its main weakness is conciseness and progressive disclosure: redundant Safety/Guardrails/Contract sections and a large monolithic file that could be split into references.

Suggestions

De-duplicate the Safety, Guardrails, and Execution Contract sections, which restate the same pre-release checks as the numbered Steps.

Move the large release-notes and release.json templates into a references/ file and link to them from the steps to improve progressive disclosure.

Trim or consolidate the Output Format example, which largely restates data already in the Artifacts Generated section.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes competence (executable bash/JSON with no padding about what git or releases are), but Safety/Guardrails sections and the Execution Contract vs. numbered Steps repeat the same points, so it is 'mostly efficient but could be tightened' rather than fully lean.	2 / 3
Actionability	It provides fully executable commands (uv run pytest, pre-commit run, git tag -a, gh release create) that are copy-paste ready and specific, matching the score-3 anchor rather than the pseudocode/incomplete score-2 anchor.	3 / 3
Workflow Clarity	A clear 9-step sequence includes explicit validation checkpoints (tests pass, no uncommitted changes, on main branch), a confirmation prompt before tagging, and post-action verification (git ls-remote, gh release view) with error-exit feedback loops for an irreversible operation.	3 / 3
Progressive Disclosure	The ~330-line file is well-sectioned but monolithic: large templates (release notes, JSON record) are inline and no references/scripts/assets bundle exists, so content that could be split is inline and navigation is single-file — matching 'some structure but content that should be separate is inline'.	2 / 3
	Total	10 / 12 Passed

Description

60%

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 specific about concrete actions but lacks an explicit use-when trigger and broad trigger-term coverage, leaving completeness and trigger quality as its weak spots. It is reasonably distinct but could be more sharply differentiated.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when cutting a new Bindu release, bumping versions, or generating release notes and Git tags.'

Broaden natural trigger terms to include variations users say (e.g. 'publish a release', 'changelog', 'version bump').

Add project context (e.g. 'Bindu/CalVer releases') to reduce overlap with generic release or git skills.

Dimension	Reasoning	Score
Specificity	The phrase 'Create releases with proper versioning, release notes, and Git tags' lists multiple specific concrete actions (versioning, release notes, Git tags), matching the score-3 anchor rather than the score-2 'some actions' anchor.	3 / 3
Completeness	It clearly states what the skill does but provides no 'Use when...' or equivalent trigger clause for when to use it, so per the guideline a missing trigger clause caps completeness at 2.	2 / 3
Trigger Term Quality	Natural terms like 'releases', 'release notes', and 'Git tags' are present, but common variations users would say ('publish', 'changelog', 'version bump', 'cut a release') are missing, so it lands at 'some relevant keywords but missing common variations' rather than full coverage.	2 / 3
Distinctiveness Conflict Risk	Release/versioning/tagging is a recognizable niche, but the description could still overlap with general git or CI/release-adjacent skills, placing it at 'somewhat specific but could still overlap'.	2 / 3
	Total	9 / 12 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: GetBindu/Bindu
Path: .agents/skills/create-release/SKILL.md
Commit: 7b1ff75

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.