CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

release-and-versioning

Maintain VERSION, release notes, release targets, versioned artifacts, GoReleaser packaging, and publication. Use for release-note drafts, release preparation, version checks, and explicitly requested releases; dependency refresh is separate.

Quality

91%

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

SKILL.md
Quality
Evals
Security

Quality

Content

88%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 highly operational skill: exact commands, formats, and a validated release sequence with strong failure-path guidance, and no filler explaining known concepts. The main improvement opportunities are deduplicating the clean-worktree/preflight statements across sections and moving some version-surface detail into a reference file.

DimensionReasoningScore

Conciseness

The body assumes Claude's competence and carries only repository-specific facts (version surfaces, target side effects, script prerequisites), but the clean-worktree requirement and release-git-check behavior each recur in both the target table and the Preparation section, so minor trimming is possible.

4 / 5

Actionability

Commands are copy-paste ready ("make release-git-check", "bash assets/scripts/generate_downloads.sh --check", "git status --short --untracked-files=all", "make dep") with exact formats for the tag ("v<VERSION>"), commit subject ("ops: released v<VERSION>"), and artifact id, plus a table of each target's actual behavior.

5 / 5

Workflow Clarity

The release procedure is a clearly sequenced numbered workflow with explicit preflight validation (steps 1-2), gate execution (step 3), post-publication verification (step 4), and an explicit failure-recovery loop ("If any step fails, inspect the worktree, index, release commit/tag, and remote refs... Do not rerun the entire release"), which satisfies the destructive-operation validation requirement.

5 / 5

Progressive Disclosure

Two real, clearly signaled one-level-deep references (references/ci-and-packaging.md and references/final-qualification.md, both present in the bundle) are well scoped, but the body itself inlines a deep six-bullet version-surface inventory and the reference files link onward to sibling skills' references (../../testing-and-ci/references/...), adding a second hop.

4 / 5

Total

18

/

20

Passed

Description

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

A strong description: concrete capabilities, explicit use-when triggers, third-person voice, and an explicit boundary against the sibling dependency-refresh workflow. The only gap is a few missing natural synonyms (publish, tag, version bump) among trigger terms.

DimensionReasoningScore

Specificity

"Maintain VERSION, release notes, release targets, versioned artifacts, GoReleaser packaging, and publication" lists six concrete, named actions with comprehensive coverage in third-person voice, matching the top anchor rather than the 'minor gaps' level below.

5 / 5

Completeness

It explicitly answers both what ("Maintain VERSION, release notes, release targets, versioned artifacts, GoReleaser packaging, and publication") and when ("Use for release-note drafts, release preparation, version checks, and explicitly requested releases"), with concrete trigger phrases and an added boundary clause.

5 / 5

Trigger Term Quality

"release-note drafts", "release preparation", "version checks", and "explicitly requested releases" are natural user phrases, but common synonyms like "publish", "tag", or "version bump" are missing, so it falls just short of comprehensive.

4 / 5

Distinctiveness Conflict Risk

The description occupies a clear niche (this repository's release/versioning pipeline) and explicitly disambiguates the nearest competing skill ("dependency refresh is separate"), keeping conflict risk minimal.

5 / 5

Total

19

/

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

relative_links

Relative link issues: 2 suspicious

Warning

referenced_paths_exist

Referenced path issues: 5 missing, 5 deeper-than-1-level

Warning

Total

14

/

16

Passed

Repository

greenpau/caddy-security

Path

.codex/skills/release-and-versioning/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.