skills/onboarding/SKILL.md
When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value. Also use when the user mentions "onboarding flow," "activation rate," "user activation," "first-run experience," "empty states," "onboarding checklist," "aha moment," "new user experience," "users aren't activating," "nobody completes setup," "low activation rate," "users sign up but don't use the product," "time to value," or "first session experience." Use this whenever users are signing up but not sticking around. For signup/registration optimization, see signup. For ongoing email sequences, see emails.
npx skillsauth add coreyhaines31/marketingskills onboardingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
You are an expert in user onboarding and activation. Your goal is to help users reach their "aha moment" as quickly as possible and establish habits that lead to long-term retention.
Check for product marketing context first:
If .agents/product-marketing.md exists (or .claude/product-marketing.md, or the legacy product-marketing-context.md filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
Before providing recommendations, understand:
Remove every step between signup and experiencing core value. Design the Minimum Path to Value (MPTV) — the least number of steps to experience enough value to make a confident decision (see references/minimum-path-to-value.md).
Focus first session on one successful outcome. Save advanced features for later.
Interactive > Tutorial. Doing the thing > Learning about the thing.
Show advancement. Celebrate completions. Make the path visible. (See onboarding psychology below for the mechanisms.)
The principles that make progress mechanics, checklists, and prompts actually work:
The components you assemble an onboarding experience from. Use the fewest that reach value:
| Component | Purpose | |-----------|---------| | Welcome forms | Capture role/goal to personalize the path (keep short — Hick's Law) | | Initial screens | First-run screens that orient and point to one clear action | | Drip emails | Multi-touch nurture — one concept per email, don't overload | | Skippable tutorials | Optional guidance users can bypass — never trap them | | Videos | Show complex workflows visually | | Docs / help center | Self-serve reference for when users get stuck | | Onboarding calls | Human touch for complex or high-value accounts | | Data inputs | Getting the user's real data in so value feels "real" | | Checklists | Ordered, value-first steps with visible progress (see below) | | Empty states | Guided first-action opportunities, not dead ends (see below) |
Judge activation by lead→customer conversion + 90-day retention, not lead volume. More signups mean nothing if they don't convert and stick.
Choose an activation model (freemium, free trial, paid trial, money-back, consultation) before designing the flow — the model shapes the whole onboarding path. See references/activation-models.md for the 5 models, the credit-card tradeoff, Model-Market Fit, and the Evernote-vs-Notion parable.
The action that correlates most strongly with retention:
Examples by product type:
| Approach | Best For | Risk | |----------|----------|------| | Product-first | Simple products, B2C, mobile | Blank slate overwhelm | | Guided setup | Products needing personalization | Adds friction before value | | Value-first | Products with demo data | May not feel "real" |
Whatever you choose:
When to use:
Best practices:
Empty states are onboarding opportunities, not dead ends.
Good empty state:
When to use: Complex UI, features that aren't self-evident, power features users might miss
Best practices:
Trigger-based emails:
Email should:
Define "stalled" criteria (X days inactive, incomplete setup)
| Metric | Description | |--------|-------------| | Activation rate | % reaching activation event | | Time to activation | How long to first value | | Onboarding completion | % completing setup | | Day 1/7/30 retention | Return rate by timeframe |
Track drop-off at each step:
Signup → Step 1 → Step 2 → Activation → Retention
100% 80% 60% 40% 25%
Identify biggest drops and focus there.
For each issue: Finding → Impact → Recommendation → Priority
| Product Type | Key Steps | |--------------|-----------| | B2B SaaS | Setup wizard → First value action → Team invite → Deep setup | | Marketplace | Complete profile → Browse → First transaction → Repeat loop | | Mobile App | Permissions → Quick win → Push setup → Habit loop | | Content Platform | Follow/customize → Consume → Create → Engage |
When recommending experiments, consider tests for:
For comprehensive experiment ideas: See references/experiments.md
development
When the user wants to plan, run, sponsor, speak at, or get pipeline from events — webinars, conferences, trade shows, meetups, dinners, workshops, virtual summits, or user conferences. Also use when the user mentions 'event marketing,' 'field marketing,' 'run a webinar,' 'webinar funnel,' 'show-up rate,' 'should we sponsor,' 'sponsor a conference,' 'trade show booth,' 'booth strategy,' 'event ROI,' 'badge scans,' 'event follow-up,' 'speaking slot,' 'CFP,' 'conference talk,' 'host a dinner,' 'user conference,' or 'virtual summit.' Covers all four roles: hosting, sponsoring/exhibiting, speaking, and attending. For product launch moments, see launch. For the partnership side of joint webinars, see co-marketing. For ongoing community programs, see community-marketing. For podcast appearances, see public-relations. For the email sequences themselves, see emails.
development
When the user wants to design, construct, or improve an offer — the thing they actually sell — including value framing, bonus stacking, guarantee design, scarcity/urgency, naming, and payment structure. Also use when the user mentions 'offer,' 'offer design,' 'build an offer,' 'grand slam offer,' 'irresistible offer,' 'value stack,' 'bonus stack,' 'guarantee,' 'risk reversal,' 'money-back guarantee,' 'scarcity,' 'urgency,' 'high-ticket offer,' 'productize a service,' 'naming an offer,' 'payment plan,' 'down-sell,' 'upsell offer,' or 'why isn't my offer converting.' Best for services, agencies, courses, coaching, info products, high-ticket B2B, and direct-response. If you run pure self-serve SaaS, read pricing first — tiers and packaging do more work there. For price level itself (tiers, freemium, value metric), see pricing. For the page that presents the offer, see copywriting. For the launch moment, see launch. For sales collateral, see sales-enablement.
development
When the user wants help with public relations, earned media, press coverage, journalist outreach, or media strategy (not pull requests). Also use when the user mentions 'PR,' 'public relations,' 'press,' 'press release,' 'press coverage,' 'media outreach,' 'pitch a journalist,' 'get featured,' 'media list,' 'media kit,' 'press kit,' 'newsjacking,' 'news hijack,' 'HARO,' 'Qwoted,' 'Featured,' 'Help A Reporter,' 'reporter request,' 'tech press,' 'TechCrunch,' 'earned media,' 'thought leadership placement,' 'op-ed,' 'guest article,' 'press contacts,' 'podcast prep,' 'going on a podcast,' 'podcast guest,' 'prep me for this podcast,' or 'how do I get press.' Use this for earned media work — finding journalists, pitching stories, newsjacking, prepping podcast appearances, and responding to press requests. For startup/SaaS/AI directory submissions, see directory-submissions. For product launches, see launch. For social-media engagement, see social. For cold-email outreach to prospects, see cold-email.
tools
When the user needs a comprehensive marketing plan for a client, a company they advise, or their own product. Also use when the user mentions "marketing plan," "growth plan," "GTM plan," "go-to-market plan," "AARRR plan," "90-day marketing plan," "12-month marketing roadmap," "fractional CMO plan," or "fCMO plan." Generates an exhaustive 13-section plan structured by AARRR (Acquisition, Activation, Retention, Referral, Revenue), customized to the client's current budget, team, and stage, mapped to future funding milestones, cross-referenced with the 139-idea marketing-ideas library and an embedded 17-section current-state audit rubric, with a full marketing operations stack showing which skills and MCP/API integrations execute each part. Outputs a Notion-paste-ready markdown document. For positioning and ICP context before planning, see product-marketing. For stage-specific deep work, see onboarding, signup, emails, referrals, pricing.