form-cro

When the user wants to optimize any form that is NOT signup/registration — including lead capture forms, contact forms, demo request forms, application forms, survey forms, or checkout forms. Also use when the user mentions "form optimization," "lead form conversions," "form friction," "form fields," "form completion rate," or "contact form." For signup/registration forms, see signup-flow-cro. For popups containing forms, see popup-cro.

Quality

78%

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 ./marketing-skill/skills/form-cro/SKILL.md

Quality

Content

67%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, actionable form-audit skill with a real analyzer script, concrete thresholds, and a clear sequenced workflow backed by verified reference files. Its main weakness is verbosity: the extensive inlined experiment catalogs could be trimmed or moved into the playbook reference to lean down the overview.

Suggestions

Move the four experiment catalog sections (Form Structure, Copy & Design, Form Type-Specific, Mobile & UX) into references/form-cro-playbook.md and keep only a brief pointer plus the top 3-5 highest-impact tests in SKILL.md to improve conciseness and progressive disclosure.

Add an explicit verification checkpoint to the workflow (e.g., after the Form Audit, confirm field-justification coverage against business context before producing the Recommended Form Design) to raise workflow clarity.

Tighten the Tools table and Core Principles so each threshold reads as a single decisive line, removing any restated phrasing that does not add new information.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and free of basic-concept padding, but the large inlined experiment catalogs ('Form Structure Experiments', 'Copy & Design Experiments', 'Form Type-Specific Experiments', 'Mobile & UX Experiments') run to dozens of bullets that could be tightened or moved to the playbook, fitting 'mostly efficient but includes some unnecessary...could be tightened'.	3 / 5
Actionability	It gives concrete executable guidance — a real tool invocation 'python3 scripts/form_field_analyzer.py forms.json (no arg = embedded demo; --json for pipelines)', specific thresholds ('3-5 fields is the working ceiling; 7+ required fields is a high-priority finding'), and a defined Issue/Impact/Fix/Priority output structure — with only minor gaps, matching 'mostly executable guidance; concrete code or commands with minor gaps'.	4 / 5
Workflow Clarity	The sequence is clear and ordered: Initial Assessment → run the field analyzer ('Run it on the form definition first; its flags become the seed list for the Form Audit') → Form Audit → Recommended Form Design → Test Hypotheses. As a non-destructive advisory skill it avoids the destructive/batch validation cap, but it lacks explicit verification checkpoints, capping it just below 5.	4 / 5
Progressive Disclosure	Structure is good with clearly signaled one-level-deep references that are real files — 'full treatment in references/form-cro-playbook.md' (verified present) and the scripts/form_field_analyzer.py invocation (verified present) — but substantial experiment content is inlined in SKILL.md rather than pushed into the playbook, keeping it just short of the ideal split.	4 / 5
	Total	15 / 20 Passed

Description

90%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.

A strong, well-structured description that clearly states what it does, when to trigger it with natural user phrases, and where its boundaries lie against sibling skills. The only weakness is that the action vocabulary is essentially the single verb 'optimize' rather than a set of distinct concrete actions.

Dimension	Reasoning	Score
Specificity	The description names the domain and enumerates concrete form types ('lead capture forms, contact forms, demo request forms, application forms, survey forms, or checkout forms'), but the only action verb is 'optimize' — a single generic action applied to many targets, which fits 'names domain and 1-2 concrete actions, but not comprehensive' rather than the multi-action anchors at 4-5.	3 / 5
Completeness	It explicitly answers both 'what' ('optimize any form that is NOT signup/registration...') and 'when' ('Use when the user mentions...') with concrete trigger phrases, matching the top anchor for explicit what-and-when coverage.	5 / 5
Trigger Term Quality	It includes multiple natural trigger phrases users would actually say — '"form optimization," "lead form conversions," "form friction," "form fields," "form completion rate," or "contact form"' — covering synonyms and common variations, matching the comprehensive coverage anchor.	5 / 5
Distinctiveness Conflict Risk	It carves a clear niche (non-signup/registration forms) and gives explicit boundary guidance ('For signup/Registration forms, see signup-flow-cro. For popups containing forms, see popup-cro.'), minimizing conflict risk with related skills.	5 / 5
	Total	18 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: alirezarezvani/claude-skills
Path: marketing-skill/skills/form-cro/SKILL.md
Commit: 19392f7

Reviewed: ~1 hour 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.