launch-runbook SKILL.md skillA
launch-runbook from rampstackco/claude-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add rampstackco/claude-skills/launch-runbook@git:20260507.ac2b078Pins git:20260507.ac2b078 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- rampstackco/claude-skills
- Path
skills/launch-runbook/SKILL.md- Versions recorded
- 3
- Latest version
- git:20260507.ac2b078, committed May 7, 2026
- First version recorded
- Apr 28, 2026
- Size
- 7,870 bytes
- Repository stars
- 1,037
- License
- MIT
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…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Launch Runbook Plan and execute the launch of a website, product, or major release. The runbook is the document everyone uses on launch day. Stack-agnostic. This skill is for the launch event. For pre-launch QA, use `qa-testing`. For post-launch incident handling, use `incident-response`. --- ## When to use - Launching a new website or major redesign - Migrating from one platform to another - Releasing a major product or feature - Coordinating cross-team launches - Building a runbook for a recurring deploy ## When NOT to use - Pre-launch testing (use `qa-testing`) - Post-launch incident response (use `incident-response`) - After-launch retrospective (use `after-action-report`) --- ## Required inputs - The launch scope (what's being launched) - The launch window (date, time, duration) - The team (roles, on-call rotation) - The rollback criteria (when to abort) - The communication plan (who tells whom what, when) --- ## The framework: 4 phases A launch has four phases. The runbook covers all four. ### Phase 1: Pre-launch (T-30 days to T-1 hour) Verify everything is ready before the launch window. **T-30 days:** - Final scope locked …
Read the whole file at its exact version.
How to install
mdr add rampstackco/claude-skills/launch-runbook@sha256:8d1f7b18667dfd50The line at the top of this page pins the label git:20260507.ac2b078, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_x4l4irv2pxvjomaa)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Apr 28, 2026 and May 7, 2026, about one every 4 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260507.ac2b078 latest | 2026-05-07 | ac2b078 | 7,870 B | A | view · diff |
| git:20260505.c80b896 | 2026-05-05 | c80b896 | 7,836 B | A | view · diff |
| git:20260428.f066ffe | 2026-04-28 | f066ffe | 7,727 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (7870 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
rampstackco/claude-skills · 1,037 stars · license MIT · pushed 2026-10-27 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_x4l4irv2pxvjomaa GET https://markdownregistry.com/api/v1/resolve?ref=rampstackco/claude-skills/launch-runbook GET https://markdownregistry.com/api/v1/blob/8d1f7b18667dfd507d3bdfb31858f5b5ff48205230060785cff40701e8a21adf
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.