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.

Quality

49%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

—

The risk profile of this skill

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/signup-flow-cro/SKILL.md

Quality

Content

27%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill reads like a comprehensive CRO textbook chapter rather than a targeted skill for Claude. It is excessively verbose, explaining many UX and conversion optimization concepts that Claude already understands. While the output format and common patterns sections add some value, the bulk of the content could be reduced by 60-70% without losing actionable information.

Suggestions

Reduce content by at least 50% — remove explanations of basic UX concepts (touch targets, inline validation, keyboard types) that Claude already knows, and focus only on the specific decision framework and output format.

Extract the lengthy 'Experiment Ideas' section and 'Common Signup Flow Patterns' into separate bundle files (e.g., EXPERIMENTS.md, PATTERNS.md) referenced from the main skill to improve progressive disclosure.

Add a clear step-by-step workflow with validation checkpoints, e.g.: 1) Read context file → 2) Ask clarifying questions → 3) Audit current flow → 4) Verify findings against metrics → 5) Deliver recommendations in specified format.

Make the output format more actionable by providing a concrete example of a completed audit finding rather than just describing the template structure.

Dimension	Reasoning	Score
Conciseness	At ~300+ lines, this skill is extremely verbose. It explains many concepts Claude already knows (what social auth is, how password fields work, basic UX principles like 'larger touch targets'). Sections like 'Mobile Signup Optimization' and 'Trust and Friction Reduction' are largely common knowledge for Claude. The experiment ideas section alone is massive and reads like a generic CRO textbook rather than targeted instructions.	1 / 3
Actionability	The skill provides structured recommendations and a clear output format (audit findings with Issue/Impact/Fix/Priority), which is useful. However, there is no executable code, no concrete implementation examples, and much of the guidance is general best-practice advice rather than specific, copy-paste-ready instructions. The experiment ideas are lists of things to try rather than concrete implementations.	2 / 3
Workflow Clarity	The initial assessment section provides a reasonable sequence (gather context → assess → recommend), and the output format section structures deliverables well. However, there are no explicit validation checkpoints or feedback loops. The workflow for conducting an audit is implicit rather than explicitly sequenced with verification steps.	2 / 3
Progressive Disclosure	This is a monolithic wall of text with no bundle files or references to supporting documents. All content is inline in a single massive file. The experiment ideas section alone could be a separate reference file. Related skills are mentioned at the end but no content is appropriately split into separate files for deeper reference.	1 / 3
	Total	6 / 12 Passed

Description

72%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description excels at trigger term coverage and distinctiveness, with explicit cross-references to related skills that reduce conflict risk. However, it is weak on specificity of capabilities — it tells Claude when to use the skill but not what concrete actions or outputs the skill provides. Adding specific actions (e.g., 'analyzes signup funnels, recommends form simplification, suggests social login integration') would significantly improve it.

Suggestions

Add concrete capability descriptions such as 'Analyzes signup funnels, recommends form field reduction, suggests social login options, identifies dropoff points, and provides A/B test recommendations for registration flows.'

Restructure to lead with 'what it does' before 'when to use it' — e.g., 'Optimizes signup and registration flows by analyzing conversion funnels, reducing form friction, and improving trial activation rates. Use when...'

Dimension	Reasoning	Score
Specificity	The description names the domain (signup/registration flow optimization) and mentions some actions like 'optimize signup, registration, account creation, or trial activation flows,' but it doesn't list multiple specific concrete actions (e.g., A/B test form fields, reduce form steps, implement social login). It's more about when to use it than what it concretely does.	2 / 3
Completeness	The 'when' is very well covered with explicit trigger terms and use cases, but the 'what' is weak — it says 'optimize' flows but doesn't describe what concrete actions or outputs the skill provides. The description is heavily skewed toward trigger guidance without clearly explaining what the skill actually does.	2 / 3
Trigger Term Quality	Excellent coverage of natural trigger terms: 'signup,' 'registration,' 'account creation,' 'trial activation,' 'signup conversions,' 'registration friction,' 'signup form optimization,' 'free trial signup,' 'reduce signup dropoff,' 'account creation flow.' These are terms users would naturally use.	3 / 3
Distinctiveness Conflict Risk	The description explicitly differentiates itself from related skills ('onboarding-cro' for post-signup and 'form-cro' for lead capture forms), creating clear boundaries. The trigger terms are specific to signup/registration flows, making conflicts unlikely.	3 / 3
	Total	10 / 12 Passed

Validation

90%

Warnings & errors only

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: TheCraigHewitt/seomachine
Path: .claude/skills/signup-flow-cro/SKILL.md
Commit: e818d5e

Reviewed: 6 days ago

Table of Contents

Discovery Implementation Validation

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.