Form Friction Finder

Finds the fields, validation rules, error states and steps that stop people finishing a form they intended to finish. Use when form starts are healthy and submits are not, or when a field was added and completion dropped.

9 stars 3 forksOther

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add mardab96/landing-pages-claude-skills --skill form-friction-finder
Manual install
git clone --depth 1 https://github.com/mardab96/landing-pages-claude-skills.git /tmp/landing-pages-claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/landing-pages-claude-skills/form-friction-finder ~/.claude/skills/form-friction-finder

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Form Friction Finder

## Use this skill when

- the form's fields, validation behaviour and step structure are available, and starts exceed submits by more than the team can explain.
- a field, a validation rule or a step was added and completion dropped.
- people submit the form with obviously fake values in one particular field.

This skill asks why people stop filling a form in. Whether a field should exist at all belongs to `lead-form-sales-handoff-check`.

## Required input

- the full field list with types, required flags, validation rules and order.
- the step structure: one page, multi-step, progressive, and what the progress indicator says.
- error behaviour: when errors appear, where, and what they say.
- numbers if they exist: form starts, submits, per-field drop-off, time to complete, device split.
- If starts and submits are both unavailable, say the ranking is structural rather than measured. The defects are still real; their order is not established.

### If the data does not exist

- **No form starts:** GA4 fires `form_start` and `form_submit` automatically for many forms under enhanced measurement. Reports, then Engagement, then Events. If they are there, you have both numbers already and did not know it.
Read the full skill on GitHub

Details

Skill name
form-friction-finder
Path
form-friction-finder/SKILL.md
License
MIT
Repo updated
30 July 2026

FAQ

What does the Form Friction Finder skill do?

Finds the fields, validation rules, error states and steps that stop people finishing a form they intended to finish. Use when form starts are healthy and submits are not, or when a field was added and completion dropped.

How do I install the Form Friction Finder skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add mardab96/landing-pages-claude-skills --skill form-friction-finder. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Form Friction Finder popular?

It lives in mardab96/landing-pages-claude-skills, which has 9 GitHub stars and 3 forks.

Related skills

Above the Fold Clarity Review

9

mardab96/landing-pages-claude-skills

Judges what a visitor can actually understand and do in the first screen, before any scroll. Use when bounce is high, when a page was redesigned, or when the hero has to carry cold traffic that knows nothing about the brand.

Frontend & Design

Accessibility Conversion Blocker Check

9

mardab96/landing-pages-claude-skills

Finds the accessibility defects that also block conversion: unreadable contrast, tap targets too small to hit, form fields with no label, and error states nobody can perceive. Use when a page is being shipped, when mobile form completion is poor, or when an audit flagged accessibility and nobody knows which items matter commercially.

Frontend & Design

Comparison Page Positioning Review

9

mardab96/landing-pages-claude-skills

Reviews a "versus competitor" or alternatives page for claims that will not survive contact with the competitor's own page. Use when a comparison page is being written, when it ranks but does not convert, or when a competitor changed their pricing or feature set.

Marketing, Sales & Business

Hero Section Diagnosis

9

mardab96/landing-pages-claude-skills

Reads the headline, subhead, visual and primary CTA as one unit and finds where they contradict each other. Use when each hero element looks fine alone but the section as a whole does not land, or before a hero rewrite ships.

Other

Cta Clarity Check

9

mardab96/landing-pages-claude-skills

Checks whether each call to action states the next step plainly, and whether the page is asking for one thing or quietly asking for five. Use when clicks on the primary action are low, or when a page has accumulated buttons over time.

Other

Mobile Conversion Review

9

mardab96/landing-pages-claude-skills

Diagnoses what breaks on a phone specifically: thumb reach, viewport competition, tap targets, keyboard behaviour and scroll cost. Use when the mobile conversion rate sits well below desktop and the layout is nominally responsive.

Other

Browse the most popular Claude skills, all other skills, or write your own with the skills generator.