Name: tessl/release-check
Rating: 68.8 (1 reviews)
Author: tessl

tessl/release-check

Walk a release readiness checklist — migrations, feature flags, changelog, docs — and report what is missing before the release window.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

78%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 well-structured, actionable instruction-only skill with a clear workflow and per-item verification; absence of code is appropriate here. Minor gains are possible from a concrete PR-listing command example and an error-recovery branch for missing release tags.

Suggestions

Add a concrete example command for step 1 (e.g. a gh pr list / git log range snippet) so the "list merged PRs in that range" step is copy-paste ready.

Add a short error-recovery branch for when the last release tag or changelog entry cannot be found, so the workflow has an explicit feedback loop for that failure case.

Trim the opening paragraph that restates the frontmatter description to remove the small redundancy and lift conciseness toward a 5.

Dimension	Reasoning	Score
Conciseness	Lean and efficient with no tutorializing of concepts Claude already knows; not a 5 because the opening paragraph slightly restates the frontmatter's value statement and the third-party-content admonition is a generic restatement.	4 / 5
Actionability	Gives concrete acceptance criteria for each checklist item, specifies gh/glab, the tag/changelog range source, and a precise output table contract with a --instructions customisation example; not a 5 because step 1 leaves the command to list merged PRs in a range abstract rather than a copy-paste example.	4 / 5
Workflow Clarity	A clear three-step sequence (find window, check each item, report) with a built-in per-item pass/fail/evidence verification checkpoint and explicit output contract; not a 5 because there is no error-recovery branch for when the release range or last tag cannot be determined.	4 / 5
Progressive Disclosure	A single-purpose skill under 50 lines with no external references needed and well-organized section headers, meeting the rubric's simple-skill exception for a top score.	5 / 5
	Total	17 / 20 Passed

Description

87%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, specific description that clearly states what the skill does and when to use it, with concrete release-checklist triggers and low conflict risk. The only minor gap is trigger-term synonym breadth.

Dimension	Reasoning	Score
Specificity	Names the release-readiness domain plus several concrete checklist items ("migrations, feature flags, changelog, and docs"), listing several specific actions with only minor coverage gaps; not a 5 because it frames one composite walk-the-checklist action rather than multiple distinct top-level actions.	4 / 5
Completeness	Explicitly answers both what ("Walk a release readiness checklist ... and report what is missing") and when ("Use before a release window so problems surface while there is still time to fix them") with a concrete trigger phrase.	5 / 5
Trigger Term Quality	Includes natural release-prep terms ("release readiness", "checklist", "release window", "migrations", "feature flags", "changelog", "docs") that users would actually say; not a 5 because it lacks synonym expansion like "ship", "deploy", or "cut a release".	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (pre-release readiness gating) with distinct triggers (migrations, feature flags, changelog, docs, release window) and minimal overlap with other skills.	5 / 5
	Total	18 / 20 Passed

Validation

100%

Warnings & errors only

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.

Reviewed

6 days ago

Table of Contents

Discovery Implementation Validation