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," "contact form," "nobody fills out our form," "form abandonment," "too many fields," "demo request form," or "lead form isn't converting." Use this for any non-signup form that captures information. For signup/registration forms, see signup-flow-cro. For popups containing forms, see popup-cro.

Quality

61%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/form-cro/SKILL.md

Quality

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 explicit cross-references to related skills that prevent overlap. However, it is notably weak on describing what the skill actually does — it reads more like a routing rule than a capability description. Adding concrete actions (e.g., 'Analyzes form fields, recommends field reduction, suggests progressive disclosure, and improves form completion rates') would significantly improve it.

Suggestions

Add concrete actions describing what the skill does, e.g., 'Analyzes form structure, recommends field reduction strategies, suggests progressive disclosure patterns, and provides copy improvements to increase form completion rates.'

Restructure to lead with capabilities ('what it does') before the trigger/routing guidance ('when to use it') for better readability and to ensure Claude understands the skill's outputs.

Dimension	Reasoning	Score
Specificity	The description names the domain (form optimization for non-signup forms) and lists form types (lead capture, contact, demo request, application, survey, checkout), but it doesn't describe concrete actions the skill performs — it only describes when to use it, not what it actually does (e.g., 'reduces form fields,' 'adds progressive disclosure,' 'improves completion rates').	2 / 3
Completeness	The 'when' is exceptionally well-covered with explicit triggers and boundary conditions (referencing related skills for signup and popup forms). However, the 'what does this do' is weak — it never states what actions or outputs the skill produces, only what types of forms it applies to.	2 / 3
Trigger Term Quality	Excellent coverage of natural trigger terms users would say: 'form optimization,' 'lead form conversions,' 'form friction,' 'nobody fills out our form,' 'form abandonment,' 'too many fields,' 'demo request form,' 'lead form isn't converting,' 'contact form,' and 'form completion rate.' These are highly natural phrases.	3 / 3
Distinctiveness Conflict Risk	Very clearly distinguished from related skills with explicit boundary statements ('For signup/registration forms, see signup-flow-cro. For popups containing forms, see popup-cro.'). The niche of non-signup form optimization is well-defined and unlikely to conflict with other skills.	3 / 3
	Total	10 / 12 Passed

Implementation

50%

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

This is a thorough form optimization reference that covers the domain comprehensively with useful heuristics (field count impact percentages, specific button copy examples, mobile sizing guidelines). Its main weaknesses are verbosity — much content could be trimmed or split into sub-files — and a lack of explicit workflow sequencing with validation checkpoints. The guidance is practical but sits at the advisory level rather than providing truly executable, copy-paste-ready artifacts.

Suggestions

Split the experiment ideas and form-type-specific guidance into separate referenced files (e.g., FORM-EXPERIMENTS.md, FORM-TYPES.md) to reduce the main skill's token footprint.

Add an explicit numbered workflow: 1) Read context → 2) Identify form type → 3) Audit current fields against business needs → 4) Validate recommendations against compliance requirements → 5) Produce output. This would improve workflow clarity.

Trim explanations of concepts Claude already knows (e.g., what inline validation is, how dropdowns work, what checkboxes are) to just the optimization-specific guidance.

Add a concrete example of a complete form audit output (e.g., a sample 'before' form with 8 fields and the recommended 'after' with 4 fields, including specific copy) to improve actionability.

Dimension	Reasoning	Score
Conciseness	The skill is comprehensive but overly verbose in places. Sections like 'Field-by-Field Optimization' explain things Claude already knows (e.g., what inline validation is, how dropdowns work). The experiment ideas section significantly bloats the document with items that could be inferred. However, the rule-of-thumb numbers and specific patterns do earn their place.	2 / 3
Actionability	The skill provides specific recommendations (e.g., 44px touch targets, field reduction percentages, button copy examples) but lacks executable code or implementation snippets. It's mostly instructional guidance with good/bad examples for copy, but nothing is truly copy-paste ready for implementation. The output format section provides a useful audit framework but remains template-level.	2 / 3
Workflow Clarity	The initial assessment section provides a clear sequence for gathering information, and the output format gives structure for deliverables. However, there's no explicit validation or feedback loop — no step like 'verify recommendations against business constraints' or 'check field necessity against data usage.' The overall flow from assessment → principles → recommendations → output is implicit rather than explicitly sequenced.	2 / 3
Progressive Disclosure	The document is well-organized with clear headers and logical sections, and it references related skills at the bottom. However, at ~350+ lines, significant content (like the full experiment ideas section or form-type-specific guidance) could be split into separate reference files. The monolithic structure means Claude loads everything even when only a contact form audit is needed.	2 / 3
	Total	8 / 12 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: coreyhaines31/marketingskills
Commit: 2c7c108

Reviewed: 4 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.