Forms often lose qualified visitors through excess fields, unclear copy, and weak error handling. This skill helps Claude, Codex, or Claude Code audit forms and recommend field, layout, copy, trust, and testing improvements.
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Agent request
Review the Skillstore skill "form-cro" from https://skillstore.io/skills/coreyhaines31-form-cro.md and its manifest at https://skillstore.io/api/skills/coreyhaines31-form-cro/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.
Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
All six static findings are false positives caused by Markdown examples and form validation copy in SKILL.md. No evidence of executable commands, prompt injection, data exfiltration intent, or system reconnaissance was found.
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Reduce unnecessary fields and clarify the value exchange for gated content or newsletter forms.
Redesign Complex Request Forms
Break long quote, application, or survey forms into clearer steps with better field sequencing.
Increase Demo Request Quality
Balance sales qualification needs with lower friction for prospects who request a demo.
Try These Prompts
Basic Form Audit
Audit this contact form for conversion issues. The fields are name, email, phone, company, message, and budget. Recommend the highest-impact fixes.
Field Reduction Plan
Review this lead capture form and decide which fields should be required, optional, removed, or asked after submission. Explain the tradeoffs.
Mobile Form Redesign
Redesign this five-field demo request form for mobile completion. Include field order, labels, validation behavior, button copy, and trust messaging.
Experiment Roadmap
Create an A/B testing plan for this form using completion rate, field drop-off, error rate, and mobile versus desktop data. Prioritize three experiments.
Best Practices
Provide current fields, completion rate, device split, and known drop-off points when available.
Ask for recommendations by priority so design, copy, and analytics changes are easy to sequence.
Validate suggested changes with A/B tests or field-level analytics before making permanent decisions.
Avoid
Do not ask the skill to optimize signup or registration flows covered by another specialist skill.
Do not treat conversion estimates as guaranteed outcomes without testing.
Do not remove legally required fields only to reduce friction.
Frequently Asked Questions
What types of forms does this skill support?
It supports lead capture, contact, demo request, application, survey, quote, checkout, and similar non-signup forms.
Can it help choose which fields to remove?
Yes. It evaluates each field against user effort, business need, follow-up value, and timing.
Does it write production form code?
No. It provides UX, copy, layout, validation, measurement, and testing recommendations.
What information should I provide?
Provide the form type, current fields, completion rate, device split, drop-off data, and business requirements.
Can it improve mobile forms?
Yes. It covers tap targets, keyboard types, single-column layout, autofill, sticky submit buttons, and minimal typing.
Is it suitable for signup forms?
No. Signup and registration flows should use a dedicated signup-flow CRO skill.