Individual skill

go-live

Use this skill for the go/no-go check before real customers use the app and pay: 'am I ready to launch,' 'is it ready to go live,' 'pre-launch checklist,' 'deploy my app,' 'set up my domain,' 'how do I know if my site goes down,' or 'set up backups.' Checks the core flow, payments, security basics, backups with a restore test, error tracking, uptime alerts, and rollback, then gives a verdict. Not for the launch announcement itself (use first-customers) or for a full security audit (use secure).

skills/go-live/SKILL.md

Read pinned source

Source commit 01bd10f79a4b6a741be78e3184612a90ecbd54ef

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: No
Repository scan complete: No
Skill scan complete: Yes
Observed behavior: Not checked yet
Last checked: Nov 7, 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): 262
Repository last updated: Oct 16, 2026
License: MIT

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

security Derived category
testing Derived category

Files and excerpt

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

Browse files

SKILL.mdcore · 3,817 bytes

Read excerpt


# Go Live

A gate, not a process. Check the app the way a stranger with a credit card would meet it. Pass, and the founder lets customers in. Fail, and the founder fixes the showstoppers first.

## Step 1: Deploy, if not live yet

- Use a managed host that deploys from git, so every push deploys.
- Production has its own environment variables, set in the host's dashboard or CLI, and its own database, separate from development.
- Connect the custom domain at the host. The host lists the DNS records to add.
- Skip a staging environment until there are paying customers.
- The first deploy should take under 30 minutes. If it takes hours, simplify.
- "Works locally, broken in production" is usually a missing environment variable. Check those first.

## Step 2: Showstoppers (all must pass)