release-checklist

Generates a comprehensive pre-release validation checklist covering build verification, certification requirements, store metadata, and launch readiness.

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

87%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is a well-structured, actionable checklist generator with strong conciseness and organization. Its main weakness is the absence of validation/fallback steps when loading project context, which leaves the workflow without error-recovery checkpoints.

Suggestions

Add a validation/fallback step in Phase 2 for when CLAUDE.md or a milestone file is missing (e.g., note the gap and proceed with defaults) to close the workflow-clarity validation gap.

Specify how to locate test output/CI logs concretely in Phase 3 rather than the vague 'any test output directories or CI logs if available'.

Add a brief verification pass before presenting the checklist (e.g., confirm FIXME/HACK counts were gathered and platform sections match the argument) to introduce an explicit feedback loop.

Dimension	Reasoning	Score
Conciseness	The body is lean with no concept explanations Claude already knows; the substantial length is the checklist template deliverable itself, so every token earns its place per the 'lean and efficient' anchor.	3 / 3
Actionability	Provides concrete, executable guidance — specific file reads ('CLAUDE.md', 'production/milestones/'), TODO/FIXME/HACK counting, and a copy-paste-ready markdown checklist template — matching 'fully executable; copy-paste ready'.	3 / 3
Workflow Clarity	The six phases are clearly sequenced with a confirmation gate before writing, but there are no validation steps or fallbacks (e.g., if the milestone file or CLAUDE.md is absent), fitting 'steps listed but validation gaps; checkpoints missing or implicit'.	2 / 3
Progressive Disclosure	A self-contained single-file skill with no bundle files, organized into clearly delineated phases and sections with no nested references, which scores 3 for a well-organized self-contained skill.	3 / 3
	Total	11 / 12 Passed

Description

67%

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 is specific and distinctive about its release-readiness niche, but it omits any explicit trigger guidance, capping completeness and limiting trigger-term quality. Adding a 'Use when...' clause with natural launch/release keywords would raise both dimensions.

Suggestions

Append an explicit trigger clause, e.g. 'Use when preparing to ship a release, running a go/no-go review, or finalizing store/certification submission.'

Add natural user-facing trigger terms such as 'ship', 'launch', 'go/no-go', and 'cert submission' to broaden trigger-term coverage.

Optionally mention the platform argument hint in the description so users know it is parameterizable.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete coverage areas ('build verification, certification requirements, store metadata, and launch readiness') tied to a specific generating action, matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	Clearly states what the skill does but provides no explicit 'Use when...' trigger guidance, so per the judging guidelines completeness is capped at 2 ('has what, but when is missing or only implied').	2 / 3
Trigger Term Quality	Contains relevant terms ('pre-release validation checklist', 'launch readiness') but omits common natural variations users would say ('ship readiness', 'go/no-go', 'cert submission') and lacks any trigger phrase, fitting 'some relevant keywords but missing common variations'.	2 / 3
Distinctiveness Conflict Risk	Occupies a clear niche (pre-release validation for a launch) with domain-specific terms unlikely to overlap with other skills, matching 'clear niche with distinct triggers'.	3 / 3
	Total	10 / 12 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
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
Commit: 984023d

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.