netlify-edge-functions

Guide for writing Netlify Edge Functions. Use when building middleware, geolocation-based logic, request/response manipulation, authentication checks, A/B testing, or any low-latency edge compute. Covers Deno runtime, context.next() middleware pattern, geolocation, and when to choose edge vs serverless.

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

The canonical home for this skill is netlify-edge-functions in netlify/context-and-tools

Quality

Content

92%

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

A well-organized, concise, and highly actionable reference skill with executable code throughout. The only weakness is progressive disclosure: at ~120 lines it is a single monolithic doc that could offload some detail (limits, module support) into reference files.

Suggestions

Move the Limits table and the import-map/netlify.toml module-support detail into a reference file (e.g., references/ADVANCED.md) and link to it from the body, splitting content one level deep to improve progressive disclosure toward the score-3 anchor.

Add a brief one-line "Quick start" pointer at the top that links to the syntax example, so the overview reads as a clear entry point into the detail sections.

Confirm the netlify.png/netlify.svg assets in ./assets are intentionally unreferenced; if they are meant to illustrate deployment topology, link them, otherwise they are unused bundle weight.

Dimension	Reasoning	Score
Conciseness	Lean and directive with no padding and no explanation of concepts Claude already knows (e.g., "Place files in `netlify/edge-functions/`.", "Use `Netlify.env` (not `process.env` or `Deno.env`):"), matching the score-3 anchor where every token earns its place.	3 / 3
Actionability	Provides fully executable TypeScript with real imports and specific config values (e.g., `onError: "bypass"`, `cache: "manual"`) plus a concrete dev command (`netlify dev --geo=mock --country=US`), matching the score-3 anchor for copy-paste ready code.	3 / 3
Workflow Clarity	Although not a multi-step workflow, the single action (write an edge function) is unambiguous and clearly sequenced through sections (Syntax → Config → Middleware → Geo → Limits), so per the simple-skills scoring note it reaches 3; no destructive or batch operations require validation checkpoints.	3 / 3
Progressive Disclosure	Sections are well-organized and there are no nested references, but the ~120-line body keeps detail that could be split (the Limits table and the import-map/netlify.toml module-support detail) inline rather than offloaded to reference files, matching the score-2 anchor more closely than the score-3 "content appropriately split" anchor.	2 / 3
	Total	11 / 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.

A strong, specific description that clearly states both capabilities and explicit "Use when..." triggers, with natural trigger terms and a distinct niche unlikely to conflict with other skills.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions tied to a named domain — "building middleware, geolocation-based logic, request/response manipulation, authentication checks, A/B testing" — matching the score-3 anchor for listing several specific concrete actions rather than naming only some.	3 / 3
Completeness	Explicitly answers what ("Guide for writing Netlify Edge Functions... Covers Deno runtime, context.next() middleware pattern, geolocation") and when ("Use when building middleware... or any low-latency edge compute"), matching the score-3 anchor for both an explicit what and an explicit when.	3 / 3
Trigger Term Quality	Includes natural terms users would say ("middleware", "authentication checks", "A/B testing", "edge compute", "Netlify Edge Functions") with good coverage in an explicit "Use when..." clause, matching the score-3 anchor.	3 / 3
Distinctiveness Conflict Risk	The Netlify/Deno edge-vs-serverless framing carves a clear niche with distinct triggers unlikely to overlap with generic skills, matching the score-3 anchor rather than the score-2 "could still overlap" case.	3 / 3
	Total	12 / 12 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: openai/plugins
Path: plugins/netlify/skills/netlify-edge-functions/SKILL.md
Commit: 11c74d6

Reviewed: about 14 hours 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.