CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

release

Release for this repo — CalVer tag + narrative prepend.

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/release/SKILL.md
SKILL.md
Quality
Evals
Security

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.

A strongly engineered operational skill: fully executable commands, explicit sequencing, validation and feedback loops at every phase, and honest failure-mode coverage. The main weaknesses are the verbose epistemic framing around theme axes and horizon fusion, and the absence of any bundle split that would keep SKILL.md lean.

Suggestions

Trim the meta-commentary in Phases 4-5 (trade-off signals, epistemic observations, fusion-accountability rationale) to bare instructions — the CommonMark setext explanation and fusion-trace justification can each be one short sentence.

Move the theme-axis enumeration criteria and the horizon-fusion sub-protocol into a references/ file (e.g. references/narrative.md) and keep only the trigger conditions and a one-line pointer in SKILL.md.

State the tmp-file convention for `--notes-file <tmp-path>` concretely (e.g. how the composed body is written and where) so the final apply step is fully copy-paste ready.

DimensionReasoningScore

Conciseness

The operational core is dense and useful, but Phase 4/5 carry padded meta-discourse — "Trade-off signal: structural strength (faithful to commit shape) vs. interpretive weight (post-hoc grouping)", "a brief epistemic observation", per-horizon trace "fusion accountability" language — plus a CommonMark setext explanation Claude already knows. More than minor trimming is needed, matching 'mostly efficient but includes some unnecessary explanation or could be tightened'.

3 / 5

Actionability

Every phase gives copy-paste-ready commands with exact flags: `git describe --tags --abbrev=0`, `gh run list --workflow=release.yml --limit 1 --json status,conclusion,databaseId`, `gh release view <tag> --json body,url`, `gh release edit <tag> --notes-file <tmp-path>`, plus concrete poll parameters (every 5s, max 12 attempts) and a fill-in narrative template covering the common case.

5 / 5

Workflow Clarity

Six phases are explicitly sequenced (tag decision → push → CI wait → narrative → gate → apply) with validation checkpoints throughout: clean-tree precondition, CI polling with a failure branch and remediation commands, a mandatory user gate with a refine loop, and Rule 6's check-before-overwrite guarding the destructive `gh release edit`. This matches the anchor with explicit validation, error-recovery feedback loops, and a failure-modes checklist.

5 / 5

Progressive Disclosure

No bundle files exist; the skill is a single well-sectioned file (Purpose, Preconditions, Flow phases, Rules, Failure Modes) that reads cleanly top to bottom. However, at ~160 lines the theme-axis enumeration and the horizon-fusion sub-protocol are self-contained detail that could be split into a reference file to slim SKILL.md — 'good structure; minor organization gaps', and the under-50-lines exception for a 5 does not apply.

4 / 5

Total

17

/

20

Passed

Description

50%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 two genuinely concrete actions, but it answers only "what" and leaves "when" entirely unanswered. It also does nothing to distinguish itself from the global /release skill the body says it overrides.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to cut, tag, or publish a release for this repo, or mentions a CalVer tag or release notes."

Broaden natural trigger terms to include user-vocabulary synonyms such as "publish", "cut a release", "version tag", and "release notes" rather than only "release" and jargon like "CalVer".

Disambiguate from the global /release skill in the description itself (e.g. "Project-local release routine that overrides the global /release skill") so the right skill triggers.

DimensionReasoningScore

Specificity

"CalVer tag + narrative prepend" names the release domain and two concrete actions, but coverage is not comprehensive — CI draft coordination, the user gate, and draft/publish handling are all absent. It sits at 'names domain and 1-2 concrete actions' rather than 'lists several specific actions'.

3 / 5

Completeness

The "what" is clear (creates a CalVer tagged release with a narrative prepended to the CI-generated body), but there is no "Use when..." clause or equivalent trigger guidance. Per the judging guideline, a missing trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

"Release" and "tag" are natural terms a user would say, but "CalVer" is jargon and common variations like "publish", "cut a release", "changelog", or "version" are missing. This matches 'some relevant keywords but missing common variations or synonyms'.

3 / 5

Distinctiveness Conflict Risk

"Release for this repo" adds scoping, but the trigger word "release" is generic and the skill body itself acknowledges a global /release skill that this one overrides — a real overlap risk the description does not address. It is 'somewhat specific but could still overlap with similar skills', not 'mostly distinct with minor overlap'.

3 / 5

Total

12

/

20

Passed

Validation

87%

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

CriteriaDescriptionResult

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

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.