The body is lean operational guidance with no padding of concepts Claude already knows (e.g., no explanation of what DNS or a rollback is); every section — phases, roles, rollback, comms, failure patterns — earns its place. It is not the level below because there is no unnecessary explanation that could be tightened further.

Provides concrete, specific guidance: T-30/T-7/T-1/T-1hr timelines, a 12-step numbered cutover sequence with owners/verifications, explicit rollback triggers, and exact update cadences ('Every 15 minutes during cutover'). It is not the level below because the direction is specific and copy-ready rather than abstract; absence of code is acceptable for this instruction-only operations skill.

A clear four-phase sequence with explicit validation checkpoints ('Verify deploy completed without errors', 'Run smoke tests on production', 'Verify each step before moving to next') and rollback as an error-recovery feedback loop, plus checklists. It is not the level below because checkpoints are explicit and the rollback loop is documented, not merely implied.

Well-sectioned overview in SKILL.md with a single clearly-signaled, one-level-deep reference to a real file ([references/runbook-template.md]). It is not the level below because the reference is shallow, real, and clearly signaled rather than nested or broken.

Lists multiple specific concrete actions — 'pre-launch verification, go-live procedures, DNS cutover, post-launch monitoring, and rollback procedures' — rather than vague language. It is not the level below because it goes beyond naming a domain to enumerate several discrete operations.

Clearly answers both what ('Plan and execute a launch runbook covering...') and when ('Use this skill whenever the user is preparing to launch...'). It is not the level below because the trigger guidance is explicit, not merely implied.

'Triggers on launch runbook, go-live, launch day, DNS cutover, deploy to production, site launch, product launch, cutover plan, launch checklist, deployment procedure' gives broad coverage of natural terms a user would say. It is not the level below because it includes many common variations rather than a single keyword.

Occupies a clear launch-runbook niche with distinct triggers (DNS cutover, go-live, launch day) unlikely to fire for unrelated skills. It is not the level below because the scope is narrowly bounded to the launch event rather than overlapping generic deploy/QA skills.