Install any skill in seconds. Free to start, no credit card required.
Get Started Free →donchitos/launch-checklist
Complete launch readiness validation covering every department: code, content, store, marketing, community, infrastructure, legal, and go/no-go sign-offs.
Passed 16 of 18 test cases with the skill, and 6 of 18 without it.
and 13 more in the full report
10 fixed6 passed either way2 still failing0 broke4 errored
Tokens, turns and time describe resource use, not a dollar price.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
We ran /launch-checklist on a project where project.stage is set to Polish. The checklist generated successfully. What specific command should Phase 6 recommend running before proceeding with release?
| Checked | Without skill | With skill |
|---|---|---|
| Recommends running /gate-check release in Phase 6 when project.stage is set to Polish | Missed | Passed |
The instructions your model reads when the skill loads.
!bash "${CLAUDE_SKILL_DIR}/../../hooks/yaml-helper.sh" resolve_config --keys rigor,workflow,project.stage,cert_tier,automation
Automation mode: Resolve modes.automation (project.local.yaml →
project.yaml → default collaborative). Every AskUserQuestion call and
every file write follows .claude/docs/automation-modes.md
(collaborative asks always · guided major-only · autonomous logs and proceeds;
automation_always_ask categories always prompt).
Resolved above — use as-is. No block → defaults in .claude/docs/config-resolution.md.
Scope this checklist to the project. Emitting every item for every platform trains the reader to skip the list, which defeats the gate:
project.stage — items for phases this project has not reached are out of
scope; say so rather than listing them unchecked.
modes.rigor — at minimal, drop items whose only justification is process
weight this project has opted out of.
platform.cert_tier — emit certification items only for the tier the
project targets. If it is unset, ask which platforms are in scope
rather than emitting all of them — an unset value is a question, not a licence
to emit every certification track. The answer, mapped onto the four values
below, is the tier for this run. If it cannot be determined, mark the section
NOT ASSESSED — cert tier unknown. Unset is not none: none is a
decision, unset is a missing one, and they must not produce the same output.
Branch on the four values this key takes — none | itch | steam | console —
and not on platform names. The full requirement table is the ## platform.cert_tier
section of .claude/docs/effects-map.md — read only that section (Grep its
heading, then a bounded Read); the file as a whole is not a runtime input.
none — emit no certification section at all. Internal release, alpha or
jam game. Say the section was omitted and why; do not leave it blank.itch — itch.io upload requirements only: build size, page setup, age tags.
No console and no Steamworks items.steam — Steamworks: store page, depot build, achievements, system
requirements, common content rules. No console certification items.console — full platform certification (TRC / XR / Lotcheck), save-data
rules, controller-mapping rules, age-rating boards. The heaviest tier.Branch on the
cert_tiervalues above, not on platform names. "Emit
test cases passed, vs 6 / 18 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.