AB 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.
As a process B 68/100 · Nearly there — weak spots: inputs and preconditions, consistency, running it twice
How to improve
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 68/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 12 mutating operations with no state check
- 40Consistency. Frontmatter name (form-cro) differs from the folder (abm-form-cro)
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 85Steps. 214 steps, 2 vague phrases
- 100Tools and files. No external tools needed
- 100Failures and branches. 1 branches, has a failure section
- 100Execution cost. Instruction body is 2511 tokens
- low 14 top-level sections: this looks like several domains in one skill
- low No test case covers injection arriving through data
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +4Description does not say when NOT to use the skill (false activations)
- +1No license
- +2Single-language instructions
- +5Description quotes 11 example trigger phrases
- +3Description length 619: enough signal without eating the budget
- +4Structure: 56 headings
- +3Step-by-step instructions: 214 items
- +3Output format is stated explicitly
- +4Has examples (2 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 92.