[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AE2B9MJC13QFF5ESZT5FTX":3,"skill-same:01M6AE2B9MJC13QFF5ESZT5FTX":80},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":28,"publishedAt":51,"linkOnly":52,"markdownContent":53,"markdownBody":54,"frontMatter":55,"refName":56,"commitSha":57,"skillDirectory":58,"forksCount":59,"repositoryHtmlUrl":60,"repositoryHomepageUrl":61,"ownerHtmlUrl":62,"ownerBlogUrl":63,"ownerDescription":64,"updatedAt":65,"install":66,"resources":79},"01M6AE2B9MJC13QFF5ESZT5FTX","onboarding-cro",null,"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,\" or \"new user experience.\" For signup\u002Fregistration optimization, see signup-flow-cro. For ongoing email sequences, see email-sequence.","davila7\u002Fclaude-code-templates","davila7","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6216945?v=4","01M6ADEWWFPS191NFM0Y1EX1JH","Daniel Avila","01M6ADJHGM78PHQRD3XZTFDVKK",33602,"MIT","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fbusiness-marketing\u002Fonboarding-cro\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000005","邮件与沟通","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000038","人力资源","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50],"onboarding","onboarding cro","cro","new","run","when","value","rate","new user","for","states","post","email sequences","signup","time","registration","checklist","use","user","flow","Optimization","email","2026-11-10 10:12:30",false,"---\nname: onboarding-cro\ndescription: 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,\" or \"new user experience.\" For signup\u002Fregistration optimization, see signup-flow-cro. For ongoing email sequences, see email-sequence.\n---\n\n# Onboarding CRO\n\nYou 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.\n\n## Initial Assessment\n\nBefore providing recommendations, understand:\n\n1. **Product Context**\n   - What type of product? (SaaS tool, marketplace, app, etc.)\n   - B2B or B2C?\n   - What's the core value proposition?\n\n2. **Activation Definition**\n   - What's the \"aha moment\" for your product?\n   - What action indicates a user \"gets it\"?\n   - What's your current activation rate?\n\n3. **Current State**\n   - What happens immediately after signup?\n   - Is there an existing onboarding flow?\n   - Where do users currently drop off?\n\n---\n\n## Core Principles\n\n### 1. Time-to-Value Is Everything\n- How quickly can someone experience the core value?\n- Remove every step between signup and that moment\n- Consider: Can they experience value BEFORE signup?\n\n### 2. One Goal Per Session\n- Don't try to teach everything at once\n- Focus first session on one successful outcome\n- Save advanced features for later\n\n### 3. Do, Don't Show\n- Interactive > Tutorial\n- Doing the thing > Learning about the thing\n- Show UI in context of real tasks\n\n### 4. Progress Creates Motivation\n- Show advancement\n- Celebrate completions\n- Make the path visible\n\n---\n\n## Defining Activation\n\n### Find Your Aha Moment\nThe action that correlates most strongly with retention:\n- What do retained users do that churned users don't?\n- What's the earliest indicator of future engagement?\n- What action demonstrates they \"got it\"?\n\n**Examples by product type:**\n- Project management: Create first project + add team member\n- Analytics: Install tracking + see first report\n- Design tool: Create first design + export\u002Fshare\n- Collaboration: Invite first teammate\n- Marketplace: Complete first transaction\n\n### Activation Metrics\n- % of signups who reach activation\n- Time to activation\n- Steps to activation\n- Activation by cohort\u002Fsource\n\n---\n\n## Onboarding Flow Design\n\n### Immediate Post-Signup (First 30 Seconds)\n\n**Options:**\n1. **Product-first**: Drop directly into product\n   - Best for: Simple products, B2C, mobile apps\n   - Risk: Blank slate overwhelm\n\n2. **Guided setup**: Short wizard to configure\n   - Best for: Products needing personalization\n   - Risk: Adds friction before value\n\n3. **Value-first**: Show outcome immediately\n   - Best for: Products with demo data or samples\n   - Risk: May not feel \"real\"\n\n**Whatever you choose:**\n- Clear single next action\n- No dead ends\n- Progress indication if multi-step\n\n### Onboarding Checklist Pattern\n\n**When to use:**\n- Multiple setup steps required\n- Product has several features to discover\n- Self-serve B2B products\n\n**Best practices:**\n- 3-7 items (not overwhelming)\n- Order by value (most impactful first)\n- Start with quick wins\n- Progress bar\u002Fcompletion %\n- Celebration on completion\n- Dismiss option (don't trap users)\n\n**Checklist item structure:**\n- Clear action verb\n- Benefit hint\n- Estimated time\n- Quick-start capability\n\nExample:\n```\n☐ Connect your first data source (2 min)\n  Get real-time insights from your existing tools\n  [Connect Now]\n```\n\n### Empty States\n\nEmpty states are onboarding opportunities, not dead ends.\n\n**Good empty state:**\n- Explains what this area is for\n- Shows what it looks like with data\n- Clear primary action to add first item\n- Optional: Pre-populate with example data\n\n**Structure:**\n1. Illustration or preview\n2. Brief explanation of value\n3. Primary CTA to add first item\n4. Optional: Secondary action (import, template)\n\n### Tooltips and Guided Tours\n\n**When to use:**\n- Complex UI that benefits from orientation\n- Features that aren't self-evident\n- Power features users might miss\n\n**When to avoid:**\n- Simple, intuitive interfaces\n- Mobile apps (limited screen space)\n- When they interrupt important flows\n\n**Best practices:**\n- Max 3-5 steps per tour\n- Point to actual UI elements\n- Dismissable at any time\n- Don't repeat for returning users\n- Consider user-initiated tours\n\n### Progress Indicators\n\n**Types:**\n- Checklist (discrete tasks)\n- Progress bar (% complete)\n- Level\u002Fstage indicator\n- Profile completeness\n\n**Best practices:**\n- Show early progress (start at 20%, not 0%)\n- Quick early wins (first items easy to complete)\n- Clear benefit of completing\n- Don't block features behind completion\n\n---\n\n## Multi-Channel Onboarding\n\n### Email + In-App Coordination\n\n**Trigger-based emails:**\n- Welcome email (immediate)\n- Incomplete onboarding (24h, 72h)\n- Activation achieved (celebration + next step)\n- Feature discovery (days 3, 7, 14)\n- Stalled user re-engagement\n\n**Email should:**\n- Reinforce in-app actions\n- Not duplicate in-app messaging\n- Drive back to product with specific CTA\n- Be personalized based on actions taken\n\n### Push Notifications (Mobile)\n\n- Permission timing is critical (not immediately)\n- Clear value proposition for enabling\n- Reserve for genuine value moments\n- Re-engagement for stalled users\n\n---\n\n## Engagement Loops\n\n### Building Habits\n- What regular action should users take?\n- What trigger can prompt return?\n- What reward reinforces the behavior?\n\n**Loop structure:**\nTrigger → Action → Variable Reward → Investment\n\n**Examples:**\n- Trigger: Email digest of activity\n- Action: Log in to respond\n- Reward: Social engagement, progress, achievement\n- Investment: Add more data, connections, content\n\n### Milestone Celebrations\n- Acknowledge meaningful achievements\n- Show progress relative to journey\n- Suggest next milestone\n- Shareable moments (social proof generation)\n\n---\n\n## Handling Stalled Users\n\n### Detection\n- Define \"stalled\" criteria (X days inactive, incomplete setup)\n- Monitor at cohort level\n- Track recovery rate\n\n### Re-engagement Tactics\n1. **Email sequence for incomplete onboarding**\n   - Reminder of value proposition\n   - Address common blockers\n   - Offer help\u002Fdemo\u002Fcall\n   - Deadline\u002Furgency if appropriate\n\n2. **In-app recovery**\n   - Welcome back message\n   - Pick up where they left off\n   - Simplified path to activation\n\n3. **Human touch**\n   - For high-value accounts: personal outreach\n   - Offer live walkthrough\n   - Ask what's blocking them\n\n---\n\n## Measurement\n\n### Key Metrics\n- **Activation rate**: % reaching activation event\n- **Time to activation**: How long to first value\n- **Onboarding completion**: % completing setup\n- **Day 1\u002F7\u002F30 retention**: Return rate by timeframe\n- **Feature adoption**: Which features get used\n\n### Funnel Analysis\nTrack drop-off at each step:\n```\nSignup → Step 1 → Step 2 → Activation → Retention\n100%      80%       60%       40%         25%\n```\n\nIdentify biggest drops and focus there.\n\n---\n\n## Output Format\n\n### Onboarding Audit\nFor each issue:\n- **Finding**: What's happening\n- **Impact**: Why it matters\n- **Recommendation**: Specific fix\n- **Priority**: High\u002FMedium\u002FLow\n\n### Onboarding Flow Design\n- **Activation goal**: What they should achieve\n- **Step-by-step flow**: Each screen\u002Fstate\n- **Checklist items**: If applicable\n- **Empty states**: Copy and CTA\n- **Email sequence**: Triggers and content\n- **Metrics plan**: What to measure\n\n### Copy Deliverables\n- Welcome screen copy\n- Checklist items with microcopy\n- Empty state copy\n- Tooltip content\n- Email sequence copy\n- Milestone celebration copy\n\n---\n\n## Common Patterns by Product Type\n\n### B2B SaaS Tool\n1. Short setup wizard (use case selection)\n2. First value-generating action\n3. Team invitation prompt\n4. Checklist for deeper setup\n\n### Marketplace\u002FPlatform\n1. Complete profile\n2. First search\u002Fbrowse\n3. First transaction\n4. Repeat engagement loop\n\n### Mobile App\n1. Permission requests (strategic timing)\n2. Quick win in first session\n3. Push notification setup\n4. Habit loop establishment\n\n### Content\u002FSocial Platform\n1. Follow\u002Fcustomize feed\n2. First content consumption\n3. First content creation\n4. Social connection\u002Fengagement\n\n---\n\n## Experiment Ideas\n\n### Flow Simplification Experiments\n\n**Reduce Friction**\n- Add or remove email verification during onboarding\n- Test empty states vs. pre-populated dummy data\n- Provide pre-filled templates to accelerate setup\n- Add OAuth options for faster account linking\n- Reduce number of required onboarding steps\n\n**Step Sequencing**\n- Test different ordering of onboarding steps\n- Lead with highest-value features first\n- Move friction-heavy steps later in flow\n- Test required vs. optional step balance\n\n**Progress & Motivation**\n- Add progress bars or completion percentages\n- Test onboarding checklists (3-5 items vs. 5-7 items)\n- Gamify milestones with badges or rewards\n- Show \"X% complete\" messaging\n\n---\n\n### Guided Experience Experiments\n\n**Product Tours**\n- Add interactive product tours (Navattic, Storylane)\n- Test tooltip-based guidance vs. modal walkthroughs\n- Video tutorials for complex workflows\n- Self-paced vs. guided tour options\n\n**CTA Optimization**\n- Test CTA text variations during onboarding\n- Test CTA placement within onboarding screens\n- Add in-app tooltips for advanced features\n- Sticky CTAs that persist during onboarding\n\n---\n\n### Personalization Experiments\n\n**User Segmentation**\n- Segment users by role to show relevant features\n- Segment by goal to customize onboarding path\n- Create role-specific dashboards\n- Ask use-case question to personalize flow\n\n**Dynamic Content**\n- Personalized welcome messages\n- Industry-specific examples and templates\n- Dynamic feature recommendations based on answers\n\n---\n\n### Quick Wins & Engagement Experiments\n\n**Time-to-Value**\n- Highlight quick wins early (\"Complete your first X\")\n- Show success messages after key actions\n- Display progress celebrations at milestones\n- Suggest next steps after each completion\n\n**Support & Help**\n- Offer free onboarding calls for complex products\n- Add contextual help throughout onboarding\n- Test chat support availability during onboarding\n- Proactive outreach for stuck users\n\n---\n\n### Email & Multi-Channel Experiments\n\n**Onboarding Emails**\n- Personalized welcome email from founder\n- Behavior-based emails (triggered by actions\u002Finactions)\n- Test email timing and frequency\n- Include quick tips and video content\n\n**Feedback Loops**\n- Add NPS survey during onboarding\n- Ask \"What's blocking you?\" for incomplete users\n- Follow-up based on NPS score\n\n---\n\n## Questions to Ask\n\nIf you need more context:\n1. What action most correlates with retention?\n2. What happens immediately after signup?\n3. Where do users currently drop off?\n4. What's your activation rate target?\n5. Do you have cohort analysis on successful vs. churned users?\n\n---\n\n## Related Skills\n\n- **signup-flow-cro**: For optimizing the signup before onboarding\n- **email-sequence**: For onboarding email series\n- **paywall-upgrade-cro**: For converting to paid during\u002Fafter onboarding\n- **ab-test-setup**: For testing onboarding changes\n","# Onboarding CRO\n\nYou 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.\n\n## Initial Assessment\n\nBefore providing recommendations, understand:\n\n1. **Product Context**\n   - What type of product? (SaaS tool, marketplace, app, etc.)\n   - B2B or B2C?\n   - What's the core value proposition?\n\n2. **Activation Definition**\n   - What's the \"aha moment\" for your product?\n   - What action indicates a user \"gets it\"?\n   - What's your current activation rate?\n\n3. **Current State**\n   - What happens immediately after signup?\n   - Is there an existing onboarding flow?\n   - Where do users currently drop off?\n\n---\n\n## Core Principles\n\n### 1. Time-to-Value Is Everything\n- How quickly can someone experience the core value?\n- Remove every step between signup and that moment\n- Consider: Can they experience value BEFORE signup?\n\n### 2. One Goal Per Session\n- Don't try to teach everything at once\n- Focus first session on one successful outcome\n- Save advanced features for later\n\n### 3. Do, Don't Show\n- Interactive > Tutorial\n- Doing the thing > Learning about the thing\n- Show UI in context of real tasks\n\n### 4. Progress Creates Motivation\n- Show advancement\n- Celebrate completions\n- Make the path visible\n\n---\n\n## Defining Activation\n\n### Find Your Aha Moment\nThe action that correlates most strongly with retention:\n- What do retained users do that churned users don't?\n- What's the earliest indicator of future engagement?\n- What action demonstrates they \"got it\"?\n\n**Examples by product type:**\n- Project management: Create first project + add team member\n- Analytics: Install tracking + see first report\n- Design tool: Create first design + export\u002Fshare\n- Collaboration: Invite first teammate\n- Marketplace: Complete first transaction\n\n### Activation Metrics\n- % of signups who reach activation\n- Time to activation\n- Steps to activation\n- Activation by cohort\u002Fsource\n\n---\n\n## Onboarding Flow Design\n\n### Immediate Post-Signup (First 30 Seconds)\n\n**Options:**\n1. **Product-first**: Drop directly into product\n   - Best for: Simple products, B2C, mobile apps\n   - Risk: Blank slate overwhelm\n\n2. **Guided setup**: Short wizard to configure\n   - Best for: Products needing personalization\n   - Risk: Adds friction before value\n\n3. **Value-first**: Show outcome immediately\n   - Best for: Products with demo data or samples\n   - Risk: May not feel \"real\"\n\n**Whatever you choose:**\n- Clear single next action\n- No dead ends\n- Progress indication if multi-step\n\n### Onboarding Checklist Pattern\n\n**When to use:**\n- Multiple setup steps required\n- Product has several features to discover\n- Self-serve B2B products\n\n**Best practices:**\n- 3-7 items (not overwhelming)\n- Order by value (most impactful first)\n- Start with quick wins\n- Progress bar\u002Fcompletion %\n- Celebration on completion\n- Dismiss option (don't trap users)\n\n**Checklist item structure:**\n- Clear action verb\n- Benefit hint\n- Estimated time\n- Quick-start capability\n\nExample:\n```\n☐ Connect your first data source (2 min)\n  Get real-time insights from your existing tools\n  [Connect Now]\n```\n\n### Empty States\n\nEmpty states are onboarding opportunities, not dead ends.\n\n**Good empty state:**\n- Explains what this area is for\n- Shows what it looks like with data\n- Clear primary action to add first item\n- Optional: Pre-populate with example data\n\n**Structure:**\n1. Illustration or preview\n2. Brief explanation of value\n3. Primary CTA to add first item\n4. Optional: Secondary action (import, template)\n\n### Tooltips and Guided Tours\n\n**When to use:**\n- Complex UI that benefits from orientation\n- Features that aren't self-evident\n- Power features users might miss\n\n**When to avoid:**\n- Simple, intuitive interfaces\n- Mobile apps (limited screen space)\n- When they interrupt important flows\n\n**Best practices:**\n- Max 3-5 steps per tour\n- Point to actual UI elements\n- Dismissable at any time\n- Don't repeat for returning users\n- Consider user-initiated tours\n\n### Progress Indicators\n\n**Types:**\n- Checklist (discrete tasks)\n- Progress bar (% complete)\n- Level\u002Fstage indicator\n- Profile completeness\n\n**Best practices:**\n- Show early progress (start at 20%, not 0%)\n- Quick early wins (first items easy to complete)\n- Clear benefit of completing\n- Don't block features behind completion\n\n---\n\n## Multi-Channel Onboarding\n\n### Email + In-App Coordination\n\n**Trigger-based emails:**\n- Welcome email (immediate)\n- Incomplete onboarding (24h, 72h)\n- Activation achieved (celebration + next step)\n- Feature discovery (days 3, 7, 14)\n- Stalled user re-engagement\n\n**Email should:**\n- Reinforce in-app actions\n- Not duplicate in-app messaging\n- Drive back to product with specific CTA\n- Be personalized based on actions taken\n\n### Push Notifications (Mobile)\n\n- Permission timing is critical (not immediately)\n- Clear value proposition for enabling\n- Reserve for genuine value moments\n- Re-engagement for stalled users\n\n---\n\n## Engagement Loops\n\n### Building Habits\n- What regular action should users take?\n- What trigger can prompt return?\n- What reward reinforces the behavior?\n\n**Loop structure:**\nTrigger → Action → Variable Reward → Investment\n\n**Examples:**\n- Trigger: Email digest of activity\n- Action: Log in to respond\n- Reward: Social engagement, progress, achievement\n- Investment: Add more data, connections, content\n\n### Milestone Celebrations\n- Acknowledge meaningful achievements\n- Show progress relative to journey\n- Suggest next milestone\n- Shareable moments (social proof generation)\n\n---\n\n## Handling Stalled Users\n\n### Detection\n- Define \"stalled\" criteria (X days inactive, incomplete setup)\n- Monitor at cohort level\n- Track recovery rate\n\n### Re-engagement Tactics\n1. **Email sequence for incomplete onboarding**\n   - Reminder of value proposition\n   - Address common blockers\n   - Offer help\u002Fdemo\u002Fcall\n   - Deadline\u002Furgency if appropriate\n\n2. **In-app recovery**\n   - Welcome back message\n   - Pick up where they left off\n   - Simplified path to activation\n\n3. **Human touch**\n   - For high-value accounts: personal outreach\n   - Offer live walkthrough\n   - Ask what's blocking them\n\n---\n\n## Measurement\n\n### Key Metrics\n- **Activation rate**: % reaching activation event\n- **Time to activation**: How long to first value\n- **Onboarding completion**: % completing setup\n- **Day 1\u002F7\u002F30 retention**: Return rate by timeframe\n- **Feature adoption**: Which features get used\n\n### Funnel Analysis\nTrack drop-off at each step:\n```\nSignup → Step 1 → Step 2 → Activation → Retention\n100%      80%       60%       40%         25%\n```\n\nIdentify biggest drops and focus there.\n\n---\n\n## Output Format\n\n### Onboarding Audit\nFor each issue:\n- **Finding**: What's happening\n- **Impact**: Why it matters\n- **Recommendation**: Specific fix\n- **Priority**: High\u002FMedium\u002FLow\n\n### Onboarding Flow Design\n- **Activation goal**: What they should achieve\n- **Step-by-step flow**: Each screen\u002Fstate\n- **Checklist items**: If applicable\n- **Empty states**: Copy and CTA\n- **Email sequence**: Triggers and content\n- **Metrics plan**: What to measure\n\n### Copy Deliverables\n- Welcome screen copy\n- Checklist items with microcopy\n- Empty state copy\n- Tooltip content\n- Email sequence copy\n- Milestone celebration copy\n\n---\n\n## Common Patterns by Product Type\n\n### B2B SaaS Tool\n1. Short setup wizard (use case selection)\n2. First value-generating action\n3. Team invitation prompt\n4. Checklist for deeper setup\n\n### Marketplace\u002FPlatform\n1. Complete profile\n2. First search\u002Fbrowse\n3. First transaction\n4. Repeat engagement loop\n\n### Mobile App\n1. Permission requests (strategic timing)\n2. Quick win in first session\n3. Push notification setup\n4. Habit loop establishment\n\n### Content\u002FSocial Platform\n1. Follow\u002Fcustomize feed\n2. First content consumption\n3. First content creation\n4. Social connection\u002Fengagement\n\n---\n\n## Experiment Ideas\n\n### Flow Simplification Experiments\n\n**Reduce Friction**\n- Add or remove email verification during onboarding\n- Test empty states vs. pre-populated dummy data\n- Provide pre-filled templates to accelerate setup\n- Add OAuth options for faster account linking\n- Reduce number of required onboarding steps\n\n**Step Sequencing**\n- Test different ordering of onboarding steps\n- Lead with highest-value features first\n- Move friction-heavy steps later in flow\n- Test required vs. optional step balance\n\n**Progress & Motivation**\n- Add progress bars or completion percentages\n- Test onboarding checklists (3-5 items vs. 5-7 items)\n- Gamify milestones with badges or rewards\n- Show \"X% complete\" messaging\n\n---\n\n### Guided Experience Experiments\n\n**Product Tours**\n- Add interactive product tours (Navattic, Storylane)\n- Test tooltip-based guidance vs. modal walkthroughs\n- Video tutorials for complex workflows\n- Self-paced vs. guided tour options\n\n**CTA Optimization**\n- Test CTA text variations during onboarding\n- Test CTA placement within onboarding screens\n- Add in-app tooltips for advanced features\n- Sticky CTAs that persist during onboarding\n\n---\n\n### Personalization Experiments\n\n**User Segmentation**\n- Segment users by role to show relevant features\n- Segment by goal to customize onboarding path\n- Create role-specific dashboards\n- Ask use-case question to personalize flow\n\n**Dynamic Content**\n- Personalized welcome messages\n- Industry-specific examples and templates\n- Dynamic feature recommendations based on answers\n\n---\n\n### Quick Wins & Engagement Experiments\n\n**Time-to-Value**\n- Highlight quick wins early (\"Complete your first X\")\n- Show success messages after key actions\n- Display progress celebrations at milestones\n- Suggest next steps after each completion\n\n**Support & Help**\n- Offer free onboarding calls for complex products\n- Add contextual help throughout onboarding\n- Test chat support availability during onboarding\n- Proactive outreach for stuck users\n\n---\n\n### Email & Multi-Channel Experiments\n\n**Onboarding Emails**\n- Personalized welcome email from founder\n- Behavior-based emails (triggered by actions\u002Finactions)\n- Test email timing and frequency\n- Include quick tips and video content\n\n**Feedback Loops**\n- Add NPS survey during onboarding\n- Ask \"What's blocking you?\" for incomplete users\n- Follow-up based on NPS score\n\n---\n\n## Questions to Ask\n\nIf you need more context:\n1. What action most correlates with retention?\n2. What happens immediately after signup?\n3. Where do users currently drop off?\n4. What's your activation rate target?\n5. Do you have cohort analysis on successful vs. churned users?\n\n---\n\n## Related Skills\n\n- **signup-flow-cro**: For optimizing the signup before onboarding\n- **email-sequence**: For onboarding email series\n- **paywall-upgrade-cro**: For converting to paid during\u002Fafter onboarding\n- **ab-test-setup**: For testing onboarding changes\n",{"name":5,"description":7},"main","2b749c82b5d11fac39d9a6e021ce3f5b8a541bd1","cli-tool\u002Fcomponents\u002Fskills\u002Fbusiness-marketing\u002Fonboarding-cro",3963,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates","https:\u002F\u002Faitmpl.com","https:\u002F\u002Fgithub.com\u002Fdavila7","https:\u002F\u002Fdanielavila.me","Building AI dev tools with LLMs","2026-11-15 01:32:48",{"source":8,"skillName":5,"commands":67,"prompt":77,"zipAvailable":78},[68,71,74],{"tool":69,"command":70},"npx","npx skills add davila7\u002Fclaude-code-templates --skill onboarding-cro",{"tool":72,"command":73},"bunx","bunx skills add davila7\u002Fclaude-code-templates --skill onboarding-cro",{"tool":75,"command":76},"pnpm","pnpm dlx skills add davila7\u002Fclaude-code-templates --skill onboarding-cro","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fbusiness-marketing\u002Fonboarding-cro\u002FSKILL.md",true,[],[81,108,135,166,201,225],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":90,"publishedAt":51},"01M70NHBTQ8BV0A2SCAZXEPHCX","wealthville-pool-scoring","Score DeFi liquidity pools before providing liquidity. Returns a 0-100 pool score and an Enter\u002FHold\u002FExit\u002FReduce\u002FAvoid verdict with calibrated confidence for ~68,800 Solana pools and 575 EVM pools, plus a public miss-inclusive track record. Use when asked whether a pool is worth LPing into, which pools look best right now, or how accurate the scores have actually been.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fweb-data\u002Fwealthville-pool-scoring\u002FSKILL.md",[87],{"categoryNo":88,"categoryName":89,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[91,92,93,94,95,38,96,97,46,34,98,99,100,101,102,103,104,105,106,107],"scoring","pool","wealthville pool scoring","liquidity","which","exit","now","reduce","with","record","track","verdict","evm","solana","how","public","look",{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":115,"publishedAt":51},"01M70MB6VR8ERJ4EM8D5KHBMEV","technical-debt-auditor","Scans a codebase and produces a quantified technical debt report with a prioritized remediation plan. Analyzes dead code, TODO\u002FFIXME\u002FHACK markers, dependency staleness, complexity hotspots, code duplication signals, test coverage gaps, unused exports, and outdated patterns. Use this skill when the user asks to audit their codebase for tech debt, wants a health check of their code quality, says things like \"where should I focus refactoring\", \"find code smells\", \"audit my codebase\", \"what technical debt do we have\", \"prioritize cleanup work\", or asks about code quality metrics. Also trigger when the user mentions \"code rot\", \"legacy cleanup\", \"refactoring priorities\", or wants to understand the overall health of a project before a major effort. Trigger even if the user doesn't say \"technical debt\" explicitly — any request to systematically assess code quality and identify improvement priorities belongs here.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Ftechnical-debt-auditor\u002FSKILL.md",[114],{"categoryNo":88,"categoryName":89,"taxonomyType":21,"taxonomyTypeDesc":22},[116,117,118,119,120,121,122,123,124,125,126,34,127,128,129,130,131,132,133,134],"technical debt","debt","technical","technical debt auditor","auditor","coverage","complexity","markers","project","cleanup","unused","code","todo","work","plan","focus","signals","audit","dependency",{"skillNo":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":139,"categories":140,"keywords":148,"publishedAt":51},"01M70KPYH9QNHCNME5GJQGE22K","readonly-sql-guard","Make an agent's database access provably read-only. Use when an agent runs caller-supplied SQL against a production\u002FERP\u002Fanalytics database (a \"query\" MCP tool, text-to-SQL, an admin console), or when reviewing DB-access code for write\u002FDDL\u002Fside-effect\u002Ftransaction-escape risks. Checks what a statement CALLS, not just its shape.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdatabase\u002Freadonly-sql-guard\u002FSKILL.md",[141,144,145],{"categoryNo":142,"categoryName":143,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":88,"categoryName":89,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":146,"categoryName":147,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000033","数据分析师",[149,150,151,152,153,154,155,38,156,157,158,159,160,161,162,46,163,164,34,165],"readonly","guard","sql guard","sql","readonly sql guard","erp","effect","read-only","db","just","tool","calls","only","MCP","access","database","query",{"skillNo":167,"name":168,"nameZh":6,"description":169,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":170,"licenseFileUrl":171,"sourceHtmlUrl":172,"categories":173,"keywords":177,"publishedAt":51},"01M6AFY6F7CC2BBZP1QD6VTNVC","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FSKILL.md",[174],{"categoryNo":175,"categoryName":176,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[178,179,180,181,182,183,184,185,186,187,188,189,190,191,192,193,194,195,196,197,198,199,38,200],"artifacts builder","web","web artifacts builder","artifacts","builder","state","routing","state management","component","css","frontend","ui","Tools","file","components","shadcn","react","Tailwind","suite","jsx","html","single-file","ui components",{"skillNo":202,"name":203,"nameZh":6,"description":204,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":170,"licenseFileUrl":205,"sourceHtmlUrl":206,"categories":207,"keywords":212,"publishedAt":51},"01M6AFWF33SFV9Z3SF4PEEE4BF","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FSKILL.md",[208,211],{"categoryNo":209,"categoryName":210,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":175,"categoryName":176,"taxonomyType":21,"taxonomyTypeDesc":22},[213,214,215,216,217,179,218,188,189,219,220,221,222,38,223,99,224],"webapp testing","testing","webapp","browser","playwright","applications","debugging","toolkit","logs","screenshots","local","behavior",{"skillNo":226,"name":227,"nameZh":6,"description":228,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":170,"licenseFileUrl":229,"sourceHtmlUrl":230,"categories":231,"keywords":239,"publishedAt":51},"01M6AF67Q67JJJ5V51JR2P52KA","discernment-nudge","After you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdiscernment-nudge\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdiscernment-nudge\u002FSKILL.md",[232,235,236],{"categoryNo":233,"categoryName":234,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":88,"categoryName":89,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":237,"categoryName":238,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000036","内容创作者",[240,241,242,243,33,244,245,246,181,247,191,127,248,249,250,251,252,161,253,34,254,255,256,257,258,105,259],"discernment nudge","nudge","interpretation","help","reasoning","data","writing","lookup","content","review","conversation","short","up","invoke","you","analysis","claims","argument","assemble","recommendations"]