launch-checklist

Complete launch readiness validation covering every department: code, content, store, marketing, community, infrastructure, legal, and go/no-go sign-offs.

Quality

68%

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/launch-checklist/SKILL.md

Quality

Content

80%

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

The content is highly actionable and concise, with specific paths, search targets, and a complete deliverable template driven by a clear phase sequence. Its main gaps are an implicit validation checkpoint before saving and a monolithic structure that inlines the full checklist rather than splitting reference material.

Suggestions

Add an explicit validation checkpoint between Phase 4 and Phase 5, e.g. 'Review the generated checklist against gathered context and confirm every department section is populated before presenting/saving.'

Consider extracting the large checklist template into a references file (e.g. references/launch-checklist-template.md) referenced one level deep, keeping SKILL.md as an overview plus phase instructions.

Make the dry-run vs. write decision and the blocking/conditional summary a single explicit verification step with a clear pass/fail framing before any file is written.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — it never explains concepts Claude already knows — and the large inlined checklist is the actual deliverable rather than padded explanation, so every token earns its place.	3 / 3
Actionability	It gives concrete file paths to read (CLAUDE.md, production/milestones/, design/live-ops/content-calendar.md), specific search targets (TODO/FIXME/HACK, console.log/print, localhost/test creds), a copy-paste-ready checklist template, and a concrete write path (production/releases/launch-checklist-[date].md).	3 / 3
Workflow Clarity	The 6-phase sequence is clear and the file write is gated by explicit user permission, but the validation checkpoint between generating the checklist (Phase 4) and saving it (Phase 5) is implicit; per the rubric, missing explicit verification in a generative/batch workflow caps workflow clarity at 2.	2 / 3
Progressive Disclosure	Sections are well-organized with clear headers and no bundle files exist, but the entire large checklist template is inlined in a monolithic SKILL.md with no external reference split; for a skill well over 50 lines this is structured but not optimally separated.	2 / 3
	Total	10 / 12 Passed

Description

57%

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 conveys a clear, distinctive niche and a comprehensive scope, but it leans on one generalized action verb and omits an explicit 'when to use' trigger clause. Adding a Use-when clause and naming concrete actions would lift specificity and completeness.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user requests a launch readiness review, pre-launch checklist, or go/no-go decision before shipping.'

Replace the single 'validation covering' phrasing with concrete actions, e.g. 'Scans codebase health, generates a per-department checklist, and collects go/no-go sign-offs.'

Include common trigger variations users would actually say: 'launch checklist', 'pre-launch', 'release readiness', 'ship readiness'.

Dimension	Reasoning	Score
Specificity	It enumerates many concrete departments (code, content, store, marketing, community, infrastructure, legal) and 'go/no-go sign-offs', but the action is essentially a single generalized verb ('validation covering') rather than multiple distinct concrete actions, so it sits at the domain-listing level rather than the multi-action anchor.	2 / 3
Completeness	It clearly answers 'what' (validation across named departments plus sign-offs) but lacks any explicit 'Use when...' trigger clause; per the rubric guideline a missing explicit trigger caps completeness at 2.	2 / 3
Trigger Term Quality	Natural terms like 'launch readiness', 'go/no-go sign-offs', and 'launch' are present, but common variations a user would say ('pre-launch', 'release readiness', 'ship readiness', 'launch checklist') are only partially covered.	2 / 3
Distinctiveness Conflict Risk	The niche is specific — full cross-department launch readiness with go/no-go sign-offs — and is unlikely to trigger for unrelated skills.	3 / 3
	Total	9 / 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/launch-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.