onboarding-cro
tessl i github:coreyhaines31/marketingskills --skill onboarding-croWhen 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/registration optimization, see signup-flow-cro. For ongoing email sequences, see email-sequence.
Review Score
66%
Validation Score
13/16
Implementation Score
70%
Activation Score
45%
Generated
Validation
Total
13/16Score
Passed| Criteria | Score |
|---|---|
metadata_version | 'metadata' field is not a dictionary |
license_field | 'license' field is missing |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata |
Implementation
Suggestions 3
Score
70%Overall Assessment
This is a well-structured strategic skill with good workflow clarity and organization, but it operates at a high level of abstraction. The content would benefit from more concrete, actionable examples like specific copy templates, tracking code snippets, or before/after onboarding flow mockups. It reads more like a consulting framework than executable guidance.
Suggestions
- Add concrete copy examples for empty states, checklist items, and onboarding emails (e.g., 'Welcome to [Product]! Your first step: [specific action]')
- Include executable code snippets for common activation tracking implementations (e.g., Segment, Mixpanel event examples)
- Provide a specific before/after example of an onboarding flow audit with actual findings and recommendations
| Dimension | Score | Reasoning |
|---|---|---|
Conciseness | 2/3 | The content is reasonably efficient but includes some explanatory content Claude would already know (e.g., explaining what empty states are, basic definitions). Tables and lists help density, but sections like 'Core Principles' state obvious UX truisms. |
Actionability | 2/3 | Provides frameworks and checklists but lacks concrete, executable examples. No specific copy examples, no code snippets for tracking implementation, and recommendations remain at the strategic level rather than copy-paste ready deliverables. |
Workflow Clarity | 3/3 | Clear sequencing throughout with explicit output formats, funnel analysis structure, and step-by-step audit approach. The 'Output Format' section provides clear deliverable structures, and the task-specific questions guide the discovery process. |
Progressive Disclosure | 3/3 | Well-organized with clear sections, appropriate use of tables for dense information, and proper references to related skills and external files (references/experiments.md). Content is appropriately structured for scanning and navigation. |
Activation
Suggestions 3
Score
45%Overall Assessment
This description excels at trigger terms and distinctiveness, with excellent keyword coverage and clear boundary-setting via cross-references to related skills. However, it critically fails at its core purpose by never describing what the skill actually does - it only explains when to use it, leaving Claude unable to understand the skill's capabilities.
Suggestions
- Add concrete actions at the beginning describing what the skill does, e.g., 'Designs onboarding flows, creates activation checklists, optimizes empty states, and reduces time-to-value for new users.'
- Restructure to lead with capabilities (what) before the trigger conditions (when), following the pattern: '[Actions]. Use when [triggers].'
- Include specific deliverables or outputs the skill produces, such as 'wireframes,' 'copy recommendations,' 'checklist designs,' or 'flow diagrams.'
| Dimension | Score | Reasoning |
|---|---|---|
Specificity | 1/3 | The description lacks concrete actions entirely. It only describes when to use the skill ('When the user wants to optimize...') but never states what the skill actually does - no verbs describing capabilities like 'designs', 'analyzes', 'creates', etc. |
Completeness | 1/3 | The description answers 'when' extensively but completely fails to answer 'what does this do.' There are no capabilities or actions described - only trigger conditions and cross-references to other skills. |
Trigger Term Quality | 3/3 | Excellent coverage of natural trigger terms users would say: 'onboarding flow,' 'activation rate,' 'user activation,' 'first-run experience,' 'empty states,' 'onboarding checklist,' 'aha moment,' 'new user experience,' and 'time-to-value.' |
Distinctiveness Conflict Risk | 3/3 | Very clear niche focused specifically on post-signup onboarding and activation. The explicit cross-references to signup-flow-cro and email-sequence skills actively prevent conflicts by defining boundaries. |