CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

launch-checklist

Launch readiness across every department: code, content, store, marketing, community, infrastructure, legal, go/no-go sign-offs.

Quality

74%

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

Quality

Content

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

The body is a rigorously specified, fully actionable six-phase workflow with outstanding validation discipline — denominator reporting for every scan, a deterministic Go/No-Go precedence rule, tier-gated output, and user confirmation for unresolvable items. Its weaknesses are repetition (the cert_tier rule restated and re-justified in multiple places) and a large inlined checklist template that belongs in a separate reference file, which together cost both conciseness and progressive-disclosure points.

Suggestions

Move the Phase 4 checklist template to a bundle file such as references/checklist-template.md and reference it from the phase (e.g., "Render the template from references/checklist-template.md"), cutting the SKILL.md body roughly in half.

State the cert_tier gating rule once in the scope section and have the Platform Certification section point back to it ("gated per the cert_tier rule above") instead of restating and re-justifying it with blockquotes.

Compress rationale blockquotes ("Emitting every item for every platform trains the reader to skip the list...", "A test on target platforms treats an itch project and a steam project identically...") into single-line imperatives such as "Branch on cert_tier values, never platform names."

DimensionReasoningScore

Conciseness

The bulk is dense, project-specific instruction Claude would not know (config keys, phases, gating rules), but it could be tightened: the cert_tier rule is stated three times (top scope section, Platform Certification section, and the "> Branch on the cert_tier values above" blockquote), and rationale blockquotes like "Emitting every item for every platform trains the reader to skip the list, which defeats the gate" and "A test on target platforms treats an itch project and a steam project identically..." explain why at essay length. This is anchor 3 (mostly efficient, some unnecessary explanation), not 2, since nothing explains concepts Claude already knows and the duplication is limited to a few motifs.

3 / 5

Actionability

Fully executable for an instruction-only skill: exact search targets ("TODO, FIXME, HACK", "console.log, print()", "placeholder, temp_, WIP_"), exact output strings ("[?] = not assessed — the input to this check was absent"), a complete copy-paste-ready checklist template, exact AskUserQuestion option labels, an exact write path ("production/releases/launch-checklist-[date].md"), and a deterministic first-match-wins Go/No-Go rule. Anchor 5 — specific guidance covers the common cases with no gaps.

5 / 5

Workflow Clarity

Six clearly ordered phases with explicit validation checkpoints throughout: "Establish the denominator before every scan, and report it", Phase 4b user confirmation, explicit failure handling ("If it cannot be determined, mark the section NOT ASSESSED — cert tier unknown"), and a permission gate before the only write ("Create nothing before the answer — not even the production/releases/ directory"). The destructive/batch validation cap does not apply: the sole write is gated by dry-run mode and explicit permission. Matches anchor 5 — clear sequence, explicit checkpoints, checklists for the complex process, and error-recovery paths for every failure mode.

5 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are absent), and external references are exceptionally well signaled and bounded ("read only that section (Grep its heading, then a bounded Read)" for .claude/docs/effects-map.md). However, the ~230-line checklist template inlined in Phase 4 is content that clearly belongs in a separate template file — it roughly doubles the SKILL.md body. This fits anchor 3 (content that should be separate is inline); it is not 4 because the inlined template is a major placement gap, not a minor one, and not 2 because overall structure and navigation are otherwise good.

3 / 5

Total

16

/

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 clearly conveys scope — launch readiness spanning seven named departments culminating in go/no-go sign-offs — and uses natural trigger language around "launch". Its main weakness is the absence of any 'when to use this' guidance and of concrete actions describing what the skill actually does (generates a launch checklist, scans code, collects sign-offs), leaving it a scope statement rather than a full capability statement.

Suggestions

Add an explicit trigger clause, e.g.: "Use when preparing for a game release, running a launch readiness review, or making a go/no-go decision."

State the concrete actions the skill performs: generates a project-scoped launch checklist, scans the codebase for TODOs/debug output/placeholder assets, and collects department sign-offs.

Include common synonyms such as "release readiness", "ship readiness", and "launch checklist" to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

Names the domain ("Launch readiness across every department") and enumerates departments ("code, content, store, marketing, community, infrastructure, legal") plus one concrete deliverable ("go/no-go sign-offs"), but uses no action verbs for what it does (e.g., generate a checklist, scan the codebase, collect sign-offs). This matches anchor 3 (domain + 1-2 concrete actions) rather than 4, which requires several specific actions listed.

3 / 5

Completeness

The 'what' is present ("Launch readiness across every department... go/no-go sign-offs") but there is no "Use when..." clause or any equivalent explicit trigger guidance, which caps completeness at 3. It is not a 4 because 'when' is entirely absent rather than merely less explicit.

3 / 5

Trigger Term Quality

Includes natural phrases users would say — "Launch readiness", "go/no-go sign-offs", "store", "marketing" — giving good keyword coverage. It is not a 5 because common synonyms and variations are missing: no "release readiness", "ship", "pre-launch", or "checklist".

4 / 5

Distinctiveness Conflict Risk

"Launch readiness" plus "go/no-go sign-offs" carves a mostly distinct niche with minor overlap risk against a generic release/deployment skill. Not a 5 because the description does not anchor its triggers to an unambiguous context, leaving some overlap with general 'release readiness' or rollout skills.

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/launch-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.