Onboarding CRO

Optimize post-signup onboarding by defining activation, mapping flows, removing friction, redesigning steps, and measuring activation rates to boost user ret...

Security Scan

The skill's instructions and requirements match its stated purpose (onboarding/CRO) and it requests no installs, credentials, or system access — it is internally coherent and low-risk.

Purpose & Capability

Name, description, and SKILL.md all focus on redesigning onboarding flows and measuring activation; nothing requested (no env vars, no binaries) is unexpected.

Instruction Scope

Runtime instructions are limited to product-design steps (define activation, map flow, identify friction, redesign, measure). They do not instruct reading system files, accessing credentials, or calling external endpoints.

Install Mechanism

Instruction-only skill with no install spec and no code files — nothing will be downloaded or written to disk by the skill itself.

Credentials

No environment variables, credentials, or config paths are requested — access requested is proportionate to the stated purpose.

Persistence & Privilege

always is false (default) and the skill is user-invocable; it does not request permanent/system-wide presence or elevated privileges.

Assessment

This skill is coherent and low-risk: it only provides design guidance and requests no access to your system or secrets. Before enabling any agent to act on its advice, be mindful that (1) the skill's source is unknown and has no homepage — verify provenance if that matters to you; (2) when the agent asks for product data or analytics to produce concrete recommendations, avoid sharing credentials or sensitive user data (share only non-sensitive examples or anonymized metrics); and (3) review any outputs before applying changes to your product. If you plan to integrate its recommendations into automated workflows that touch production systems or analytics, require explicit human review first.

Onboarding CRO Skill

Trigger

Optimise post-signup onboarding for faster activation.

Trigger phrases: "onboarding flow", "activation rate", "user onboarding", "time to value", "empty state", "onboarding checklist"

Process

1. Define activation: What is the key action that correlates with retention?
2. Map current flow: Steps from signup to activation
3. Identify friction: Where do users drop off post-signup?
4. Redesign: Shortest path to activation event
5. Measure: Activation rate before/after

Key Principles

• Time-to-value is everything. Users decide in the first session.
• One primary action per screen. Don't overwhelm.
• Checklists work: 3-5 items, show progress, celebrate completion
• Empty states should educate and motivate, not just be blank
• Progressive disclosure: show features as users need them
• Personalise: ask 1-2 questions to tailor the experience
• Skip tutorials — let users learn by doing

Onboarding Patterns

Checklist (best for tools with setup)

• Complete profile
• Create first [item]
• Invite a teammate
• Connect integration

Product Tour (best for complex UI)

• Highlight 3-5 key features
• Interactive, not passive
• Skip option always visible

Template/Sample Data (best for content tools)

• Pre-populate with example data
• User edits rather than creates from scratch
• Reduces blank-page anxiety

Output

Redesigned onboarding flow: screen-by-screen breakdown, checklist items, empty state copy, activation metric definition, and success criteria.