Menu

Individual skill

pre-launch

Gate a website launch from its repository — repo hygiene, placeholders and leaked dev hosts, the production build, the build output (404 page, internal references, icons, social cards, robots, sitemap, canonicals, titles, headings), framework configuration, and redirect coverage for the site being replaced — then walk the human checklist no script can verify. Use before any site launch, before a DNS cutover, when a site is replacing an existing one, or when somebody asks whether a site is ready to launch. Read-only apart from its own report and a progress file; it exits 1 if anything fails.

skills/pre-launch/SKILL.md

Read pinned source

Source commit 8beb1de5099a2be1ddb1d98ffc7b3682343bc420

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
123
Repository last updated
Oct 31, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# pre-launch

The gate. It inspects the repository and the build, and it blocks the launch if anything
mechanical is wrong. Then it hands you up to nine things no script can check.

## The two rules

**Never declare the site ready while any check fails.** There is no flag that turns a failure into
a warning, and adding one would be the wrong fix. Exit 1 means not ready. If you believe a check is
wrong about this site, say so plainly to the human and fix the check — do not route around it.

**Never reorder the human list.** Its order is a dependency order with two one-way doors in it:
the Search Console baseline must be exported **before DNS moves**, and the forms must reach a real
person **before the deploy** that makes them public. Both are unrecoverable if taken late.