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.
Install with Tessl CLI
npx tessl i github:coreyhaines31/marketingskills --skill signup-flow-croOverall
score
80%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillEvaluation — 100%
↑ 1.18xAgent success when using this skill
Validation for skill structure
Discovery
72%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 distinctiveness, with helpful cross-references to related skills that clarify boundaries. However, it's weak on specificity - it tells Claude when to use the skill but not what concrete actions or capabilities it provides for optimizing signup flows.
Suggestions
Add specific capabilities at the beginning, e.g., 'Analyzes and optimizes signup flows by reducing form fields, improving CTAs, streamlining multi-step registration, and identifying dropoff points.'
Restructure to lead with 'what it does' before the 'Use when...' clause to follow the pattern of good examples in the rubric.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (signup/registration flows) and mentions optimization, but doesn't list specific concrete actions like 'analyze form fields', 'reduce form steps', or 'A/B test CTAs'. The description focuses more on when to use it than what it actually does. | 2 / 3 |
Completeness | Strong on 'when' with explicit trigger terms and boundary clarifications (references to onboarding-cro and form-cro), but weak on 'what' - doesn't clearly explain what actions or capabilities the skill provides for optimization. | 2 / 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'. | 3 / 3 |
Distinctiveness Conflict Risk | Excellent distinctiveness with explicit boundary definitions separating it from 'onboarding-cro' (post-signup) and 'form-cro' (lead capture). Clear niche focused specifically on account creation flows. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, actionable skill with excellent concrete guidance for signup flow optimization. The content is well-structured with clear workflows and specific recommendations. However, it's somewhat verbose for a skill file and could benefit from splitting detailed reference content (experiment ideas, common patterns) into separate files to improve token efficiency.
Suggestions
Move 'Experiment Ideas' and 'Common Signup Flow Patterns' sections to separate reference files (e.g., EXPERIMENTS.md, PATTERNS.md) and link from the main skill
Trim basic UX guidance that Claude already knows (e.g., 'larger touch targets 44px+', 'single column layout') to improve conciseness
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some content Claude would already know (e.g., basic UX principles like 'larger touch targets', 'single column layout'). Some sections could be tightened, though most content is relevant and actionable. | 2 / 3 |
Actionability | Provides highly specific, concrete guidance throughout: exact field recommendations, specific copy examples, detailed audit output formats, and clear experiment ideas. The recommendations are immediately actionable without needing additional context. | 3 / 3 |
Workflow Clarity | Clear workflow structure with Initial Assessment → Core Principles → Field Optimization → Measurement → Output Format. The audit findings format with Issue/Impact/Fix/Priority provides explicit structure, and the task-specific questions create a clear discovery process. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and headers, but the skill is quite long (~400 lines) with all content inline. Some sections like 'Experiment Ideas' or 'Common Signup Flow Patterns' could be split into separate reference files for better navigation. | 2 / 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.
Table of Contents
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.