CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pre-release

Prepare this repository for a release. Use when asked to do pre-release checks, summarize changes since a previous tag, update WHATSNEW.md or changelog entries, update CONTRIBUTORS.md, audit command long help or docs for release-visible features, or verify release documentation consistency.

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

86%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 tight, command-dense workflow document with explicit validation and state-preservation guardrails, appropriate for a self-contained skill with no bundle files. Minor improvements possible: specify the actual test command and add an explicit fix-and-revalidate loop.

Suggestions

In the Validate step, name the concrete test invocation (e.g. `go test ./...` or `go test <touched-package>/...`) instead of the generic 'Run targeted tests for touched Go packages'.

Add an explicit feedback loop after validation: if gofmt or tests fail, fix the issue and re-run before proceeding.

Optionally note in step 1 what to do when no tags exist at all (first release), since the current guidance only covers inferring a previous tag.

DimensionReasoningScore

Conciseness

The ~70-line body is lean and imperative with zero concept padding — every line instructs an action, and concrete git/gofmt commands are given inline without explaining what git or changelogs are. Every token earns its place.

5 / 5

Actionability

Mostly executable guidance: copy-paste-ready commands such as `git tag --list 'v*' --sort=-version:refname`, `git log --oneline <base>..HEAD`, `git shortlog -sne <base>..HEAD`, plus concrete file globs in Search Hints. The gap keeping it below the top anchor is that 'Run targeted tests for touched Go packages' gives no actual command.

4 / 5

Workflow Clarity

A clear 5-step sequence culminating in a dedicated Validate step (gofmt, targeted tests, diff/status review) with an explicit guardrail ('Preserve the user's staged and unstaged state'). It falls short of the top anchor because there is no explicit error-recovery loop for validation failures (fix and re-run).

4 / 5

Progressive Disclosure

No bundle files exist and none are needed: the short body contains only workflow-level guidance that belongs in SKILL.md, organized under clear Workflow / Search Hints / Final Response sections with no inline bloat and no nested references.

5 / 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 with explicit what/when structure and multiple concrete, naturally phrased trigger terms scoped to a distinct niche. Keyword coverage could add a few common synonyms like 'release notes' to be fully comprehensive.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'pre-release checks', 'summarize changes since a previous tag', 'update WHATSNEW.md or changelog entries', 'update CONTRIBUTORS.md', 'audit command long help or docs', 'verify release documentation consistency' — giving comprehensive, not generic, coverage of the skill's capabilities.

5 / 5

Completeness

It clearly answers 'what' ('Prepare this repository for a release') and 'when' with an explicit 'Use when asked to...' clause enumerating six concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Good natural keyword coverage including 'pre-release checks', 'changelog', 'CONTRIBUTORS.md', and 'release documentation'. A few natural terms users might say are missing, such as 'release notes' or 'version bump', so it falls just short of the comprehensive-synonym anchor.

4 / 5

Distinctiveness Conflict Risk

Release prep is a clear niche with distinct triggers (WHATSNEW.md, CONTRIBUTORS.md, command long help auditing); only negligible overlap with generic changelog or commit-message skills.

5 / 5

Total

19

/

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

rusq/slackdump

Path

.agents/skills/pre-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.