| name | website-launch-readiness |
| description | Website launch readiness for SEO, Cloudflare, analytics, performance, security.txt, and AI-agent discovery. |
Website Launch Readiness
Use this skill to make a web surface launch-ready without mixing marketing, portal, and infrastructure scopes.
Use
- Identify the canonical surface owner, then read
references/checklist.md.
- Implement only owner-level launch fixes, deploy, verify live, and report stale third-party scans separately from current evidence.
Scope Rules
- Keep public marketing content and authenticated portal content separate
- For portals, expose only product/operational public documentation to agents. Do not expose private workspace data, task text, user records, tokens, or authenticated API schemas
- For Cloudflare findings, do not mutate unrelated
workers.dev, staging, or sibling-zone findings unless the user explicitly scopes them
- MFA and account-user findings are owner actions. Report them instead of attempting account takeover-style setup
Validation
At minimum, verify live URLs with curl -I, fetch text endpoints directly, run available typecheck/build/tests, and run the repo push/dry-run gate when repo policy requires it.
