launch-runbook

Plan and execute a launch runbook covering pre-launch verification, go-live procedures, DNS cutover, post-launch monitoring, and rollback procedures. Use this skill whenever the user is preparing to launch a website or product, planning a DNS cutover, building a go-live checklist, or executing a launch day. Triggers on launch runbook, go-live, launch day, DNS cutover, deploy to production, site launch, product launch, cutover plan, launch checklist, deployment procedure. Also triggers when a launch is approaching and the team needs structured coordination, even if 'runbook' is not explicitly stated.

Quality

96%

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

Quality

Content

92%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 content is well-structured, concise, and assumes Claude's competence, with a clear phased workflow and strong validation/rollback checkpoints. The only gap is that executable command specifics live in the template rather than the body, leaving a few steps as placeholders.

Suggestions

For the most common cutover steps (deploy, DNS cutover, maintenance mode), include one concrete example command or tool alongside the 'if applicable' placeholder so the body is copy-paste ready for the standard case.

Add a short inline snippet showing the expected internal status-channel update format ('[Time] - [Step name] - [Status]') since the comms cadence is otherwise described but not exemplified in the body.

Consider noting near the cutover sequence that the template's per-step fields (owner, pre-condition, verification, rollback) are mandatory to fill, reinforcing the validation gate before day-of execution.

Dimension	Reasoning	Score
Conciseness	Lean and efficient throughout — it assumes Claude's competence, never explains what a launch or DNS cutover is, and every section earns its place without padding.	5 / 5
Actionability	Provides concrete numbered cutover steps, specific timing anchors, and rollback thresholds, but the actionable commands are placeholders ('if applicable', '[Specific command]') with the executable specifics deferred to the template rather than inlined.	4 / 5
Workflow Clarity	Clear four-phase sequence with explicit validation checkpoints (go/no-go meeting, smoke tests after each step, rollback criteria and decision authority, tabletop exercise), satisfying the destructive/batch feedback-loop requirement.	5 / 5
Progressive Disclosure	The body is an overview that signals a single one-level-deep reference to references/runbook-template.md (a real file), with no nested references and clear section navigation.	5 / 5
	Total	19 / 20 Passed

Description

100%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 is exemplary: it states concrete capabilities, provides comprehensive natural trigger terms, answers both what and when explicitly, and carves out a distinct, low-conflict niche. It uses appropriate third-person voice and avoids verbosity.

Dimension	Reasoning	Score
Specificity	Lists five concrete capability areas — 'pre-launch verification, go-live procedures, DNS cutover, post-launch monitoring, and rollback procedures' — giving comprehensive, specific coverage rather than vague abstraction.	5 / 5
Completeness	Explicitly answers both 'what' (plan/execute a launch runbook across five phases) and 'when' ('Use this skill whenever the user is preparing to launch...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Comprehensive natural trigger terms with synonyms — 'launch runbook, go-live, launch day, DNS cutover, deploy to production, site launch, product launch, cutover plan, launch checklist, deployment procedure' — phrases a user would actually say.	5 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (the launch event itself) with distinct triggers and minimal overlap risk; the body further disambiguates from qa-testing, incident-response, and after-action-report.	5 / 5
	Total	20 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: rampstackco/claude-skills
Path: skills/launch-runbook/SKILL.md
Commit: 0479242

Reviewed: 14 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.