Name: signup-flow-cro
Rating: 45.6 (1 reviews)
Author: administrakt0r

signup-flow-cro

You are an expert in optimizing signup and registration flows. Your goal is to reduce friction, increase completion rates, and set users up for successful activation.

Quality

47%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/signup-flow-cro/SKILL.md

The canonical home for this skill is signup-flow-cro in administrakt0r/AI-Agents-Safe-Coding-Skills

Quality

Content

42%Weight 40%Scale 1-5

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

The body is a well-organized but oversized reference that leans heavily on generic UX/CRO knowledge Claude already has, with a concrete audit output framework as its strongest part. It would benefit from trimming common-knowledge content and externalizing bulky sections into reference files.

Suggestions

Move the large 'Experiment Ideas' and 'Common Signup Flow Patterns' sections into separate reference files (e.g. references/experiments.md) and link to them from the body to reduce inline token bulk.

Cut generic UX advice Claude already knows (44px touch targets, show-password toggle, inline validation) and keep only signup-specific tactical guidance.

Add an explicit procedural sequence with checkpoints (assess current state -> audit fields -> prioritize quick wins / high-impact / tests -> deliver structured findings) so the workflow is a clear process rather than a reference dump.

Dimension	Reasoning	Score
Conciseness	The ~360-line body reiterates a great deal of generic UX knowledge Claude already has (44px touch targets, show-password toggles, inline validation, single-column layouts) and includes a very large 'Experiment Ideas' section of generic test ideas, making it noticeably verbose with several padded sections despite the bullet-list format.	2 / 5
Actionability	There is concrete guidance (the Issue/Impact/Fix/Priority output format, field-priority lists, the progressive-commitment pattern, specific microcopy examples), but much of the body is generic advice ('Use smart defaults', 'Reduce typing') without specific executable steps.	3 / 5
Workflow Clarity	A loose sequence exists ('Before providing recommendations, understand...' then Output Format), but the body reads more like a reference manual than a tightly sequenced workflow, and validation/checkpoint feedback loops are only implicit; this is advisory rather than destructive, so the workflow cap does not apply.	3 / 5
Progressive Disclosure	Section headers are clear and well-organized, but the skill is a monolithic ~360-line SKILL.md with no bundle files and no one-level-deep references; bulky sections like 'Experiment Ideas' and 'Common Signup Flow Patterns' are inlined rather than split into separate reference files.	3 / 5
	Total	11 / 20 Passed

Description

52%Weight 40%Scale 1-5

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 clearly identifies the signup-CRO domain and uses natural trigger terms, but it is written in second person, describes goals rather than concrete actions, and lacks an explicit 'Use when' clause. Adding a trigger clause and concrete actions would lift the weakest dimensions.

Suggestions

Add an explicit 'Use when...' trigger clause, e.g. 'Use when optimizing signup or registration flows, auditing form completion rates, or reducing signup friction.'

Rewrite in third person with concrete actions, e.g. 'Optimizes signup and registration flows: audits forms, recommends field reductions, and designs A/B tests to reduce friction and lift completion rates.'

Include natural synonyms such as 'account creation' and 'conversion' to broaden trigger coverage and distinguish from form-cro/onboarding-cro.

Dimension	Reasoning	Score
Specificity	The description names the domain ('optimizing signup and registration flows') and a few outcomes ('reduce friction, increase completion rates, set up for successful activation'), but these are goals rather than concrete actions like auditing forms or designing A/B tests; the second-person voice ('You are an expert', 'Your goal') triggers the rubric's -1 specificity penalty, dropping a base 3 to 2.	2 / 5
Completeness	It clearly states what the skill does, but there is no 'Use when...' clause or equivalent explicit trigger guidance, so per the rubric completeness is capped at 3.	3 / 5
Trigger Term Quality	Natural terms a user would say are present ('signup', 'registration flows', 'friction', 'completion rates', 'activation'), giving good coverage, though common synonyms like 'account creation' or 'conversion rate' are missing.	4 / 5
Distinctiveness Conflict Risk	The signup/registration niche is somewhat specific, but the generic CRO framing ('reduce friction, increase completion rates') overlaps with sibling skills the body itself lists (form-cro, onboarding-cro), so overlap risk remains.	3 / 5
	Total	12 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/signup-flow-cro/SKILL.md
Commit: 57c135b

Reviewed: 19 hours 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.