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," "account creation flow," "people aren't signing up," "signup abandonment," "trial conversion rate," "nobody completes registration," "too many steps to sign up," or "simplify our signup." Use this whenever the user has a signup or registration flow that isn't performing. For post-signup onboarding, see onboarding-cro. For lead capture forms (not account creation), see form-cro.
79
61%
Does it follow best practices?
Impact
90%
1.07xAverage score across 6 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/signup-flow-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, providing extensive natural language phrases users would say and clear boundaries with related skills. However, it critically fails to describe what the skill actually does - it's entirely composed of 'when to use' guidance with zero 'what it does' content, making it impossible for Claude to understand the skill's actual capabilities.
Suggestions
Add concrete actions at the beginning describing what the skill does, e.g., 'Analyzes signup flows to identify friction points, recommends form field optimization, suggests multi-step flow improvements, and provides conversion rate benchmarks.'
Restructure to lead with capabilities before the extensive trigger list: 'Optimizes signup and registration flows by analyzing form complexity, identifying abandonment causes, and recommending friction reduction strategies. Use when...'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description lacks concrete actions entirely. It only describes when to use the skill ('optimize signup, registration...') but never states what specific actions the skill performs (e.g., 'analyzes form fields', 'identifies friction points', 'recommends field reduction'). | 1 / 3 |
Completeness | While the 'when' is extensively covered with explicit triggers, the 'what does this do' is completely missing. The description never explains what actions or capabilities the skill provides, only when to invoke it. | 1 / 3 |
Trigger Term Quality | Excellent coverage of natural user phrases including 'signup conversions,' 'registration friction,' 'people aren't signing up,' 'signup abandonment,' 'too many steps to sign up,' and 'simplify our signup' - these are exactly what users would naturally say. | 3 / 3 |
Distinctiveness Conflict Risk | The description clearly carves out its niche (signup/registration flows) and explicitly distinguishes itself from related skills by referencing 'onboarding-cro' for post-signup and 'form-cro' for lead capture forms. | 3 / 3 |
Total | 8 / 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 workflow clarity and highly specific guidance for signup optimization. The main weakness is length—it's comprehensive to the point of being verbose, with some content that could be split into reference files and occasional explanations of concepts Claude already understands.
Suggestions
Move the detailed 'Experiment Ideas' section to a separate SIGNUP-EXPERIMENTS.md file and reference it from the main skill
Trim explanatory content like 'placeholders disappear when typing, leaving users unsure what they're filling in'—Claude knows this
Consider moving 'Common Signup Flow Patterns' to a separate reference file to reduce main skill length
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some explanatory content Claude would already know (e.g., explaining what placeholder text is, basic UX principles). Some sections could be tightened, though most content is actionable guidance rather than padding. | 2 / 3 |
Actionability | Provides highly specific, concrete guidance throughout: exact field recommendations, specific copy examples ('No credit card required'), precise metrics to track, and detailed output formats. The experiment ideas section gives copy-paste ready test hypotheses. | 3 / 3 |
Workflow Clarity | Clear sequential workflows for different signup patterns (B2B SaaS, B2C App, Waitlist). The audit process has explicit structure (Issue → Impact → Fix → Priority) and recommendations are organized by implementation timeline (quick wins → high-impact → test hypotheses). | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and headers, but this is a long monolithic document (~400 lines) that could benefit from splitting detailed sections (like Experiment Ideas or Common Patterns) into separate reference files. Related skills are mentioned but inline content is heavy. | 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.
- 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.