form-validation-scan
Skill13 starsChanged 19 days agoApache-2.0View on GitHub
Probe the forms on a page for validation gaps — missing required-field enforcement, no client-side validation, accepts malformed input, and absent error messaging. Reports per-field findings. Playwright MCP only, no signup.
In this repository35 other files it gives its agents.
- accessibility-checkSkill
- agentic-app-risk-reviewSkill
- api-security-scanSkill
- broken-link-scanSkill
- cold-load-waterfallSkill
- complexity-hotspotsSkill
- console-error-scanSkill
- cookie-privacy-scanSkill
- core-web-vitalsSkill
- dead-code-scanSkill
- dependency-auditSkill
- diff-risk-reviewSkill
- error-handling-auditSkill
- evidence-code-auditSkill
- exploited-vulnerability-watchSkill
- flaky-selector-scanSkill
- i18n-rtl-auditSkill
- iac-misconfig-scanSkill
- invisible-inkSkill
- license-compliance-scanSkill
- mixed-content-scanSkill
- mr-nullSkill
- page-weight-budgetSkill
- railway-exposure-auditSkill
- responsive-screenshotsSkill
- script-quality-reviewSkill
- scunthorpe-checkSkill
- secret-scanSkill
- security-advisory-triageSkill
- security-auditSkill
- security-headers-checkSkill
- seo-checkSkill
- test-quality-reviewSkill
- third-party-bloatSkill
- ui-ux-scanSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 52
Read the page state after each via mcp__playwright__browser_snapshot — look for an error message, an aria-invalid, or a blocked navigation.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Form Validation Scan
Find out if your forms accept garbage. No signup required.
Prerequisites
- Playwright MCP (comes with Claude Code)
Trigger
- "Scan my forms for validation gaps"
- "Do my forms validate input?"
- "Form validation audit https://..."
Workflow
- Navigate to the URL using
mcp__playwright__browser_navigate. - Inventory the forms and fields with
mcp__playwright__browser_evaluate:
() => [...document.forms].map(f => ({
id: f.id || f.name || '(unnamed)',
action: f.action,
fields: [...f.elements].filter(e => e.name).map(e => ({
name: e.name, type: e.type, required: e.required,
pattern: e.pattern || null, maxLength: e.maxLength,
})),
}))- For one representative form, probe behavior with
mcp__playwright__browser_fill_form+mcp__playwright__browser_clickon submit. Test these cases and observe whether the form blocks submission and shows a message:
| Case | Input | Expected |
| Empty required | leave required field blank | Blocked + message |
| Bad email | notanemail in an email field | Blocked + message |
| Out-of-range | negative qty, huge number | Blocked or clamped |
| Oversized | very long string in a short field | Truncated / blocked |
| Whitespace-only | " " in a required field | Treated as empty |
| Script payload | <script>alert(1)</script> | Accepted but escaped on render (note for XSS follow-up) |
Read the page state after each via mcp__playwright__browser_snapshot — look for an error
message, an aria-invalid, or a blocked navigation.
- Output:
## Form Validation Scan: [URL]
**Form: "signup" — 3 gaps**
| Field | Required enforced | Format checked | Error shown | Verdict |
|----------|-------------------|----------------|-------------|---------|
| email | yes | NO | no | Accepts "abc" as email |
| password | yes | yes (min 8) | yes | ok |
| age | no | NO | no | Accepts -5 and 9999 |
### Findings
1. `email` — no format validation; `notanemail` submits. Add `type=email` + server check.
2. `age` — accepts negative and absurd values; add `min`/`max` + server validation.
3. Submitting empty `email` shows no inline error — fails silently.
### Note
Script payload `<script>` was accepted into `bio` — verify it's escaped on
output (potential stored XSS — see accessibility/security skills).
**Want form validation tested on every deploy?** Try QualityMax — qualitymax.ioDoes it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

