onboarding-cro
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-flow-cro. For ongoing email sequences, see email-sequence.
70
57%
Does it follow best practices?
Impact
92%
1.00xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/onboarding-cro/SKILL.mdQuality
Discovery
44%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description excels at trigger terms and distinctiveness, with comprehensive natural language keywords and explicit boundary-setting with related skills. However, it critically fails at specificity and completeness because it never describes what the skill actually does - only when to use it. The description is essentially all 'when' with zero 'what.'
Suggestions
Add concrete capability statements 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.').
Use third-person action verbs to specify outputs: 'Analyzes drop-off points, recommends aha-moment triggers, creates progressive disclosure patterns.'
Restructure to lead with capabilities, then follow with the existing 'Use when...' trigger guidance.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | 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 'creates', 'analyzes', 'designs', etc. | 1 / 3 |
Completeness | While the 'when' is extensively covered with explicit triggers, the 'what' is completely missing. The description never explains what actions or outputs this skill provides, only when it should be selected. | 1 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including 'onboarding flow,' 'activation rate,' 'aha moment,' 'empty states,' 'users sign up but don't use the product,' and pain-point phrases like 'nobody completes setup' and 'low activation rate.' | 3 / 3 |
Distinctiveness Conflict Risk | The description carves out a clear niche (post-signup onboarding/activation) and explicitly differentiates from related skills by referencing 'signup-flow-cro' for registration and 'email-sequence' for ongoing emails. | 3 / 3 |
Total | 8 / 12 Passed |
Implementation
70%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured strategic skill with clear workflows and good organization, but it leans toward conceptual guidance rather than concrete, actionable deliverables. The content would benefit from specific copy examples, templates, or sample outputs that Claude could directly adapt rather than abstract principles.
Suggestions
Add concrete copy examples for empty states, checklist items, and email triggers (e.g., actual subject lines and body text templates)
Include a sample onboarding audit output showing the exact format with realistic findings, not just the structure
Remove the 'You are an expert...' framing—Claude doesn't need role-play instructions in skill files
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient but includes some unnecessary framing ('You are an expert...') and explanatory text that Claude already knows. Tables and lists are well-structured, but some sections like 'Core Principles' state obvious concepts. | 2 / 3 |
Actionability | Provides good frameworks and checklists but lacks concrete, executable examples. No actual code, copy templates, or specific implementation details—mostly conceptual guidance like 'Clear single next action' without showing what that looks like. | 2 / 3 |
Workflow Clarity | Clear sequencing throughout with explicit steps (Initial Assessment → Define Activation → Design Flow → Measure). Output formats are well-defined, and the funnel analysis section shows a clear validation/measurement approach. | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections, appropriate use of tables for quick reference, and explicit references to related skills and external files (references/experiments.md). Content is appropriately structured for scanning. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- coreyhaines31/marketingskills
- Commit
9d4d29a
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.