netlify-forms
Guide for using Netlify Forms for HTML form handling. Use when adding contact forms, feedback forms, file upload forms, or any form that should be collected by Netlify. Covers the data-netlify attribute, spam filtering, AJAX submissions, file uploads, notifications, and the submissions API.
68
82%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly identifies its domain (Netlify Forms), lists specific capabilities and features covered, and includes an explicit 'Use when...' clause with natural trigger terms. It is well-scoped and distinctive, making it easy for Claude to select appropriately from a large skill set.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and features: contact forms, feedback forms, file upload forms, data-netlify attribute, spam filtering, AJAX submissions, file uploads, notifications, and the submissions API. | 3 / 3 |
Completeness | Clearly answers both 'what' (guide for Netlify Forms covering data-netlify attribute, spam filtering, AJAX submissions, etc.) and 'when' (explicit 'Use when adding contact forms, feedback forms, file upload forms, or any form that should be collected by Netlify'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'contact forms', 'feedback forms', 'file upload forms', 'Netlify', 'form handling', 'spam filtering', 'AJAX submissions', 'notifications'. These cover common variations of how users would describe form-related tasks on Netlify. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to Netlify Forms specifically, with distinct triggers like 'data-netlify attribute', 'Netlify', and 'submissions API' that are unlikely to conflict with generic form-handling or other platform-specific skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, highly actionable skill with excellent concrete examples covering the full spectrum of Netlify Forms usage. Its main weakness is the lack of explicit validation checkpoints (e.g., verifying form detection in the Netlify UI before testing submissions) and some minor verbosity. The SSR-specific guidance is particularly valuable and represents genuine domain knowledge that Claude wouldn't inherently know.
Suggestions
Add a verification step after form setup, e.g., 'After deploying, confirm the form appears in Netlify UI > Forms before testing submissions'
Consider extracting the API reference table and the full React example into separate referenced files to improve progressive disclosure
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with good code examples, but includes some explanatory text that could be tightened (e.g., the SSR troubleshooting callout partially repeats the earlier SSR note, and some phrasing like 'Netlify Forms collects HTML form submissions without server-side code' explains what Claude already knows). The SSR guidance is genuinely useful domain knowledge though. | 2 / 3 |
Actionability | Excellent actionability throughout — every section provides fully executable, copy-paste-ready code examples (HTML forms, AJAX submissions, React components, file uploads, API endpoints). The API table with specific methods and paths is immediately usable. The SSR skeleton file pattern is concrete and complete. | 3 / 3 |
Workflow Clarity | The content covers multiple scenarios clearly (basic setup, JS-rendered forms, AJAX, file uploads) with good sequencing within each section. However, there are no explicit validation/verification steps — no guidance on how to confirm form detection succeeded, no 'check the Netlify Forms UI to verify registration' step, and the troubleshooting is reactive rather than built into a workflow with checkpoints. | 2 / 3 |
Progressive Disclosure | The content is well-organized with clear section headers and logical progression from basic to advanced topics. However, at ~150 lines it's moderately long and some sections (like the full React example or the API table) could be split into referenced files. With no bundle files, everything is inline, which is acceptable but not optimal for this amount of content. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- netlify/context-and-tools
- Commit
cffaf74
- Reviewed
Table of Contents
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.