CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

74

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

90%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, highly actionable release-prep workflow with concrete git/gofmt commands and an explicit validation step. The only gaps are an implicit validation feedback loop and the absence of any reference-split structure (which the skill's size does not require).

DimensionReasoningScore

Conciseness

Lean and efficient throughout: every line is actionable instruction with no padding or explanation of concepts Claude already knows (e.g. no 'what a changelog is' filler), and the intro line orients without verbosity.

5 / 5

Actionability

Provides concrete, copy-paste-ready commands at every step — `git tag --list 'v*' --sort=-version:refname`, `git log --oneline <base>..HEAD`, `git shortlog -sne <base>..HEAD`, `gofmt` — plus specific file paths and exact formats; this is an instruction-only skill whose guidance is fully actionable.

5 / 5

Workflow Clarity

A clearly sequenced five-step workflow with an explicit 'Validate' step (gofmt, targeted tests, diff/status review), but the fix-and-retry feedback loop for failed validation is implicit rather than spelled out, leaving it just below the top anchor.

4 / 5

Progressive Disclosure

Well-organized into clear sections (Workflow, Search Hints, Final Response) with a concise overview line and content appropriately self-contained in one file; it stops short of the top anchor only because no one-level-deep reference structure is demonstrated (none is needed, but the 5-anchor emphasizes signaled references).

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, third-person description that clearly states the skill's purpose and gives explicit, varied trigger conditions grounded in concrete artifacts and actions. Only minor synonym coverage is missing in the trigger terms.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — '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 coverage of the release-prep domain.

5 / 5

Completeness

Explicitly answers both 'what' ('Prepare this repository for a release') and 'when' ('Use when asked to do pre-release checks, summarize changes...') with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Good natural-term coverage ('pre-release checks', 'changelog', 'release', 'WHATSNEW.md', 'CONTRIBUTORS.md'), but a few common synonyms users might say (e.g. 'release notes', 'version bump', 'changelog generation') are absent, keeping it just below comprehensive.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (repository-local release-prep documentation passes) with distinct triggers and concrete artifact names, giving minimal overlap risk with unrelated 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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
rusq/slackdump
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.