CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

release-checklist

Pre-release checklist — build verification, certification requirements, store metadata, launch readiness.

Quality

75%

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

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/release-checklist/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

This is a strong, highly actionable skill: every phase yields concrete, executable output with explicit validation, NOT ASSESSED semantics, and precise config-driven gating that distinguishes unset from decided values. Its one real weakness is token efficiency — the cert_tier and unset-vs-none rules are restated nearly verbatim across three sections, and the inlined per-tier templates make the file longer than it needs to be.

Suggestions

State the cert_tier rule (including "unset is not none") once in the top scoping section and reference it from Phase 1 and Phase 4 instead of repeating it nearly verbatim three times.

Move the four per-tier certification template blocks and the per-platform device blocks into references/ files keyed by tier, keeping only the gating logic and the "none" one-liner inline in SKILL.md.

Consolidate the repeated blockquote warnings about console/cert_tier vocabulary collision into a single canonical statement in the scoping section.

DimensionReasoningScore

Conciseness

The body repeats its core rules verbatim multiple times — "Unset is not none: none is a decision, unset is a missing one" appears at both the top scoping section and again in the Phase 4 certification subsection, and the branch-on-cert_tier-not-platform-names warning is stated three times — which is tightening-eligible padding, though it never explains concepts Claude already knows.

3 / 5

Actionability

Guidance is fully executable: exact grep commands ("grep the **Severity** and **Status** lines of production/qa/bugs/*.md"), complete copy-paste markdown templates per tier and platform, exact NOT ASSESSED strings, and a first-match-wins Go/No-Go decision rule.

5 / 5

Workflow Clarity

Six phases are clearly sequenced with explicit validation checkpoints: the state-the-denominator rule in Phase 3, ask-before-write in Phase 5, the unset-to-ask fallback for cert_tier, and NOT ASSESSED precedence rules in the Go/No-Go logic.

5 / 5

Progressive Disclosure

The body is well organized into phases and correctly defers the full requirement table to .claude/docs/effects-map.md with a bounded-read instruction ("read only that section (Grep its heading, then a bounded Read)"), but at ~315 lines with every per-tier and per-platform template inlined, SKILL.md is heavier than an overview and some template blocks belong in reference files.

4 / 5

Total

17

/

20

Passed

Description

61%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 communicates a specific domain and four concrete coverage areas but reads as a topic list rather than a capability statement, and it entirely lacks a "when to use this" trigger clause. Adding verb-led actions and an explicit "Use when..." clause with natural synonyms (ship, go-live, release candidate) would lift both completeness and trigger quality.

Suggestions

Add an explicit trigger clause, e.g. "Use when preparing to ship a release, before running /gate-check release, or when the user mentions release readiness, shipping, or going live."

Rewrite the area list with verb-led capabilities ("Verifies clean builds, audits platform certification requirements, reviews store page metadata, assesses launch readiness") so it states actions, not just topics.

Include natural synonyms such as "ship", "go-live", and "release candidate" to broaden trigger-term coverage beyond the current four labels.

DimensionReasoningScore

Specificity

"build verification, certification requirements, store metadata, launch readiness" names four concrete areas but they are noun-phrase deliverable categories with no verb-led actions, matching anchor 3 (domain named, concrete actions limited) rather than anchor 4 (specific actions listed).

3 / 5

Completeness

The "what" is clear (a pre-release checklist covering four named areas) but there is no "Use when" clause or equivalent trigger guidance anywhere, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

"Pre-release", "checklist", "certification", "launch readiness", "store metadata" are natural phrases users would say when needing this skill, though common synonyms like "ship", "go-live", or "release candidate" are missing, placing it just below anchor 5.

4 / 5

Distinctiveness Conflict Risk

The pre-release-gate niche is mostly distinct, but "launch readiness" overlaps the separate /launch-checklist skill referenced in the body, leaving minor conflict risk rather than a clear standalone niche.

4 / 5

Total

14

/

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

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository

Donchitos/Claude-Code-Game-Studios

Path

.claude/skills/release-checklist/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.