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," or "new user experience." For signup/registration optimization, see signup-flow-cro. For ongoing email sequences, see email-sequence.
65
Quality
57%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./config/claude/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 but critically fails at describing what the skill actually does. It reads as a 'when to use' clause without the corresponding 'what it does' clause, making it impossible for users or Claude to understand the skill's actual capabilities.
Suggestions
Add a leading sentence describing concrete actions, e.g., 'Designs onboarding flows, creates activation checklists, optimizes empty states, and reduces time-to-value for new users.'
Restructure to follow the pattern: [What it does]. [When to use it]. Currently only the 'when' portion exists.
Include specific deliverables or outputs the skill produces, such as 'wireframes', 'copy recommendations', 'checklist designs', or 'flow diagrams'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description lacks concrete actions entirely. It only describes when to use the skill but never states what the skill actually does - no verbs describing capabilities like 'design', 'analyze', 'create', or 'optimize'. | 1 / 3 |
Completeness | 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. | 1 / 3 |
Trigger Term Quality | 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', 'time-to-value'. | 3 / 3 |
Distinctiveness Conflict Risk | Very clear niche focused specifically on post-signup onboarding and activation. Explicitly distinguishes itself from signup-flow-cro and email-sequence skills, reducing conflict risk. | 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 that provides good frameworks for onboarding optimization. Its strengths are clear organization, logical workflow, and appropriate cross-referencing. However, it could be more concise by removing obvious UX principles and more actionable by including specific implementation examples or tool-specific guidance.
Suggestions
Add concrete, executable examples such as specific analytics queries for measuring activation or code snippets for implementing progress tracking
Remove or condense the 'Core Principles' section - these are standard UX principles Claude already knows
Include specific tool recommendations with implementation details (e.g., specific analytics platforms, A/B testing setup commands)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some explanatory content Claude would already know (e.g., explaining what empty states are, basic definitions). The tables and lists are well-structured but some sections like 'Core Principles' state obvious UX truisms. | 2 / 3 |
Actionability | Provides frameworks and checklists but lacks concrete, executable examples. The funnel analysis shows a template but no actual implementation code or specific tool commands. Recommendations are conceptual rather than copy-paste ready. | 2 / 3 |
Workflow Clarity | Clear sequencing throughout with logical flow from assessment to implementation. The output format section provides explicit structure for deliverables. Multi-step processes like email coordination and re-engagement are well-sequenced with clear triggers. | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections, appropriate use of tables for quick reference, and explicit cross-references to related skills and external references (experiments.md). Content is appropriately scoped for an overview document. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- freekmurze/dotfiles
- Commit
355d067
- 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.