About
This skill provides onboarding and activation strategies to guide new users to their first value moment, focusing on first-run sequencing, setup checklists, and retention-linked measurement. Use it when users sign up but fail to activate or when you need to redesign the initial user flow. It specifically excludes registration optimization, email sequences, and monetization prompts, which are handled by other skills.
Quick Install
Claude Code
Recommendednpx skills add JasonColapietro/suede-creator-skills -a claude-code/plugin add https://github.com/JasonColapietro/suede-creator-skillsgit clone https://github.com/JasonColapietro/suede-creator-skills.git ~/.claude/skills/suede-onboardingCopy and paste this command in Claude Code to install this skill
Documentation
Suede Onboarding and Activation
Suede designs onboarding around verified first value and retention-linked activation, not decorative checklists or forced engagement. Define the activation evidence, remove unnecessary friction, sequence the first session, and instrument the path before claiming an "aha moment."
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:
- Product Context - What type of product? B2B or B2C? Core value proposition?
- Activation Definition - What's the "aha moment"? What action indicates a user "gets it"?
- 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)
| 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:
- 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
- Email sequence - Reminder of value, address blockers, offer help
- In-app recovery - Welcome back, pick up where left off
- Human touch - For high-value accounts, personal outreach
Measurement
Key Metrics
| 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 |
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 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 |
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
- What action most correlates with retention?
- What happens immediately after signup?
- Where do users currently drop off?
- What's your activation rate target?
- Do you have cohort analysis on successful vs. churned users?
Boundaries
- Do not invent an activation event, retention correlation, cohort result, or benchmark when product data is unavailable.
- Do not change product flows, permissions, notifications, experiments, or analytics without explicit authorization.
- Do not add friction, forced invitations, premature paywalls, or manipulative progress mechanics merely to improve a local metric.
- Do not decide sensitive-data collection, consent, accessibility, or product-risk policy for the user.
Routing
- Use
suede-signupfor registration before first-run onboarding. - Use
suede-emailsfor onboarding email sequences andsuede-paywallsfor upgrade moments. - Use
suede-ab-testingto validate onboarding changes andsuede-analyticsto measure activation.
GitHub Repository
Frequently asked questions
What is the suede-onboarding skill?
suede-onboarding is a Claude Skill by JasonColapietro. Skills package instructions and resources that Claude loads on demand, so Claude can perform suede-onboarding-related tasks without extra prompting.
How do I install suede-onboarding?
Use the install commands on this page: add suede-onboarding to Claude Code as a plugin, or clone its repository into your skills directory, then restart Claude so it picks up the skill.
What category does suede-onboarding belong to?
suede-onboarding is in the Communication category, tagged ai.
Is suede-onboarding free to use?
Yes. suede-onboarding is listed on AIMCP and free to install.
Related Skills
This Claude Skill enables email management through the Himalaya CLI tool using IMAP. It allows developers to search, summarize, and delete emails from an IMAP account with natural language queries. Use it for automated email workflows like getting daily summaries or performing batch operations directly from Claude.
imsg is a CLI tool for macOS that lets you programmatically interact with iMessage/SMS via the Messages.app. It enables developers to list chats, view message history, watch conversations in real-time, and send messages or attachments. Use this skill to automate messaging tasks or integrate iMessage/SMS functionality into your development workflows.
This Claude Skill provides comprehensive guidance for implementing internationalization (i18n) and localization in applications. It covers key tasks like message extraction, translation management, locale-specific formatting, and RTL support using libraries like i18next and gettext. Use it when building multi-language applications or adding localization features for international users.
wacli is a command-line tool that enables WhatsApp messaging, search, and synchronization via the WhatsApp Web protocol. It's primarily used within Clawdis workflows for automated handling but can be called directly to send messages, sync chats, or query history. Key features include QR-based authentication, continuous background syncing, and the ability to send both text and files.
