sales-launchlist
LaunchList platform help — viral pre-launch waitlist platform with one-time lifetime pricing, gamified referrals (queue jumping, leaderboard, position inflation), embed widget + custom form POST endpoint, new_user/email_verify webhooks, Zapier, and spam protection. Use when choosing Free (100 submissions) vs Launch $29 (500) vs Grow $79 one-time (10K — webhooks, Zapier, team unlock here), wiring waitlist signups into Mailchimp/Kit/HubSpot or a CRM because LaunchList has no email broadcast system, needing programmatic access when there is no public REST API yet (form POST + webhook workaround), building a webhook handler with referred_by referral attribution, blocking disposable-email or bot signups on a viral waitlist, a custom signup form not submitting or not tracking referrals, or comparing LaunchList vs KickoffLabs/Viral Loops/Prefinery/GetWaitlist on one-time vs subscription pricing. Do NOT use for list-growth strategy (use /sales-audience-growth) or KickoffLabs help (use /sales-kickofflabs).
What this skill does
# LaunchList Platform Help ## Step 1 — Gather context If `references/learnings.md` exists, read it first for accumulated platform knowledge. 1. **What are you trying to do?** - A) Pick a tier — Free (100 submissions) vs Launch $29 one-time (500) vs Grow $79 one-time (10K) vs Scale custom (100K+) - B) Install the waitlist — embed widget vs custom DIY form vs hosted landing page - C) Get signups out of LaunchList — webhooks, Zapier, Slack, or CSV export into an ESP/CRM - D) Set up referral rewards, leaderboard, or position inflation - E) Fight spam — disposable emails, bots, fake referrals - F) Programmatic access — what works given there's no public REST API - G) Compare LaunchList to KickoffLabs / Viral Loops / Prefinery / GetWaitlist / Waitlister 2. **Where will the form live?** Hosted LaunchList page / your own site (which builder?) / custom-coded form — drives widget vs DIY vs landing-page setup. 3. **Where do signups need to end up?** ESP (which?), CRM, spreadsheet, or just the dashboard — drives whether you need Grow ($79) for webhooks/Zapier. Skip-ahead rule: if the user's prompt already contains enough context, skip to Step 2. ## Step 2 — Route or answer directly | If the question is about... | Route to... | |---|---| | General audience/list growth strategy across platforms | `/sales-audience-growth [question]` | | Newsletter monetization | `/sales-newsletter [question]` | | KickoffLabs (waitlists + giveaways with REST API + fraud webhooks) | `/sales-kickofflabs [question]` | | UpViral (B2C sweepstakes/points campaigns) | `/sales-upviral [question]` | | Full-stack multi-level referral/affiliate (L1/2/3, coupon groups) | `/sales-referralhero [question]` | | No-code merge-tag newsletter referrals | `/sales-referralkit [question]` | | SparkLoop paid recommendations + partner network | `/sales-sparkloop [question]` | | ESP setup (Mailchimp, Kit, MailerLite, ActiveCampaign) | `/sales-mailchimp`, `/sales-kit`, `/sales-mailerlite`, `/sales-activecampaign` | If the question is LaunchList-specific, continue to Step 3. ## Step 3 — LaunchList platform reference **Read `references/platform-guide.md`** for the full reference — capabilities tagged by automation surface, pricing and plan gates, integrations, data model, quick-start recipes (custom form, webhook→ESP handler, Zapier), integration patterns, and the comparison grid vs KickoffLabs / UpViral / Viral Loops / Prefinery / GetWaitlist / Waitlister / Referlist / Tuemilio. **Read `references/launchlist-api-reference.md`** for the programmatic surface — there is **no public REST API** (roadmap: planned). What exists: the form POST endpoint (`https://getlaunchlist.com/s/FORM_KEY`), verbatim `new_user` + `email_verify` webhook payloads, Zapier triggers (New Submission / Email Verified), and the spam-protection mechanisms. Answer the user's question using only the relevant section. Don't dump the full reference. ## Step 4 — Actionable guidance Focus on the user's specific situation: - **Webhooks and Zapier are Grow-tier ($79 one-time).** Any signup→ESP/CRM automation forces Grow minimum. Free/Launch users get CSV export only. - **No email broadcast system** — LaunchList only sends welcome/verification emails. Launch announcements come from your ESP; wire signups over via webhook or Zapier, gate on `email_verify` if verification is on. - **No public REST API** — ingress is the form POST endpoint, egress is webhooks/Zapier/CSV. There is no way to read, update, or delete submissions programmatically. - **Custom forms have three hard rules**: email input named exactly `email`, form class `launchlist-form`, and `widget-diy.js` in the page head (otherwise referral attribution breaks silently). - **Webhooks have no documented signing or retries** — use an unguessable URL, check `waitlist_key`, dedupe on `id`, reconcile against CSV exports. - **One-time pricing is per project/tier** — going over your submission cap means buying up a tier, not a monthly overage. If you discover a gotcha, workaround, or tip not covered in `references/learnings.md`, append it there. ## Gotchas > *Best-effort from research (2026-06-06) — review these, especially plan-gated features and pricing that may shift.* 1. **No public REST API.** "API Access" is a *planned* roadmap item. Don't design an integration around endpoints that don't exist — use form POST (ingress) + webhooks (egress). 2. **Webhooks + Zapier gated to Grow ($79 one-time).** The free tier's "export" is manual CSV only. 3. **`referred_by.positon` is a verbatim typo** in the documented webhook payload (top level uses `position`). Parse both spellings. 4. **`is_email_verified` is null-or-timestamp, not boolean.** `null` = unverified; a `"YYYY-MM-DD HH:MM:SS"` string = verified. 5. **`referred_by` is absent for direct signups** — guard before dereferencing in webhook handlers. 6. **Server-to-server POSTs to `/s/FORM_KEY` lose referral attribution** — `widget-diy.js` does the browser-side referral parsing. Only bypass it for testing. 7. **No webhook signing documented** — validate `waitlist_key` and payload shape; don't treat webhook data as authenticated. 8. **Pricing sources disagree** — live page says $29/$79; LaunchList's own blog and third-party comparisons have cited $19/$39/$149/$299 volume steps and a $19 custom-domain add-on. Verify on the pricing page before budgeting. 9. **Email verification starts at Launch ($29)** — Free-tier lists accumulate unverified (typo'd, disposable-beating) addresses; clean before importing to your ESP. 10. **Refund only with zero signups** — the 7-day money-back guarantee is void once you've collected a single signup. ## Related skills - `/sales-audience-growth` — List-growth strategy (lead magnets, referrals, cross-promotion across all platforms) - `/sales-kickofflabs` — KickoffLabs (waitlists + giveaways with REST API v1+v2, fraud webhooks, $13–202/mo) - `/sales-upviral` — UpViral (viral sweepstakes/rewards campaigns, API at Business+, $79–319/mo) - `/sales-referralhero` — ReferralHero (full-stack referral/affiliate with multi-level L1/2/3 + REST API) - `/sales-referralkit` — ReferralKit (no-code merge-tag newsletter referrals, free first 10K leads) - `/sales-sparkloop` — SparkLoop (newsletter referrals + paid recommendations) - `/sales-mailchimp` — Mailchimp platform help (common Zapier destination) - `/sales-kit` — Kit platform help (common Zapier destination) - `/sales-do` — Not sure which skill to use? The router matches any sales objective to the right skill. Install: `npx skills add sales-skills/sales --skill sales-do -a claude-code` ## Examples ### Example 1: Tier choice for a side-project launch **User says**: "I'm collecting signups for a SaaS I'm launching in 3 months. I want referral rewards and the emails need to end up in Kit. Which LaunchList plan?" **Skill does**: Recommends Grow ($79 one-time) because Zapier/webhooks — the only automated path to Kit — unlock there, and 10K submissions covers most pre-launch lists. Notes Launch ($29) works if a manual CSV export into Kit at launch day is acceptable, and that reward/milestone settings start at Launch. Flags that LaunchList can't send the launch announcement itself. **Result**: User picks Grow, sets up the Zapier New Submission → Kit Zap with an `is_spam = 0` filter. ### Example 2: Webhook handler with referral attribution (developer) **User says**: "How do I build a webhook handler that pushes LaunchList signups into HubSpot with referral attribution?" **Skill does**: Walks through Plugins → Create a webhook, then the handler pattern from `references/platform-guide.md` Recipe 2: validate `waitlist_key` (no HMAC signing exists), dedupe on `id`, skip `is_spam == 1`, guard `referred_by` for direct signups, map `referred_by.referral_code` (and the `positon` typo) into HubSpot contact properties, and gate launch emails on the `email_verify` event. **Result**: User has a working Flask handler with idempotency, spam filtering, and
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".