Name: netlify-forms
Rating: 74.4 (1 reviews)
Author: netlify

netlify-forms

Serverless form handling on Netlify-hosted sites — detects HTML forms at deploy time, stores submissions, filters spam, and sends notifications. Use when adding a contact form, lead-capture form, file-upload form, or newsletter signup to a Netlify site; wiring AJAX form submission; setting up a custom thank-you page; adding a honeypot or reCAPTCHA to a form; getting forms working in Next.js, Nuxt, SvelteKit, Astro, or Gatsby; reading form submissions via the Netlify API; or debugging missing submissions and forms that silently fail to register.

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

82%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A dense, highly actionable reference skill with executable examples and strong gotcha coverage. Its main weakness is the duplicated 'house rules' section that restates guidance already in the body, inflating the token budget without adding information.

Suggestions

Remove or de-duplicate the appended 'Netlify house rules (forms)' block — its SSR-skeleton, Astro, Akismet, and extensionless-path points are already covered in the main body, so it adds ~35 redundant lines.

If the house-rules block must be retained for ctx-gen merging, keep only the org-convention items that are NOT already stated above (e.g., the token/CLI-config guardrail) and cross-reference the rest.

Consider collapsing the 'Submission summary (field order matters)' and 'Debugging missing submissions' sections into a single 'Gotchas' section to reduce cross-referencing for the reader.

Dimension	Reasoning	Score
Conciseness	The core body is lean and assumes Claude's competence (no library/PDF-style explanations), but the appended 'Netlify house rules (forms)' block duplicates SSR-skeleton, Astro, Akismet, and extensionless-path guidance already stated above, adding redundant tokens.	4 / 5
Actionability	Fully executable, copy-paste-ready code for static forms, the public/__forms.html skeleton, JSX forms, AJAX fetch, file uploads, honeypot, and reCAPTCHA, with the common cases explicitly covered.	5 / 5
Workflow Clarity	Sequenced procedures with checkpoints are present (JSR/SSR 'two required pieces', a prioritized 'Debugging missing submissions' list, and 'Export CSV first' guarding the destructive form deletion), though the skill is procedural-reference rather than a single validate→fix→retry pipeline.	4 / 5
Progressive Disclosure	Well-organized into clearly headed sections with no nested reference chain and no bundle files to misroute; the only structural blemish is the duplicate house-rules section appended at the end.	4 / 5
	Total	17 / 20 Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

An exemplary description: third-person, concrete, and comprehensive, with an explicit 'Use when' clause enumerating concrete trigger scenarios and framework names. It clearly distinguishes the skill and would trigger reliably for the right requests.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "detects HTML forms at deploy time, stores submissions, filters spam, and sends notifications" — giving comprehensive coverage of the skill's capabilities rather than vague abstractions.	5 / 5
Completeness	Explicitly answers both what ("Serverless form handling on Netlify-hosted sites — detects HTML forms...") and when ("Use when adding a contact form...") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Surfaces natural user phrases including form types ("contact form, lead-capture form, file-upload form, newsletter signup"), framework names (Next.js, Nuxt, SvelteKit, Astro, Gatsby), and "honeypot or reCAPTCHA", "AJAX form submission", "debugging missing submissions".	5 / 5
Distinctiveness Conflict Risk	Scoped tightly to "Netlify-hosted sites" with Netlify-specific triggers (Netlify API, Netlify UI form detection), creating a clear niche with minimal overlap risk against other skills.	5 / 5
	Total	20 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: netlify/context-and-tools
Path: codex/skills/netlify-forms/SKILL.md
Commit: 47848e2

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.