signup-flow-cro
When the user wants to optimize signup, registration, account creation, or trial activation flows. Also use when the user mentions "signup conversions," "registration friction," "signup form optimization," "free trial signup," "reduce signup dropoff," or "account creation flow." For post-signup onboarding, see onboarding-cro. For lead capture forms (not account creation), see form-cro.
81
Quality
77%
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/signup-flow-cro/SKILL.mdQuality
Discovery
89%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 term coverage and completeness, with explicit guidance on when to use it and clear disambiguation from related skills. The main weakness is the lack of specific concrete actions - it describes the domain well but doesn't enumerate what optimization activities the skill actually performs.
Suggestions
Add specific concrete actions the skill performs, such as 'analyze signup form fields', 'identify friction points', 'recommend form simplification', or 'optimize CTA placement'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (signup/registration flows) and mentions optimization, but lacks specific concrete actions like 'analyze form fields', 'reduce form steps', or 'A/B test CTAs'. It tells us what area it covers but not what specific actions it performs. | 2 / 3 |
Completeness | Clearly answers both what (optimize signup/registration/account creation flows) and when (explicit 'Use when' equivalent with trigger phrases). Also includes helpful disambiguation pointing to related skills (onboarding-cro, form-cro), which aids skill selection. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'signup', 'registration', 'account creation', 'trial activation', 'signup conversions', 'registration friction', 'signup form optimization', 'free trial signup', 'reduce signup dropoff', 'account creation flow'. These are realistic phrases users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Explicitly distinguishes itself from related skills (onboarding-cro for post-signup, form-cro for lead capture). The specific focus on account creation vs. other form types creates a clear niche with minimal conflict risk. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a comprehensive and highly actionable CRO skill with excellent specific guidance for signup flow optimization. The main weaknesses are verbosity (some sections explain concepts Claude knows) and the monolithic structure that could benefit from splitting detailed reference material into separate files. The workflow could also benefit from explicit validation steps.
Suggestions
Move the detailed 'Experiment Ideas' section to a separate EXPERIMENTS.md file and reference it from the main skill
Add a validation checkpoint in the workflow, such as 'Before finalizing recommendations, verify against current analytics data' or 'Confirm business constraints before suggesting field removal'
Trim explanations of basic UX principles (touch targets, keyboard types) that Claude already understands
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is comprehensive but includes some explanations Claude would already know (e.g., basic UX principles like 'larger touch targets', 'single column layout'). Some sections could be tightened, though most content adds value. | 2 / 3 |
Actionability | Provides highly specific, actionable guidance throughout: concrete field recommendations, specific patterns (B2B SaaS Trial flow), exact metrics to track, and detailed experiment ideas. The audit output format is copy-paste ready. | 3 / 3 |
Workflow Clarity | The Initial Assessment section provides a clear sequence for gathering context, and the Output Format section structures deliverables well. However, there's no explicit validation checkpoint or feedback loop for verifying recommendations before implementation. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and headers. References to related skills at the end are helpful. However, this is a long document (~400 lines) that could benefit from splitting detailed sections (like Experiment Ideas) into separate reference files. | 2 / 3 |
Total | 9 / 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.