Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →samber/site-launch-checklist
Pre-launch checklist for shipping a new website or web app. Scope: analytics (GA4, PostHog, Google Search Console, Ahrefs), DNS, TLS and backups, legal and CNIL/GDPR compliance, security headers, SEO and GEO (robots.txt, sitemaps, llms.txt, hreflang, schema markup, keyword research), copywriting voice via TONE.md and a humanizer pass, OpenGraph and social previews, favicons and web manifest, Lighthouse, Core Web Vitals and WCAG quality gates, directory submissions, Product Hunt, G2/Capterra revi
Passed 22 of 23 test cases with the skill, and 16 of 23 without it.
and 5 more in the full report
6 fixed16 passed either way1 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are getting ready to push our platform live on Cloudflare and Vercel and need a structured pre-ship review. Please conduct an interactive audit session with me, asking questions at decision checkpoints rather than making assumptions. At the end of the run, present a phase-grouped status breakdown along with distinct lists of critical blockers, suggested fixes, and optional improvements.
| Checked | Without skill | With skill |
|---|---|---|
| Prompts with the initial interactive question asking for site type. | Missed | Passed |
| Asks initial setup questions sequentially one at a time. | Missed | Passed |
The instructions your model reads when the skill loads.
Questions: Ask the user through the environment's question tool — never as plain-text prose. One question at a time, 2–4 tappable options, wait for the answer. If the environment has no question tool, ask in prose with the same options, one at a time.
Pre-launch audit and setup workflow for shipping a new website. Opinionated for Cloudflare DNS + Vercel hosting + PostHog + Legal context.
This skill is intentionally interactive. Ask aggressively instead of assuming. The user will tap, not type.
Always ask these questions at the start of a run (one at a time, in this order):
doc-site | marketing/lead-gen | SaaS-app | training/paid-course | personal-portfoliogreenfield-new-domain | migration-need-301-redirects | replacing-existing-on-same-domainsingle-locale | en | fr+en | other-multihogpost.samber.dev | set-up-new-proxy | skip-PostHoguse-default-for-site-type | customize-per-bot | block-allclaude-chrome-extension | playwright | neither-skip-browser-checksAsk again at every decision point throughout the phases, including:
customize-per-botstrict-default-src-none | balanced-allow-self | permissive-for-marketingNever proceed past a decision point without explicit user input. Verbose checklists without checkpoints are not the goal.
Never install any MCP server or skill without explicit user confirmation. Always ask via the question tool before running npx skills add, claude mcp add, or any equivalent install command — even when the skill selection workflow proposes a curated subset.
Six skill packs are useful for site launches. Never install full multi-skill packs. The actual subset to install is decided at invocation time based on the site type the user confirms.
test cases passed, vs 16 / 23 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.