onboarding-cro

Overview of onboarding-cro skill

What onboarding-cro is for

onboarding-cro is a Conversion-focused skill for improving what happens after signup: first-run experience, activation, time-to-value, empty states, onboarding checklists, and the path to a user’s “aha moment.” It helps an AI agent diagnose where new users stall, then propose onboarding changes that make the first successful outcome faster and clearer.

Use the onboarding-cro skill when the problem is not “get more signups,” but “turn new signups into activated users.”

Best-fit users and teams

This skill is most useful for SaaS founders, growth marketers, product managers, UX writers, and lifecycle teams working on activation metrics. It fits B2B and B2C products where you can describe the user’s first session, activation event, and current drop-off points.

It is especially valuable when you already have some onboarding evidence: analytics funnel steps, session notes, user interviews, support tickets, product screenshots, or a known activation definition.

Key differentiators

The skill is built around practical onboarding CRO principles: reduce time-to-value, focus the first session on one goal, prefer interactive “do” moments over passive tutorials, and avoid overwhelming new users with advanced features too early.

It also includes scripts/activation_funnel_analyzer.py, a helper script for identifying the worst drop-off in an onboarding funnel and estimating where improvements may matter most.

When to choose a different skill

Use a signup or registration optimization skill if users are abandoning before account creation. Use an email sequence skill if the main work is ongoing nurture after the product experience. onboarding-cro is strongest when the product experience itself needs to activate users faster.

How to Use onboarding-cro skill

onboarding-cro install and repository files

Install the skill with:

npx skills add alirezarezvani/claude-skills --skill onboarding-cro

Then inspect the source at:

marketing-skill/skills/onboarding-cro/

Read SKILL.md first because it contains the decision framework and onboarding principles. Then review scripts/activation_funnel_analyzer.py if you have step-by-step funnel counts. There are no large reference folders to study, so the fastest path is to understand the skill instructions, then run or adapt the analyzer for your own activation funnel.

Inputs that make onboarding-cro usage better

The skill performs best when you provide concrete product and funnel context instead of asking for generic onboarding ideas. Include:

• Product type, audience, and value proposition
• The activation event or “aha moment”
• Current first-run flow after signup
• Funnel steps with user counts or conversion rates
• Known friction from support, recordings, analytics, or interviews
• Constraints such as engineering capacity, compliance, sales-assist needs, or mobile/web platform

A weak prompt is: “Improve our onboarding.”

A stronger prompt is: “Use onboarding-cro for a B2B analytics SaaS. New users sign up, verify email, connect a data source, invite a teammate, then view their first dashboard. Activation is viewing a dashboard with live data within 24 hours. Current funnel: signup 4,000; email verified 3,400; data source connected 1,600; dashboard viewed 900; invited teammate 300. Recommend the top activation bottlenecks, quick experiments, and revised first-session flow.”

Using the activation funnel analyzer

If you have funnel data, create a JSON file with this shape:

{
  "steps": [
    {"name": "Signup completed", "users": 1000},
    {"name": "Email verified", "users": 850},
    {"name": "Profile setup", "users": 620},
    {"name": "First action", "users": 310},
    {"name": "Aha moment", "users": 180}
  ]
}

Run:

python3 scripts/activation_funnel_analyzer.py funnel.json

Use the output to guide your prompt. Ask the agent to explain why the worst drop-off may be happening, what evidence would confirm it, and which experiment should run first. The script does not replace product judgment; it gives the agent a sharper starting point than raw percentages.

Suggested workflow for practical results

Start with diagnosis, not redesign. Ask the skill to identify the activation goal, unnecessary steps before value, unclear user decisions, and moments where the product explains instead of helping the user do.

Then request a prioritized plan: immediate copy or UI fixes, product-flow changes, instrumentation gaps, and experiments. For each recommendation, ask for the expected effect on activation, implementation effort, risk, and the metric to watch.

Best outputs usually come from one focused target, such as “reduce drop-off between workspace creation and first project” rather than a broad request to improve the whole onboarding journey.

onboarding-cro skill FAQ

Is onboarding-cro only for SaaS products?

No. It can help any product with a post-signup activation journey, including marketplaces, consumer apps, developer tools, communities, and AI products. However, it works best when there is a clear first value moment and measurable onboarding path. If activation is vague, define it before asking for design recommendations.

How is this different from an ordinary prompt?

A normal prompt may produce a generic onboarding checklist. The onboarding-cro skill pushes the agent toward activation-specific thinking: time-to-value, one goal per session, interactive progress, drop-off diagnosis, and habit-forming next steps. It also encourages the agent to ask for product context before making recommendations.

Do beginners need analytics to use it?

Analytics help, but they are not mandatory. Beginners can still use the skill with a written description of the current flow, screenshots, or qualitative complaints. If you do not have funnel data, ask the skill to produce an instrumentation plan before proposing major redesigns.

When should I not use onboarding-cro?

Do not use it as the primary tool for pricing-page CRO, ad landing pages, checkout optimization, or long-term lifecycle email strategy. It can mention those areas if they affect activation, but its main job is improving the in-product journey from new account to meaningful value.

How to Improve onboarding-cro skill

Give onboarding-cro a sharper activation definition

The most important input is the activation event. “User becomes active” is too vague. Better definitions include “imports first file,” “publishes first project,” “connects Stripe,” “creates first report,” or “gets first qualified lead.”

If you are unsure, provide candidate activation events and ask the skill to choose the strongest one based on proximity to retained value, measurability, and user intent.

Avoid common failure modes

Common weak outputs come from missing constraints. If the agent recommends a complete rebuild when you only have one engineer, the prompt likely lacked implementation limits. If it suggests more education instead of reducing friction, ask it to reframe around “do, don’t show.” If it optimizes every step equally, ask it to prioritize by drop-off size, expected lift, and distance from the aha moment.

Iterate after the first recommendation

After the first output, ask for a second pass using your reality checks:

• “Which ideas are fastest to test without backend changes?”
• “Which recommendation is most likely to improve activation this week?”
• “What event tracking is missing before we can trust this funnel?”
• “Rewrite the onboarding checklist so it drives one first-session outcome.”
• “Turn the top idea into an A/B test with success metric, segment, and risk.”

This makes onboarding-cro usage more decision-oriented and less like a generic UX brainstorm.

Add product evidence over time

To improve future results, save a compact onboarding brief: ICP, activation definition, current funnel, top objections, screenshots, and recent experiment outcomes. If your Claude setup supports shared context, place durable product marketing context in .claude/product-marketing-context.md so the skill can reuse it and ask fewer repetitive questions.