Skip to content
OpenAgentSkill
Browsing is open · Catalog captured 2026-11-21 · Automatic updates and account services are paused.
Security

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 reviews, post-launch monitoring. Use when the user says 'checklist for the site', 'ready to ship', 'before I go live', 'ready for prod', 'audit before launch', or asks for a site review, pre-launch audit, or help launching a site or app, deploying a domain to production, or shipping a marketing, docs, SaaS, or lead-magnet site.

samber · AI review on file

Installation

Read the source and dependencies before running a command. Copying does not install or execute anything.

npx skills add samber/cc-skills --skill site-launch-checklist

About this skill


name: site-launch-checklist description: "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 reviews, post-launch monitoring. Use when the user says 'checklist for the site', 'ready to ship', 'before I go live', 'ready for prod', 'audit before launch', or asks for a site review, pre-launch audit, or help launching a site or app, deploying a domain to production, or shipping a marketing, docs, SaaS, or lead-magnet site." license: MIT compatibility: Designed for Claude Code, Codex or similar harness. Requires internet access for directory submissions, G2/Capterra reviews, and AI citation checks. user-invocable: true metadata: author: samber version: "2.0.1" openclaw: emoji: "📊" homepage: https://github.com/samber/cc-skills install: - kind: npm package: skills bins: [skills] - kind: brew formula: jq bins: [jq] requires: bins: - curl - npm - npx - jq allowed-tools: Read Edit Write Glob Grep Agent AskUserQuestion

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.

Site Launch Checklist

Pre-launch audit and setup workflow for shipping a new website. Opinionated for Cloudflare DNS + Vercel hosting + PostHog + Legal context.

Interaction style (READ FIRST)

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):

  1. Site type: doc-site | marketing/lead-gen | SaaS-app | training/paid-course | personal-portfolio
  2. Migration: greenfield-new-domain | migration-need-301-redirects | replacing-existing-on-same-domain
  3. Multilingual: single-locale | en | fr+en | other-multi
  4. PostHog setup: hogpost.samber.dev | set-up-new-proxy | skip-PostHog
  5. AI scraper policy: use-default-for-site-type | customize-per-bot | block-all
  6. Browser tool available: claude-chrome-extension | playwright | neither-skip-browser-checks

Ask again at every decision point throughout the phases, including:

  • Whether to install Sentry / BetterStack / Crisp (depends on site type, ask explicitly)
  • www vs apex canonical preference (most sites: apex; ask anyway)
  • Which AI bots to allow if user chose customize-per-bot
  • CSP tightness level: strict-default-src-none | balanced-allow-self | permissive-for-marketing
  • Whether to skip a phase entirely (e.g., skip Phase 3 if non-FR site)

Never 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.

How to use this skill

  1. Run the start-of-session questions above.
  2. Walk the user through phases 1-10 in order. For each phase: a. List items, ask if any should be skipped. b. For each remaining item, run the verification command (see "Verification tools" below). c. Report pass/fail. On fail, ask the user if they want to fix now or queue for later.
  3. End with a status report grouped by phase, with blockers, recommended fixes, and optional improvements clearly separated.

Companion skills

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.

Pack inventory

PackWhat it coversTypically useful for
AgriciDaniel/claude-seoSEO + GEO + schema + hreflang + sitemaps audits, parallel sub-agentsAll site types
addyosmani/web-quality-skillsLighthouse, Core Web Vitals, accessibility, performance, best practicesAll site types
trailofbits/skillsSecurity audit (OWASP, headers, dependencies)All site types
aaron-he-zhu/seo-geo-claude-skills20 SEO+GEO skills, CORE-EEAT + CITE frameworks, /seo: slash commandsContent-heavy sites, competitive niches
coreyhaines31/marketingskills~30 marketing skills (CRO, copywriting, ads, popups, email, paywalls, etc.)marketing/lead-gen, SaaS-app, training/paid-course
jonathimer/devmarketing-skills33 developer-marketing skills (persona, docs-as-marketing, technical tutorials, etc.)doc-site, SaaS-app for developers

Skill selection workflow (run at session start)

After the user confirms site type, for each pack relevant to that site type:

  1. List available sub-skills: npx skills add owner/repo --list
  2. Propose a curated subset based on site type and the phases this skill will execute. Match each phase's needs to specific sub-skills the listing returns.
  3. Confirm with the user. Use multi-select when the proposed list has more than 3 items, single-select (install-as-proposed | let-me-modify | skip-this-pack) otherwise.
  4. Bulk install the agreed subset: npx skills add owner/repo --skill A B C

Rules:

  • Sub-skill names live in the pack, not in this SKILL.md. Always query --list for the current state. Pack contents change.
  • Never run npx skills add owner/repo without --skill (that installs everything).
  • Site type →
Read the complete source ↗