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.
67
51%
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 extensive natural-language keywords and explicit boundary-drawing with related skills. However, it critically fails to describe what the skill actually does — there are no concrete actions, outputs, or capabilities listed. It reads as a pure 'when to use' clause with no 'what it does' clause.
Suggestions
Add a leading sentence describing concrete actions, e.g., 'Designs onboarding flows, optimizes activation funnels, creates onboarding checklists, and improves empty states to reduce time-to-value for new users.'
Restructure to lead with capabilities (what) before the 'Use when...' clause (when), following the pattern: actions first, then trigger guidance.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description lacks concrete actions entirely. It never states what the skill actually does — no verbs like 'designs,' 'analyzes,' 'creates,' or 'optimizes.' It only describes when to use it, not what it does. | 1 / 3 |
Completeness | The 'when' is thoroughly covered with explicit triggers, but the 'what does this do' is entirely missing. The description never explains what actions or outputs the skill provides, only when to invoke it. Per the rubric, this is 'Missing what OR when.' | 1 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say, including 'onboarding flow,' 'activation rate,' 'aha moment,' 'users sign up but don't use the product,' 'nobody completes setup,' 'low activation rate,' and many more natural variations. | 3 / 3 |
Distinctiveness Conflict Risk | The description carves out a clear niche around post-signup onboarding and activation, and explicitly differentiates from related skills (signup-flow-cro for registration, email-sequence for ongoing emails), making conflicts unlikely. | 3 / 3 |
Total | 8 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a competent instructional skill that provides good structural frameworks for onboarding CRO work, with clear organization and appropriate cross-references. Its main weaknesses are a lack of concrete, executable examples (e.g., actual empty state copy, specific checklist wording, email templates) and some verbosity in explaining concepts Claude already understands. The skill would benefit from replacing advisory statements with specific, actionable templates.
Suggestions
Add concrete copy examples for key deliverables—e.g., a sample empty state message, a sample onboarding checklist with real wording, or a sample welcome email template—to move from advisory to actionable.
Remove or compress sections that explain concepts Claude already knows (e.g., what empty states are, what tooltips are, basic UX principles like 'progress creates motivation') and replace with specific implementation patterns.
Add a validation checkpoint in the workflow—e.g., after defining the activation event, verify it against retention data before designing the flow—to create a feedback loop for this consultative process.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably well-structured but includes some unnecessary framing (e.g., 'You are an expert in user onboarding and activation') and explanations of concepts Claude already knows (e.g., what empty states are, what tooltips are). Several sections could be tightened—the core principles section states obvious UX truisms. | 2 / 3 |
Actionability | The skill provides structured frameworks (tables, checklists, output formats) but remains largely advisory rather than executable. There are no concrete code snippets, copy examples, or fill-in templates. Guidance like 'Clear single next action' and 'No dead ends' is directional but not specific enough to be copy-paste actionable. | 2 / 3 |
Workflow Clarity | The initial assessment section provides a clear sequence (check context file → gather info → recommend), and the output format section defines deliverable structure. However, there's no explicit validation or feedback loop—no step to verify recommendations against data, no checkpoint to confirm activation definition before proceeding to flow design. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, appropriate use of tables, and a reference to external file (references/experiments.md) that is clearly signaled and one level deep. Related skills are listed at the bottom for navigation. The skill stays at overview level and delegates appropriately. | 3 / 3 |
Total | 9 / 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
2c7c108
- 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.