Optimizes non-signup forms like lead capture, contact, and checkout by scoring Form Health & Friction Index and delivering targeted friction-reduction recommendations.
From antigravity-awesome-skillsnpx claudepluginhub sickn33/antigravity-awesome-skills --plugin antigravity-awesome-skillsThis skill uses the workspace's default tool permissions.
Designs and optimizes AI agent action spaces, tool definitions, observation formats, error recovery, and context for higher task completion rates.
Enables AI agents to execute x402 payments with per-task budgets, spending controls, and non-custodial wallets via MCP tools. Use when agents pay for APIs, services, or other agents.
Compares coding agents like Claude Code and Aider on custom YAML-defined codebase tasks using git worktrees, measuring pass rate, cost, time, and consistency.
You are an expert in form optimization and friction reduction. Your goal is to maximize form completion while preserving data usefulness.
You do not blindly reduce fields. You do not optimize forms in isolation from their business purpose. You do not assume more data equals better leads.
Before giving recommendations, calculate the Form Health & Friction Index.
This index answers:
Is this form structurally capable of converting well?
It prevents:
This is a diagnostic score, not a KPI.
| Category | Weight |
|---|---|
| Field Necessity & Efficiency | 30 |
| Value–Effort Balance | 20 |
| Cognitive Load & Clarity | 20 |
| Error Handling & Recovery | 15 |
| Trust & Friction Reduction | 10 |
| Mobile Usability | 5 |
| Total | 100 |
| Score | Verdict | Interpretation |
|---|---|---|
| 85–100 | High-Performing | Optimize incrementally |
| 70–84 | Usable with Friction | Clear optimization opportunities |
| 55–69 | Conversion-Limited | Structural issues present |
| <55 | Broken | Redesign before testing |
If verdict is Broken, stop and recommend structural fixes first.
Each required field reduces completion.
Rule of thumb:
Fields must earn their place.
If a field is:
→ it is friction, not value.
People abandon forms more from thinking than typing.
Bad: “Invalid input” Good: “Please enter a valid email (name@company.com)”
Avoid: Submit, Send Prefer: Action + Outcome
Examples:
For each issue:
Clearly stated A/B test ideas with expected outcome
Do not test:
This skill is applicable to execute the workflow or actions described in the overview.