Files
Corey Haines 30f9b9a729 feat: v2.0 skill renames and CRO consolidation (#291)
* feat: v2.0 skill renames and CRO consolidation

BREAKING CHANGE: Users must reinstall skills after this update.

## Skill Renames (16)
- ab-test-setup → ab-testing
- analytics-tracking → analytics
- aso-audit → aso
- competitor-alternatives → competitors
- email-sequence → emails
- free-tool-strategy → free-tools
- launch-strategy → launch
- onboarding-cro → onboarding
- paywall-upgrade-cro → paywalls
- popup-cro → popups
- pricing-strategy → pricing
- product-marketing-context → product-marketing
- referral-program → referrals
- schema-markup → schema
- signup-flow-cro → signup
- social-content → social

## Consolidations (1)
- page-cro + form-cro → cro (form content in references/form.md)

## Why 2.0?
- Shorter, cleaner skill names
- Consistent naming (no -strategy, -setup, -cro suffixes)
- All cross-references updated across 100+ files

Total skills: 40

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* fix(v2.0): update evals for renamed skills, fix validate script, clear warnings

- Update 32 evals.json files to reference new skill names (page-cro → cro,
  product-marketing-context → product-marketing, etc.) — these were missed
  in the initial v2.0 rename pass since only SKILL.md and marketplace.json
  were updated.
- Fix validate-skills.sh: replace GNU-only `head -n -1` with portable awk
  so frontmatter extraction works on macOS.
- Move Copy Editing Checklist (56 lines) to references/checklist.md to
  bring copy-editing SKILL.md under the 500-line limit (508 → 457).
- Add "see X" pointers to marketing-psychology description for skill
  discovery (cro, pricing, copywriting).
- Update skill-request.yml issue template placeholder (page-cro → cro).

All 40 skills now pass validation with zero warnings.

* fix(v2.0): add evals for 8 missing skills, strip stale frontmatter from cro/form.md

Adds 48 new eval cases (6 per skill) for skills that previously had no evals:
aso, co-marketing, community-marketing, competitor-profiling, directory-submissions,
image, lead-magnets, video. All 40 skills now have eval coverage (251 total cases).

Strips leftover frontmatter from skills/cro/references/form.md — it was inherited
from the old form-cro SKILL.md before consolidation. Reference files don't need
frontmatter.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* fix(v2.0): rename paid-ads → ads

One more v2.0 simplification — drops the redundant 'paid-' qualifier. Updates
the skill directory, SKILL.md frontmatter, evals.json, README skill table, the
v2.0 rename table in VERSIONS.md (now 17 renames), and all cross-references in
related skills (ad-creative, aso, competitor-profiling, customer-research,
lead-magnets, marketing-ideas) plus the tools/integrations guides.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* fix(v2.0): bump SKILL.md frontmatter version to 2.0.0 for all 40 skills

VERSIONS.md was already updated to 2.0.0 but the metadata.version field inside
each SKILL.md was still on 1.x. That mismatch would have caused the update-check
flow to perpetually report 'update available' since it compares VERSIONS.md
against local SKILL.md metadata versions.

Caught by codex review (P1).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* fix(v2.0): add legacy product-marketing-context.md filename fallback

Before this fix, users upgrading from v1.x who had a `product-marketing-context.md`
file would lose automatic context loading — every skill only checked the new
`product-marketing.md` filename. Now all 40 skills also accept the legacy
filename (in either `.agents/` or `.claude/`), and the README migration command
covers both legacy and current filenames.

Caught by codex review (P1 + P2).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* fix(v2.0): re-sort README skills table alphabetically, fix ads box width

The skills table had a few entries out of alphabetical order from the renames
(co-marketing was after cold-email, ads was at the renamed position).
Re-sorted alphabetically per sync-skills.js. Also padded the 'ads' cell in the
ASCII flow diagram to keep the box width consistent.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* fix(v2.0): document folder cleanup on upgrade, stop sync-skills from re-adding skills array

README upgrade guide now includes:
- A clear cleanup step for stale v1.x skill folders (renamed + consolidated) so
  users don't end up with both old and new folders side-by-side after upgrading
- The full v1 to v2 rename map for reference
- Existing product-marketing-context.md migration steps (preserved)

sync-skills.js no longer (re-)introduces a `skills` array on marketplace.json --
Claude Code's plugin schema discovers skills via the `skills/` directory, and the
explicit array was failing validation. The script now refreshes the description
count and strips the stale array if present.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
2026-05-13 22:05:15 -07:00

6.4 KiB

name, description, metadata
name description metadata
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 signup/registration optimization, see signup. For ongoing email sequences, see emails.
version
2.0.0

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)

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

  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

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

  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?

  • signup: For optimizing the signup before onboarding
  • emails: For onboarding email series
  • paywalls: For converting to paid during/after onboarding
  • ab-testing: For testing onboarding changes