CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

72

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

77%

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

A well-organized, highly actionable reference with strong executable examples and clear error-recovery guidance for Netlify's silent-failure pitfalls. Its main weaknesses are verbosity in several callouts and a monolithic structure with no progressive disclosure into separate reference files.

Suggestions

Tighten the longest blockquotes (reCAPTCHA env-var setup, spam-filtering behavior) to short imperative rules so every token earns its place.

Move the detailed React/SSR example and the Submissions API pagination detail into one-level-deep reference files (e.g. references/ajax.md, references/submissions-api.md) and link them from the body to improve progressive disclosure.

Trim repeated 'do not' phrasing across sections by consolidating the documented-surfaces constraints into a single concise checklist.

DimensionReasoningScore

Conciseness

The body is dense with genuine Netlify-specific gotchas and avoids explaining concepts Claude already knows, but several blockquotes (e.g. the reCAPTCHA env-var paragraph and the spam-filtering callout) are wordy and could be tightened without losing information.

2 / 3

Actionability

Provides fully executable HTML, vanilla JS, JSX/TSX, and an API endpoint table that are copy-paste ready, with concrete fetch bodies and field markup rather than pseudocode.

3 / 3

Workflow Clarity

Key workflows carry explicit checkpoints (trigger a new deploy, create the skeleton file, name must match, fetch must target the skeleton path) plus an SSR troubleshooting feedback loop and a 'report the exact error and stop' validation step.

3 / 3

Progressive Disclosure

The skill is a single ~190-line monolithic SKILL.md with no references/scripts/assets bundle; sections are well organized, but content like the detailed React example, reCAPTCHA env-var details, and pagination notes is inline where one-level-deep reference files could offload it.

2 / 3

Total

10

/

12

Passed

Description

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.

The description is specific, third-person, and explicitly covers both capability and trigger context, hitting the top anchor on all dimensions. It uses natural trigger terms and carves out a distinct niche with negligible conflict risk.

DimensionReasoningScore

Specificity

Lists multiple concrete actions across 'adding contact forms, feedback forms, file upload forms' and enumerates capabilities like 'the data-netlify attribute, spam filtering, AJAX submissions, file uploads, notifications, and the submissions API'.

3 / 3

Completeness

Clearly answers both what ('Guide for using Netlify Forms for HTML form handling') and when via an explicit trigger clause ('Use when adding contact forms... or any form that should be collected by Netlify').

3 / 3

Trigger Term Quality

Natural user-facing terms are well covered: 'contact forms, feedback forms, file upload forms', 'HTML form handling', and 'Netlify Forms' are phrases a user would actually say.

3 / 3

Distinctiveness Conflict Risk

'Netlify Forms' is a clear, narrow niche with distinct triggers unlikely to collide with other skills, anchored to a specific platform and feature surface.

3 / 3

Total

12

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
netlify/context-and-tools
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.