release

Determine the next version, update the marketing site, and run the full release pipeline.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/release/SKILL.md

Quality

Content

92%Weight 40%Scale 1-3

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

The body is a tightly written, highly actionable release runbook with explicit validation checkpoints and concrete commands throughout. Its only weakness is the absence of progressive disclosure — all detail lives inline in one file rather than being split across references.

Dimension	Reasoning	Score
Conciseness	The body is lean and procedural — exact commands and HTML/commit snippets with no concept explanations Claude already knows — so every token earns its place per the lean-and-efficient anchor.	3 / 3
Actionability	Provides fully executable, copy-paste-ready commands (git tag/log, notarytool, ./scripts/release.sh, exact HTML replacement and commit message), matching the fully-executable anchor rather than pseudocode.	3 / 3
Workflow Clarity	Steps are explicitly sequenced with validation checkpoints — clean-tree/branch/env checks, mandatory version confirmation, and a no-auto-retry stop-and-report policy for the destructive release operation — matching the clear-sequence-with-explicit-validation anchor.	3 / 3
Progressive Disclosure	Well-organized into headed sections but it is a single ~110-line file with all detail inline and no content offloaded to references; exceeding the simple-skill threshold means organization alone does not reach 3, fitting the some-structure-but-inline-content anchor.	2 / 3
	Total	11 / 12 Passed

Description

60%Weight 40%Scale 1-3

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 names concrete actions clearly but omits any explicit "Use when..." trigger guidance, capping completeness at 2 and limiting trigger-term coverage. It is specific yet lacks the natural-language cues users would actually say to invoke this skill.

Suggestions

Add an explicit trigger clause, e.g. "Use when cutting a new release of Chops, bumping the version, or shipping a new build."

Include natural variations users would say ("ship a release", "publish a new version", "cut a release") alongside "release pipeline".

Tie the description to the Chops-specific context (macOS app, notarized build) to sharpen distinctiveness from generic release skills.

Dimension	Reasoning	Score
Specificity	Lists three distinct concrete actions — "Determine the next version", "update the marketing site", "run the full release pipeline" — matching the multiple-specific-actions anchor rather than the score-2 domain-plus-some-actions level.	3 / 3
Completeness	Clearly answers "what" (three actions) but provides no "Use when..." or equivalent explicit trigger guidance, so per the judging guidelines completeness is capped at 2 (what present, when missing/implied).	2 / 3
Trigger Term Quality	Relevant terms ("next version", "marketing site", "release pipeline") are present but common natural variations a user would say ("cut a release", "ship", "publish", "bump version") are missing, fitting the some-keywords-but-missing-variations anchor.	2 / 3
Distinctiveness Conflict Risk	The release niche with a marketing-site update is fairly specific, but without distinct explicit triggers the wording could overlap with other release/publish skills, matching the somewhat-specific-but-could-overlap anchor.	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: Shpigford/chops
Path: .claude/skills/release/SKILL.md
Commit: 1a1ff0d

Reviewed: 12 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.