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.
77
Quality
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 ./config/claude/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 clear boundary conditions that prevent conflicts with related skills. However, it fails to explain what the skill actually does - it only describes when to use it, not the concrete actions or capabilities it provides. Adding specific actions like 'analyze form fields', 'reduce friction', or 'improve completion rates' would significantly improve it.
Suggestions
Add a 'what it does' clause at the beginning describing concrete actions (e.g., 'Analyzes and optimizes form design, field count, labels, and user flow to improve completion rates')
Include specific optimization techniques or outputs the skill provides (e.g., 'provides field reduction recommendations, copy improvements, and A/B test suggestions')
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (form optimization) and lists form types (lead capture, contact, demo request, application, survey, checkout), but doesn't describe concrete actions like 'reduce fields', 'improve labels', or 'analyze completion rates'. | 2 / 3 |
Completeness | Strong 'when' clause with explicit triggers and boundary conditions (references to related skills), but weak 'what' - it never explains what the skill actually does beyond implying optimization. The description focuses entirely on when to use it, not what it does. | 2 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'form optimization', 'lead form conversions', 'form friction', 'form fields', 'form completion rate', 'contact form', plus specific form types like 'demo request forms' and 'checkout forms'. | 3 / 3 |
Distinctiveness Conflict Risk | Excellent distinctiveness with explicit boundary conditions: 'NOT signup/registration', references to 'signup-flow-cro' and 'popup-cro' for related cases. Clear niche carved out 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 and highly actionable form optimization skill with excellent organization and specific guidance. The main weaknesses are moderate verbosity (explaining concepts Claude already understands) and missing explicit validation/verification steps in the audit workflow. The field-by-field and form-type-specific sections are particularly strong.
Suggestions
Trim explanatory content that Claude already knows (e.g., 'Each field reduces completion rate' is obvious; just provide the data)
Add explicit validation checkpoints to the audit workflow, such as 'Confirm field necessity with stakeholder before recommending removal' or 'Verify analytics access before promising field-level drop-off analysis'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some unnecessary explanations Claude would know (e.g., explaining what inline validation is, basic UX concepts). Some sections like 'Core Principles' explain concepts that are fairly obvious to an AI assistant. | 2 / 3 |
Actionability | Provides highly specific, concrete guidance throughout - exact field recommendations, specific button copy examples, precise mobile tap target sizes (44px), and clear good/bad examples for labels and error messages. | 3 / 3 |
Workflow Clarity | The Initial Assessment section provides a clear sequence for gathering information, but the overall document lacks explicit validation checkpoints. For form audits, there's no clear 'verify with user' or 'test before recommending' steps in the workflow. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections, logical grouping by topic (field types, form types, mobile, measurement), and appropriate cross-references to related skills at the end. Content is appropriately structured for a comprehensive skill. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
90%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
- freekmurze/dotfiles
- Commit
355d067
- Reviewed
Table of Contents
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.