Site Launch Checklist
samber/cc-skills
Pre-launch checklist for shipping a new website or web app. An agent skill from samber/cc-skills.
Launch Day Autopilot — prepare everything for a product launch.
Install Launch
$ npx skills add Houseofmvps/ultraship --skill launch -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Houseofmvps/ultraship launch --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Houseofmvps/ultraship.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/launch .claude/skills/launch && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "launch" agent skill from https://github.com/Houseofmvps/ultraship/tree/main/skills/launch into .claude/skills/launch/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "launch", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Houseofmvps/ultraship/tree/main/skills/launchType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Houseofmvps/ultraship --skill launch -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Houseofmvps/ultraship launch --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Houseofmvps/ultraship.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/launch .agents/skills/launch && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "launch" agent skill from https://github.com/Houseofmvps/ultraship/tree/main/skills/launch into .agents/skills/launch/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "launch", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Houseofmvps/ultraship --skill launch -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Houseofmvps/ultraship launch --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Houseofmvps/ultraship.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/launch .cursor/skills/launch && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "launch" agent skill from https://github.com/Houseofmvps/ultraship/tree/main/skills/launch into .cursor/skills/launch/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "launch", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Houseofmvps/ultraship.git --path skills/launch--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Houseofmvps/ultraship --skill launch -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Houseofmvps/ultraship launch --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Houseofmvps/ultraship.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/launch .gemini/skills/launch && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "launch" agent skill from https://github.com/Houseofmvps/ultraship/tree/main/skills/launch into .gemini/skills/launch/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "launch", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Houseofmvps/ultraship launchInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Houseofmvps/ultraship --skill launch -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Houseofmvps/ultraship.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/launch .github/skills/launch && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "launch" agent skill from https://github.com/Houseofmvps/ultraship/tree/main/skills/launch into .github/skills/launch/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "launch", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Houseofmvps/ultraship --skill launch -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Houseofmvps/ultraship launch --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Houseofmvps/ultraship.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/launch .opencode/skills/launch && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "launch" agent skill from https://github.com/Houseofmvps/ultraship/tree/main/skills/launch into .opencode/skills/launch/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "launch", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
launch- GitHub stars
- 123
- Token cost
- ~2k tokens
- SKILL.md length
- 1,077 words
- Files
- 1
- Skills in repo
- 28
- Repo updated
- First seen
- Licence
- MIT
At a glance
Launch Day Autopilot — prepare everything for a product launch.
- Works in 8 steps: Analyze Project → Audience & Positioning → Launch Checklist → …
- User wants to launch
- SKILL.md covers Process and Key Principles
- Calls node
What it does
Launch is an agent skill from Houseofmvps/ultraship. Launch Day Autopilot — prepare everything for a product launch. Use when user wants to launch, go live, announce, or prepare for Product Hunt / Hacker News / social media launch.
Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Marketing & SEO, covering Product launch strategy and AI search optimization. The repository describes itself as: "ULTRASHIP" Claude Code plugin — 39 skills, 33 tools, 11 agents for ship-ready workflows: planning, review, pentesting, safety guardrails, canary monitoring, SEO/AI-readiness… The licence is MIT.
When your agent uses it
- User wants to launch
- Prepare for Product Hunt / Hacker News / social media launch
Example prompts
- “/launch”
Workflow steps
8 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit ed232cb. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
node
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Launch loads about 2k tokens when it runs. Until then it costs about 46 tokens; SKILL.md has 1,077 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Houseofmvps/ultraship at commit ed232cb, republished under its MIT licence (© Houseofmvps). 1,077 words, ~1,960 tokens.
Download SKILL.mdSave it as
.claude/skills/launch/SKILL.md (or your agent's skills folder).- name
- launch
- description
- Launch Day Autopilot — prepare everything for a product launch. Use when user wants to launch, go live, announce, or prepare for Product Hunt / Hacker News / social media launch.
Launch Day Autopilot
A launch is not a deploy. A deploy puts code on a server. A launch puts a product in front of people who need it, at the right time, with the right message, on the right channels. This skill treats launch as a coordinated campaign, not a checkbox.
Process
Phase 1: Analyze Project
node ${CLAUDE_PLUGIN_ROOT}/tools/launch-prep.mjs <project-directory> --url=<production-url>Parse the JSON output for project info, launch copy, checklist, and press kit.
Phase 2: Audience & Positioning
Before writing a single word of copy, nail the positioning:
Who is this for?
- Define the target user in one sentence (e.g., "Solo SaaS founders with $5K-50K MRR who are losing customers to churn")
- What is their current pain? What do they do today without this product?
- What is the single most compelling thing this product does for them?
Positioning statement:
For [target user] who [pain point], [product] is a [category] that [key benefit]. Unlike [alternatives], it [differentiator].
This positioning statement drives ALL copy below. Every piece of content should map back to it.
Competitive angle:
- What exists today that partially solves this? Why is it insufficient?
- What is the "wedge" — the one thing that makes someone try this instead? Lead with that.
Phase 3: Launch Checklist
Present the launch checklist with pass/fail/warn status:
Product Ready:
- Landing page live and fast (Lighthouse 90+)
- Signup/onboarding flow tested end-to-end
- Pricing page clear with CTA
- No console.logs, TODOs, or placeholder text visible
- Error states handled (404, 500, empty states)
SEO + AI visibility Ready:
- Meta description, OG tags, favicon, sitemap, robots.txt
llms.txtfor AI discoverability- Structured data (JSON-LD) on key pages
- AI-friendly robots.txt (GPTBot, PerplexityBot allowed)
Analytics Ready:
- Event tracking on signup, activation, and payment
- UTM parameters working for campaign attribution
- Goal/conversion tracking configured
Legal Ready:
- Privacy policy and terms of service linked in footer
- Cookie consent if serving EU users
- GDPR/data deletion path documented
Social Proof Ready:
- At least one testimonial, beta user quote, or dogfood result
- GitHub stars, npm downloads, or other traction signal visible
- Author/founder bio with credibility signals
For any FAIL items, fix them immediately.
Phase 4: Launch Copy — Platform by Platform
Product Hunt:
- Tagline (max 60 chars): Punchy, specific, no buzzwords. Lead with what it does, not what it is.
- Bad: "AI-powered productivity platform"
- Good: "Find which customers are about to churn before they cancel"
- Description (2-3 sentences): Problem → solution → proof. Include a number (users, rules, time saved).
- Maker's first comment: Personal, authentic. Why you built this. What surprised you. What's next. End with a question to drive comments.
- Gallery images (5-6): Hero screenshot, key feature 1-3, before/after or comparison, social proof. Each image should stand alone and tell a story.
Twitter/X Thread (5-7 tweets):
- Tweet 1: Hook — state the problem in a way your target user feels. No "I'm excited to announce." Start with the pain.
- Tweet 2: The aha moment — what you realized that led to building this.
- Tweet 3-4: Show, don't tell — screenshot, GIF, or concrete example of the product working.
- Tweet 5: Social proof — beta results, dogfood data, a specific number.
- Tweet 6: The ask — try it (link), star it, share it. One clear CTA.
- Tweet 7: Bonus — what's coming next. Creates anticipation for followers.
LinkedIn Post:
- Professional tone but not corporate. Focus on the journey and the problem space.
- Lead with insight about the industry, not about your product.
- Include 3-5 hashtags (industry-specific, not generic).
- End with a question that invites comments.
Hacker News (Show HN):
- Title: "Show HN: [Product] – [What it does in plain English]"
- Body: Technical, honest, no marketing. Explain: What it does. Why you built it. How it works technically. What's interesting about the implementation. What you learned. Link to demo/repo.
- HN values: technical depth, honesty about limitations, open source, responding to every comment.
Show full SKILL.md (461 more words)Show less
Phase 5: Community Seeding Strategy
Launching on platforms is necessary but not sufficient. The products that break through have community presence before launch day:
Pre-launch (1-2 weeks before):
- Post in 3-5 relevant communities about the problem you're solving (not your product)
- Share a "building in public" update showing progress
- DM 10-20 people in your target audience for early feedback
- Ask 5 people to be ready to upvote/comment on launch day
Launch day amplification:
- Ask every early user to share on their preferred platform
- Cross-post between platforms (PH post links to Twitter thread, Twitter links to HN)
- Respond to every comment within 1 hour — engagement velocity matters for algorithms
- Share real-time metrics updates ("50 signups in the first 2 hours") — progress updates drive curiosity
Post-launch (3-7 days after):
- Follow up with everyone who signed up but didn't activate
- Publish a "launch retrospective" blog post with real numbers
- Submit to newsletters and curated lists in your niche
- Update the product based on launch day feedback and announce the updates
Phase 6: Press Kit
Present the press kit components:
- One-liner description (from positioning statement)
- Elevator pitch (3 sentences: problem, solution, proof)
- Tech highlights (for technical publications)
- Key features list (5-7 bullet points, benefit-led)
- Founder bio with relevant credentials
- High-res logo and screenshot assets
Phase 7: Pre-Launch Health Check
If a production URL was provided:
node ${CLAUDE_PLUGIN_ROOT}/tools/health-check.mjs <production-url>Verify the site is up, fast, and SSL is valid. Run /seo to ensure all SEO + AI visibility signals are in place. Nothing worse than going viral with a broken OG image or a 4-second LCP.
Phase 8: Launch Day Timeline
Generate a suggested launch day timeline (all times in user's timezone):
| Time | Action | Why |
|---|---|---|
| 6:00 AM PT | Submit to Product Hunt | Optimal for full-day upvote accumulation |
| 6:15 AM PT | Post maker's first comment on PH | Sets the tone, shows you're responsive |
| 7:00 AM PT | Tweet the announcement thread | Catches morning scrollers |
| 7:30 AM PT | Post in 2-3 Slack/Discord communities | Warm audiences convert best |
| 8:00 AM PT | Post on LinkedIn | Professional audience online |
| 9:00 AM PT | Submit to Hacker News (Show HN) | HN peaks mid-morning ET |
| 12:00 PM PT | Engage with all platform comments | Engagement velocity signals quality |
| 3:00 PM PT | Share progress update with real numbers | Social proof drives late-day interest |
| 6:00 PM PT | Thank early users, share key metrics | Gratitude posts perform well |
| Next day | Follow up everywhere, respond to all comments | Sustained engagement > launch-day spike |
Key Principles
- Launch is a performance, not a deploy. Every piece of copy, every checklist item, every timing decision matters.
- Specificity beats superlatives. "63 SEO rules" beats "comprehensive SEO." "Catches N+1 queries" beats "improves performance."
- Show, don't tell. Screenshots, GIFs, and real data outperform description text.
- The launch week matters more than launch day. Sustained follow-up converts more than a single spike.
© Houseofmvps, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/launch of Houseofmvps/ultraship.
Open the folder on GitHubat commit ed232cb
Compare with similar skills
Launch next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Launch this skillHouseofmvps/ultraship | 123 | — | ~2k | Automated safety check: Pass | MIT | |
| Site Launch Checklistsamber/cc-skills | 228 | — | ~13k | Automated safety check: Notes | MIT | |
| Directory SubmissionsCesarjoquin/Marketing-Skills | 199 | 1 repos | ~5.8k | Automated safety check: Pass | MIT | |
| Launch Blog Postamplitude/builder-skills | 159 | — | ~2.8k | Automated safety check: Pass | None | |
| SEO Visibility Expertcuriositech/some_claude_skills | 243 | — | ~1.6k | Automated safety check: Notes | MIT | |
| Geo Fundamentalswasp-lang/wasp | 19k | 8 repos | ~861 | Automated safety check: Pass | MIT |
Similar skills
Directory Submissions
Cesarjoquin/Marketing-Skills
When the user wants to submit their product to startup, SaaS, AI, agent, MCP, no-code, or review directories for backlinks, domain rating, and discovery.
Launch Blog Post
amplitude/builder-skills
Write technical launch blog posts optimized for both traditional SEO and AI engine citation (AEO).
SEO Visibility Expert
curiositech/some_claude_skills
Comprehensive SEO, discoverability, and AI crawler optimization for web projects.
Geo Fundamentals
wasp-lang/wasp
Generative Engine Optimization for AI search engines (ChatGPT, Claude, Perplexity).
SEO Geo
ReScienceLab/opc-skills
SEO & GEO (Generative Engine Optimization) for websites. An agent skill from ReScienceLab/opc-skills.
More from Houseofmvps/ultraship
All 28 skills in this repoUsing Ultraship
Houseofmvps/ultraship
A skill your agent uses when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
A11y
Houseofmvps/ultraship
Accessibility audit + auto-fix (WCAG 2.2 A/AA). An agent skill from Houseofmvps/ultraship.
Architecture
Houseofmvps/ultraship
Living Architecture Map — auto-generate Mermaid diagrams of your codebase.
Clone Patterns
Houseofmvps/ultraship
Learn From the Best — analyze patterns from any codebase and apply them to yours.
Code Review
Houseofmvps/ultraship
Code review with principal-engineer-level depth. An agent skill from Houseofmvps/ultraship.
Compete
Houseofmvps/ultraship
Competitive X-Ray — analyze any competitor URL vs your site.
Related
Categories
Questions about Launch
What does Launch do?
Launch Day Autopilot — prepare everything for a product launch. Launch is an agent skill from Houseofmvps/ultraship. Launch Day Autopilot — prepare everything for a product launch.
When should I use Launch?
Launch fits situations like: user wants to launch; prepare for Product Hunt / Hacker News / social media launch.
How do I install Launch in Claude Code?
Run `npx skills add Houseofmvps/ultraship --skill launch -a claude-code`. Or copy the skill folder (skills/launch in Houseofmvps/ultraship) into .claude/skills/launch in your project. Claude Code loads it when a task matches its description.
How do I install Launch in Codex?
Run `npx skills add Houseofmvps/ultraship --skill launch -a codex`. Or copy the skill folder (skills/launch in Houseofmvps/ultraship) into .agents/skills/launch in your project. Codex loads it when a task matches its description.
Can I use Launch in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Houseofmvps/ultraship --skill launch -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/launch, .gemini/skills/launch, .github/skills/launch and .opencode/skills/launch in your project.
What does Launch need to run?
Going by SKILL.md and its folder, Launch needs the command-line tools its instructions call (node).
Does Launch access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Launch safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Launch use?
Launch is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Launch use?
About 2k tokens (SKILL.md is roughly 7.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Launch?
Skills that share tags, products or a category with Launch: Site Launch Checklist (samber/cc-skills, 228 stars), Directory Submissions (Cesarjoquin/Marketing-Skills, 199 stars), Launch Blog Post (amplitude/builder-skills, 159 stars) and SEO Visibility Expert (curiositech/some_claude_skills, 243 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Launch?
Houseofmvps (a GitHub user) maintains it in Houseofmvps/ultraship, which has 123 GitHub stars. The repository holds 28 skills in this directory. The repository was last updated on July 8, 2026.
Source: Houseofmvps/ultraship on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.