sales-kickofflabs
KickoffLabs platform help — viral marketing for pre-launch waitlists, bonus-entry giveaways, milestone-reward referral programs, and leaderboard giveaways with REST API v1 + v2, server-side webhooks (`__fraudulent`/`__referral`), AnyForm + KOL.js, and native ESP/Shopify/Zapier integrations. Use when viral campaigns aren't tracking referrers, deciding between Hobby $13/mo (500 leads, no A/B no reward emails) vs Premium $48/mo (A/B + reward emails) vs Business $99/mo vs Enterprise $202/mo, the API key is rejected for being embedded client-side, webhook `__fraudulent` codes (`duplidate_email`/`duplicate_ip`/`bounced`) need a triage workflow, choosing v1 vs v2 endpoints, leaderboard capped at 50, lead-cap auto-upgrade inflating bills, or comparing to Viral Loops/UpViral/Prefinery. Do NOT use for newsletter audience growth (use /sales-audience-growth), merge-tag referrals (use /sales-referralkit), SparkLoop paid recommendations (use /sales-sparkloop), or multi-level Level 1/2/3 referrals (use /sales-referralhero).
What this skill does
# KickoffLabs 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 — Hobby $13/mo (500 leads) vs Premium $48/mo (2.5K) vs Business $99/mo (10K) vs Enterprise $202/mo (25K)
- B) Launch a pre-launch waitlist with viral referrals (Dropbox-style queue jumping)
- C) Set up a bonus-entry giveaway (Gleam-style)
- D) Build a milestone-reward referral program (Morning Brew style)
- E) Set up a leaderboard giveaway with top-N winners
- F) Connect API or webhooks — v1 `/subscribe` vs v2 `/v2/{CAMPAIGN_ID}/...`
- G) Configure AnyForm to post existing site forms to KickoffLabs
- H) Interpret webhook `__fraudulent` reasons (duplicate_ip / bounced / duplidate_email)
- I) Integrate with Klaviyo / Mailchimp / ActiveCampaign / Brevo / Zapier
- J) Compare KickoffLabs to Viral Loops / UpViral / Prefinery / ReferralCandy
2. **What's your campaign type?** Waitlist / giveaway / milestone-reward / leaderboard / opt-in — drives which scoring + reward + verification settings matter.
3. **What's your ESP and website stack?** Drives whether native ESP integration is enough or you need API/webhooks/Zapier glue.
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 newsletter audience growth strategy across all platforms | `/sales-audience-growth [question]` |
| Newsletter monetization | `/sales-newsletter [question]` |
| No-code newsletter-only referrals with merge-tag insertion | `/sales-referralkit [question]` |
| SparkLoop paid recommendations + partner network | `/sales-sparkloop [question]` |
| Full-stack referral/affiliate with multi-level Level 1/2/3 + coupon groups + REST API | `/sales-referralhero [question]` |
| Affiliate program strategy across many tools | `/sales-affiliate-program [question]` |
| ESP setup (Klaviyo, Mailchimp, ActiveCampaign, Brevo) | `/sales-klaviyo`, `/sales-mailchimp`, `/sales-activecampaign`, `/sales-brevo` |
If the question is KickoffLabs-specific, continue to Step 3.
## Step 3 — KickoffLabs platform reference
**Read `references/platform-guide.md`** for the full reference — feature gating per tier, campaign type selection (waitlist / giveaway / milestone / leaderboard / opt-in), AnyForm vs direct-API, fraud detection signals, SMS verification, ESP integrations, and comparisons with Viral Loops / UpViral / Prefinery / ReferralCandy / Voucherify.
**Read `references/kickofflabs-api-reference.md`** for the REST API documentation — v1 (`/subscribe`, `/info`) + v2 (`/v2/{CAMPAIGN_ID}/...` for tags, leads, actions, leaderboard, approve, block, waitlist, verify, SMS, bulk-tags), authentication via `api_key` + `CAMPAIGN_ID`, webhook payload schemas (including `__fraudulent`, `__referral`, `__reward_level`, `__score_change`, `__tagged`), and rate limits by tier.
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:
- **Hobby tier excludes A/B testing, reward level emails, tracking pixels, and custom email templates** — for any campaign that needs milestone rewards (the main referral mechanic), start at Premium ($48/mo annual).
- **API key must be server-side only.** Don't embed in client-side JavaScript — KickoffLabs explicitly warns about this. Use AnyForm + KOL.js for browser-side, then have your backend call the API with the key.
- **v1 vs v2**: v1 (`/subscribe`, `/info`) is form-encoded and still active for simple adds. v2 (`/v2/{CAMPAIGN_ID}/...`) is JSON and covers tags, approve/block, bulk operations, leaderboard, waitlist, SMS verification. Use v2 for new integrations.
- **AnyForm vs direct API**: KickoffLabs' own guidance is "in most cases, use AnyForm for custom pages instead of adding leads directly via the API." AnyForm handles attribution (`?kid=` parsing), referrer cookies, and lead deduplication automatically. Reserve direct API for server-to-server flows your AnyForm can't capture.
- **SMS verification is Premium+ as a $50/mo add-on; Enterprise includes it.** If your fraud risk requires SMS verification, budget Premium + add-on ($98/mo annual) or Enterprise ($202/mo annual).
- **Lead-cap auto-upgrade at $8 per 1,000 overage** — if your campaign spikes (Product Hunt launch, press feature), expect auto-upgrade billing to kick in. Set a campaign-level cap if you want hard ceilings.
- **Fraud-detection flags in webhook**: `duplicate_ip` (same IP signing up multiple times), `bounced` (email bounced on verify), `duplidate_email` (their typo — duplicate email). Treat them as advisory; combine with `approve` / `block` endpoints for manual review.
- **Leaderboard endpoint caps at 50 results** — for larger top-N lists, paginate via leads endpoint and sort client-side.
If you discover a gotcha, workaround, or tip not covered in `references/learnings.md`, append it there.
## Gotchas
> *Best-effort from research — review these, especially items about plan-gated features that may shift.*
1. **API key must be server-side.** "Your API Key should never be used in client side JavaScript." Browser-embedded keys leak to any attacker who reads page source. Use AnyForm + KOL.js for browser-side; reserve the API key for backend.
2. **`duplidate_email` is spelled with a typo in KickoffLabs's own webhook payload docs.** When parsing the `__fraudulent` array, match against the literal string `duplidate_email` as well as `duplicate_email` if KickoffLabs ever fixes it. Don't "correct" the typo client-side.
3. **v1 and v2 endpoints coexist.** v1 `/subscribe` is form-encoded; v2 `/v2/...` is JSON-first. Mixing them in one integration confuses parameter parsing. Pick one path per campaign workflow.
4. **Reward-level emails are Premium+.** Hobby tier ($13/mo) supports the autoresponder but NOT reward-level emails — so milestone-reward programs need Premium minimum.
5. **A/B testing is Premium+.** Hobby cannot A/B test campaign variants. Limits iteration on signup conversion early.
6. **Custom email templates + custom domains require Business+ ($99/mo).** Premium ($48/mo) gives one custom domain but uses default email templates.
7. **SMS Contests are Premium+ add-on at $50/mo extra** (Enterprise includes). Don't promise SMS verification on Hobby.
8. **Lead-cap auto-upgrade at $8 per 1,000 overage** — viral campaigns spike, billing follows. Capterra reviews flag pricing concerns; set a campaign-level cap and configure billing alerts.
9. **Leaderboard endpoint capped at 50 leads.** No pagination on `/leaderboard` itself — pull more via the leads endpoints and rank client-side.
10. **Rate limits scale with plan: ~10/min on Hobby up to ~100/min on Enterprise.** Use bulk endpoints (Bulk Tags, bulk Approve up to 200 emails) for batch operations.
11. **Webhook signing is undocumented in public material.** No HMAC/signature scheme published. Verify caller IP or use a shared-secret query param if signing matters; or contact support to confirm current behavior.
12. **AnyForm is preferred over direct API for custom pages.** KickoffLabs's own docs say so. Direct API is for server-to-server attribution flows AnyForm can't reach.
13. **Capterra reviewers complain about design customization limits** ("section mechanic requires more options") and a learning curve. If pixel-perfect landing pages matter, pair KickoffLabs with a standalone landing-page tool (Unbounce, Leadpages, Framer) and post results via AnyForm.
## Related skills
- `/sales-audience-growth` — Newsletter audience growth strategy (referrals + cross-promotion + lead magnets across all platforms)
- `/sales-newsletter` — Newsletter monetization (paid subs, sponsorships, ad networks)
- `/sales-referralkit` — ReferralKit (no-code merge-tag-driven newsletter referrals, free up to 10K leads)
- `/sales-sparkloopRelated 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".