agentsclimarketplace

Onboarding

Skill Infrasity-Labs/dev-gtm-claude-skills/plugins/marketing-skills/skills/onboarding

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 ongoing email sequences, see emails.From its SKILL.md

Install
npx -y skills add Infrasity-Labs/dev-gtm-claude-skills --skill onboarding

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

SKILL.md

7.1 KB, ~1.5k tokens by cl100k_base, as published. Nobody here has run it

Onboarding CRO

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.

Initial Assessment

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:

  1. Product Context - What type of product? B2B or B2C? Core value proposition?
  2. Activation Definition - What's the "aha moment"? What action indicates a user "gets it"?
  3. Current State - What happens after signup? Where do users drop off?

Core Principles

1. Time-to-Value Is Everything

Remove every step between signup and experiencing core value.

2. One Goal Per Session

Focus first session on one successful outcome. Save advanced features for later.

3. Do, Don't Show

Interactive > Tutorial. Doing the thing > Learning about the thing.

4. Progress Creates Motivation

Show advancement. Celebrate completions. Make the path visible.


Defining Activation

Find Your Aha Moment

The action that correlates most strongly with retention:

  • What do retained users do that churned users don't?
  • What's the earliest indicator of future engagement?

Examples by product type:

  • Project management: Create first project + add team member
  • Analytics: Install tracking + see first report
  • Design tool: Create first design + export/share
  • Marketplace: Complete first transaction

Activation Metrics

  • % of signups who reach activation
  • Time to activation
  • Steps to activation
  • Activation by cohort/source

Onboarding Flow Design

Immediate Post-Signup (First 30 Seconds)

ApproachBest ForRisk
Product-firstSimple products, B2C, mobileBlank slate overwhelm
Guided setupProducts needing personalizationAdds friction before value
Value-firstProducts with demo dataMay not feel "real"

Whatever you choose:

  • Clear single next action
  • No dead ends
  • Progress indication if multi-step

Onboarding Checklist Pattern

When to use:

  • Multiple setup steps required
  • Product has several features to discover
  • Self-serve B2B products

Best practices:

  • 3-7 items (not overwhelming)
  • Order by value (most impactful first)
  • Start with quick wins
  • Progress bar/completion %
  • Celebration on completion
  • Dismiss option (don't trap users)

Empty States

Empty states are onboarding opportunities, not dead ends.

Good empty state:

  • Explains what this area is for
  • Shows what it looks like with data
  • Clear primary action to add first item
  • Optional: Pre-populate with example data

Tooltips and Guided Tours

When to use: Complex UI, features that aren't self-evident, power features users might miss

Best practices:

  • Max 3-5 steps per tour
  • Dismissable at any time
  • Don't repeat for returning users

Multi-Channel Onboarding

Email + In-App Coordination

Trigger-based emails:

  • Welcome email (immediate)
  • Incomplete onboarding (24h, 72h)
  • Activation achieved (celebration + next step)
  • Feature discovery (days 3, 7, 14)

Email should:

  • Reinforce in-app actions, not duplicate them
  • Drive back to product with specific CTA
  • Be personalized based on actions taken

Handling Stalled Users

Detection

Define "stalled" criteria (X days inactive, incomplete setup)

Re-engagement Tactics

  1. Email sequence - Reminder of value, address blockers, offer help
  2. In-app recovery - Welcome back, pick up where left off
  3. Human touch - For high-value accounts, personal outreach

Measurement

Key Metrics

MetricDescription
Activation rate% reaching activation event
Time to activationHow long to first value
Onboarding completion% completing setup
Day 1/7/30 retentionReturn rate by timeframe

Funnel Analysis

Track drop-off at each step:

Signup → Step 1 → Step 2 → Activation → Retention
100%      80%       60%       40%         25%

Identify biggest drops and focus there.


Output Format

Onboarding Audit

For each issue: Finding → Impact → Recommendation → Priority

Onboarding Flow Design

  • Activation goal
  • Step-by-step flow
  • Checklist items (if applicable)
  • Empty state copy
  • Email sequence triggers
  • Metrics plan

Common Patterns by Product Type

Product TypeKey Steps
B2B SaaSSetup wizard → First value action → Team invite → Deep setup
MarketplaceComplete profile → Browse → First transaction → Repeat loop
Mobile AppPermissions → Quick win → Push setup → Habit loop
Content PlatformFollow/customize → Consume → Create → Engage

Experiment Ideas

When recommending experiments, consider tests for:

  • Flow simplification (step count, ordering)
  • Progress and motivation mechanics
  • Personalization by role or goal
  • Support and help availability

For comprehensive experiment ideas: See references/experiments.md


Task-Specific Questions

  1. What action most correlates with retention?
  2. What happens immediately after signup?
  3. Where do users currently drop off?
  4. What's your activation rate target?
  5. Do you have cohort analysis on successful vs. churned users?

Tool Integrations

Klaviyo (MCP)

Klaviyo's metric-triggered flows fire based on product events (user completed step X, visited pricing page) — well suited for onboarding email automation. When Klaviyo MCP is connected:

MCP ToolUse For
get_flows + get_flow_reportAudit existing onboarding flow; identify drop-off by step
get_flow_messagePull exact copy of each onboarding email for rewrite
create_email_templateBuild onboarding email templates (welcome, quick win, feature highlight, check-in)
get_eventsRead activation events (first login, feature used, first project created)
query_metric_aggregatesTrack activation event rates to measure onboarding email effectiveness
get_segmentsSegment users by onboarding stage for targeted follow-up

Flow creation gap: Metric-triggered flows are configured in the Klaviyo UI. MCP builds the templates; you wire the triggers manually.

What ships with it: 1 file

7.6 KB alongside SKILL.md

references/

Gives 8 of the 12 instructions most codebase onboarding skills give in ~1.5k tokens

Counted across 307 of the 325 authors here whose files we hold, read 2026-09-06

  • Focus first session on one successful outcomehere, and in 34 of 307, across 15 files
  • Show progress and celebrate completionshere, and in 32 of 307, across 13 files
  • Prefer interactive doing over tutorialshere, and in 32 of 307, across 13 files
  • Remove every step between signup and core valuehere, and in 32 of 307, across 13 files
  • Keep checklists to 3-7 items ordered by valuehere, and in 32 of 307, across 13 files
  • Read product marketing context before asking questionshere, and in 28 of 307, across 13 files
  • Focus fixes on the biggest funnel drop-offshere, and in 22 of 307, across 7 files
  • Define activation as the action most correlated with retentionin 20 of 307, across 6 files
  • Give one clear next action at every stephere, and in 19 of 307, across 8 files
  • Understand product context and current state before recommendingin 15 of 307, across 3 files
  • Limit guided tours to five dismissable stepsin 15 of 307, across 6 files
  • Trace one request from entry to responsein 14 of 307, across 8 files

Said here and by no other author read

  • Drive emails back to product with specific CTAs

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.