release

Release for this repo — CalVer tag + narrative prepend.

Quality

67%

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 ./.claude/skills/release/SKILL.md

Quality

Content

81%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.

The body is a highly actionable, well-sequenced release procedure with strong validation and failure handling. Its main weakness is elaborate epistemic prose (theme-axis enumeration, horizon fusion, Markdown parsing rules) that over-explains concepts Claude already knows.

Suggestions

Trim the horizon-fusion and theme-axis meta-discussion to the operational essentials; Claude can infer the epistemic framing.

Remove or shorten the CommonMark setext-H2 explanation and instead show the required blank `>` line pattern by example.

Condense the per-horizon trace and experiential-elicitation prose into a short bullet rule.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands, but the theme-axis/horizon-fusion epistemic prose and the CommonMark setext-H2 explanation cover concepts Claude already knows and could be tightened, matching the mostly-efficient anchor.	3 / 5
Actionability	Copy-paste-ready commands throughout (git tag/push, gh run list polling, gh release edit) plus a complete narrative template fully cover the release workflow's common cases.	5 / 5
Workflow Clarity	Six clearly sequenced phases with explicit validation checkpoints (clean tree, CI success gate, existing-narrative check) and a feedback loop (CI fail -> surface logs, retag with .N), plus a Failure Modes section.	5 / 5
Progressive Disclosure	Well-organized single document with clear sections (Purpose, Preconditions, Flow, Rules, Failure Modes) and no nested references; it exceeds the under-50-line simple-skill exception so it sits at good-structure rather than a perfect 5.	4 / 5
	Total	17 / 20 Passed

Description

53%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.

The description is concise and names concrete actions, but it lacks an explicit trigger clause and natural-term coverage, capping it at the midpoint. It is distinct enough to avoid most conflicts yet still risks overlap with the generic /release skill.

Suggestions

Add a 'Use when...' clause naming natural triggers, e.g. 'Use when cutting a CalVer-tagged release or when the user asks to tag/publish a release for this repo.'

Broaden trigger terms with synonyms users actually say: 'release', 'cut a release', 'tag', 'publish', 'version'.

Optionally list the concrete outcomes (build ZIPs, attach draft notes, prepend narrative) to lift specificity toward 4-5.

Dimension	Reasoning	Score
Specificity	Names the domain ("Release") plus two concrete actions ("CalVer tag" and "narrative prepend"), matching the 1-2 concrete actions anchor; not comprehensive enough for a 4.	3 / 5
Completeness	It gives a clear "what" (CalVer tag + narrative prepend) but has no "Use when..." clause or explicit trigger guidance, which per the rubric caps completeness at 3.	3 / 5
Trigger Term Quality	"Release" and "CalVer tag" are relevant but the description omits common natural variations like "cut a release", "publish", "version", or "tag", placing it at the some-keywords anchor rather than good coverage.	3 / 5
Distinctiveness Conflict Risk	"CalVer tag + narrative prepend" is a fairly specific niche, but it overlaps with the global /release skill the body says it overrides, so minor overlap risk remains rather than minimal.	4 / 5
	Total	13 / 20 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
referenced_paths_exist	Referenced path issues: 3 missing	Warning

	Total	14 / 16 Passed

Repository: jongwony/epistemic-protocols
Path: .claude/skills/release/SKILL.md
Commit: 3ffe94c

Reviewed: 1 day 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.