CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

release

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

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

High

Do not use without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

96%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 content is a tightly written, fully executable release workflow with strong validation checkpoints and clear sequencing. Progressive disclosure is solid for a self-contained single-file skill, though it has no external reference structure to evaluate.

DimensionReasoningScore

Conciseness

The body is lean and efficient with inline executable commands and no padding or explanation of concepts Claude already knows; every section earns its tokens.

5 / 5

Actionability

Guidance is fully executable and copy-paste ready: exact bash/git/notarytool commands, a specific file path with an exact HTML replacement, and complete AskUserQuestion option payloads.

5 / 5

Workflow Clarity

A clear numbered sequence with explicit validation checkpoints (prerequisite checks, version-confirm gate, changelog-confirm gate) and an explicit fail-and-stop-no-retry feedback loop for a destructive/batch operation.

5 / 5

Progressive Disclosure

The skill is a single well-organized SKILL.md with clear section headers and no nested documentation references; no bundle files exist to navigate, so it is well-structured but does not demonstrate one-level-deep reference signaling.

4 / 5

Total

19

/

20

Passed

Description

58%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 specific and action-oriented, naming three concrete release tasks, but it lacks an explicit "Use when..." trigger clause, which caps completeness. Trigger term coverage is adequate but misses common natural phrasings users would actually say.

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 synonyms users would say such as "ship a release", "new version", or "cut a release" alongside "release pipeline".

Consider naming the target product (Chops) in the description to further reduce overlap with generic release/deploy skills.

DimensionReasoningScore

Specificity

Names three concrete actions ("Determine the next version", "update the marketing site", "run the full release pipeline"); "full release pipeline" is slightly abstract, keeping it just below comprehensive coverage at 5.

4 / 5

Completeness

It clearly states what the skill does but provides no "Use when..." trigger guidance; per the rubric a missing explicit trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

Relevant keywords (release, version, marketing site, pipeline) are present but common natural variations like "cut a release", "ship", or "new version" are missing, matching the anchor for some relevant keywords with gaps.

3 / 5

Distinctiveness Conflict Risk

The release/versioning niche is mostly distinct with clear triggers, with only minor overlap risk against generic deploy/ship skills.

4 / 5

Total

14

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

Shpigford/chops

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.