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.
78
72%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/form-cro/SKILL.mdQuality
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 terms and distinctiveness, with excellent cross-references to related skills and natural language users would actually say. However, it fundamentally fails to explain what the skill does - it's entirely focused on 'when to use' without describing the actual capabilities or actions the skill performs.
Suggestions
Add concrete actions at the beginning describing what the skill does, e.g., 'Analyzes form structure, reduces field count, improves field labels, optimizes form layout, and provides copy recommendations to increase completion rates.'
Restructure to lead with capabilities before the extensive trigger list, following the pattern: '[What it does]. Use when [triggers].'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (form optimization) and lists form types (lead capture, contact, demo request, etc.), but lacks concrete actions describing what the skill actually does - it only describes when to use it, not what specific optimizations or actions it performs. | 2 / 3 |
Completeness | The 'when' is thoroughly covered with explicit triggers and form types, but the 'what' is essentially missing - the description never explains what the skill actually does to optimize forms (e.g., reduce fields, improve copy, restructure layout). | 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' - these are realistic phrases users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly distinguishes itself from related skills by explicitly excluding signup/registration forms (pointing to signup-flow-cro) and popups with forms (pointing to popup-cro), creating a well-defined niche for non-signup form optimization. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a comprehensive, highly actionable form optimization skill with excellent specific guidance and examples. Its main weaknesses are some verbosity in explaining concepts Claude already understands and a lack of explicit workflow for conducting and validating form audits. The structure and progressive disclosure are strong, making it easy to navigate.
Suggestions
Add a clear step-by-step audit workflow at the beginning (e.g., 1. Gather current metrics → 2. Identify issues → 3. Prioritize fixes → 4. Implement → 5. Measure results)
Trim explanatory content Claude already knows, such as basic definitions of form elements and standard UX principles, to improve token efficiency
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some unnecessary explanations Claude would know (e.g., explaining what dropdowns are, basic UX concepts). Some sections like 'Core Principles' explain obvious concepts. However, most content is practical guidance rather than padding. | 2 / 3 |
Actionability | Provides highly specific, actionable guidance throughout: concrete field-by-field recommendations, specific button copy examples, exact mobile tap target sizes (44px+), clear good/bad examples for labels, and specific metrics to track. The guidance is immediately implementable. | 3 / 3 |
Workflow Clarity | The skill covers many form optimization aspects but lacks a clear sequential workflow for conducting a form audit. The 'Initial Assessment' section provides a checklist, but there's no explicit validation/verification step after implementing changes. For a CRO skill involving potentially significant changes, a clearer audit-implement-validate workflow would strengthen this. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections, logical grouping (Core Principles → Field-by-Field → Layout → Form Types → Measurement), and appropriate cross-references to related skills at the end. Content is appropriately contained in a single file given its nature as a reference guide. | 3 / 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.
9d4d29a
Table of Contents
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.