Onboarding Cro
Onboarding Cro is an code AI skill with a core value of When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value. It
helps developers solve real-world problems in the code domain, boosting
efficiency, automating repetitive tasks, and optimizing workflows.
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,\" \"u...
Quick Facts
mkdir -p ./skills/onboarding-cro && curl -sfL https://raw.githubusercontent.com/sickn33/antigravity-awesome-skills/main/skills/onboarding-cro/SKILL.md -o ./skills/onboarding-cro/SKILL.md Run in terminal / PowerShell. Requires curl (Unix) or PowerShell 5+ (Windows).
Skill Content
# 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
Before providing recommendations, understand:
1. **Product Context**
- What type of product? (SaaS tool, marketplace, app, etc.)
- B2B or B2C?
- What's the core value proposition?
2. **Activation Definition**
- What's the "aha moment" for your product?
- What action indicates a user "gets it"?
- What's your current activation rate?
3. **Current State**
- What happens immediately after signup?
- Is there an existing onboarding flow?
- Where do users currently drop off?
---
Core Principles
1. Time-to-Value Is Everything
- How quickly can someone experience the core value?
- Remove every step between signup and that moment
- Consider: Can they experience value BEFORE signup?
2. One Goal Per Session
- Don't try to teach everything at once
- 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
- Show UI in context of real tasks
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?
- What action demonstrates they "got it"?
**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
- Collaboration: Invite first teammate
- 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)
**Options:**
1. **Product-first**: Drop directly into product
- Best for: Simple products, B2C, mobile apps
- Risk: Blank slate overwhelm
2. **Guided setup**: Short wizard to configure
- Best for: Products needing personalization
- Risk: Adds friction before value
3. **Value-first**: Show outcome immediately
- Best for: Products with demo data or samples
- Risk: 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)
**Checklist item structure:**
- Clear action verb
- Benefit hint
- Estimated time
- Quick-start capability
Example:
☐ Connect your first data source (2 min)
Get real-time insights from your existing tools
[Connect Now]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
**Structure:**
1. Illustration or preview
2. Brief explanation of value
3. Primary CTA to add first item
4. Optional: Secondary action (import, template)
Tooltips and Guided Tours
**When to use:**
- Complex UI that benefits from orientation
- Features that aren't self-evident
- Power features users might miss
**When to avoid:**
- Simple, intuitive interfaces
- Mobile apps (limited screen space)
- When they interrupt important flows
**Best practices:**
- Max 3-5 steps per tour
- Point to actual UI elements
- Dismissable at any time
- Don't repeat for ret
🎯 Best For
- Claude users
- Software engineers
- Development teams
- Tech leads
💡 Use Cases
- Code quality improvement
- Best practice enforcement
📖 How to Use This Skill
- 1
Install the Skill
Copy the install command from the Terminal tab and run it. The SKILL.md file downloads to your local skills directory.
- 2
Load into Your AI Assistant
Open Claude and reference the skill. Paste the SKILL.md content or use the system prompt tab.
- 3
Apply Onboarding Cro to Your Work
Open your project in the AI assistant and ask it to apply the skill. Start with a small module to verify the output quality.
- 4
Review and Refine
Review AI suggestions before committing. Run tests, check for regressions, and iterate on the skill output.
❓ Frequently Asked Questions
Is Onboarding Cro compatible with Cursor and VS Code?
Yes — this skill works with any AI coding assistant including Cursor, VS Code with Copilot, and JetBrains IDEs.
Do I need specific dependencies for Onboarding Cro?
Check the install command and Works With section. Most code skills only require the AI assistant and your codebase.
How do I install Onboarding Cro?
Copy the install command from the Terminal tab and run it. The skill downloads to ./skills/onboarding-cro/SKILL.md, ready to use.
Can I customize this skill for my team?
Absolutely. Edit the SKILL.md file to add team-specific instructions, examples, or workflows.
⚠️ Common Mistakes to Avoid
Skipping validation
Always test AI-generated code changes, even for simple refactors.
Missing dependency updates
Check if the skill requires updated dependencies or new packages.