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.
73
89%
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 niche (Netlify Edge Functions), lists concrete capabilities and use cases, and includes an explicit 'Use when' clause with natural trigger terms. It covers both the 'what' and 'when' comprehensively while remaining concise and distinctive from other potential skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and concepts: middleware, geolocation-based logic, request/response manipulation, authentication checks, A/B testing, Deno runtime, context.next() middleware pattern, and edge vs serverless decision guidance. | 3 / 3 |
Completeness | Clearly answers both 'what' (guide for writing Netlify Edge Functions, covers Deno runtime, context.next(), geolocation, edge vs serverless) and 'when' (explicit 'Use when' clause listing middleware, geolocation-based logic, request/response manipulation, authentication checks, A/B testing, low-latency edge compute). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'Netlify Edge Functions', 'middleware', 'geolocation', 'authentication', 'A/B testing', 'edge compute', 'Deno', 'serverless'. These are all terms a developer would naturally use when seeking this kind of help. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with 'Netlify Edge Functions' as a clear niche. The combination of Netlify-specific terminology, Deno runtime, and edge compute context makes it very unlikely to conflict with general serverless or other platform-specific skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
79%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, concise reference skill with excellent actionability—nearly every section has executable, copy-paste-ready code. Its main weaknesses are the lack of an end-to-end workflow with validation steps (e.g., local testing, deployment verification) and the absence of progressive disclosure references for advanced topics. Overall it serves well as a quick-reference guide for building Netlify Edge Functions.
Suggestions
Add a brief end-to-end workflow section: create file → test locally with `netlify dev` → deploy → verify, with explicit validation checkpoints at each step.
Include references to external resources or documentation for advanced topics like caching strategies, detailed Context API, and debugging edge functions (e.g., 'For full Context API: see Netlify Edge Functions docs').
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient throughout. It avoids explaining what edge functions are conceptually beyond a single introductory sentence, jumps straight into executable code, and uses tables for comparison/limits rather than prose. Every section earns its place. | 3 / 3 |
Actionability | Every section provides fully executable TypeScript code examples that are copy-paste ready. Config objects, middleware patterns, geolocation, environment variables, and module imports all have concrete, complete examples with specific syntax. | 3 / 3 |
Workflow Clarity | The skill covers multiple patterns clearly (middleware, geolocation, env vars) but lacks an explicit workflow sequence for creating and deploying an edge function end-to-end. There are no validation checkpoints—e.g., how to test locally, verify deployment, or handle common errors beyond the onError config option. | 2 / 3 |
Progressive Disclosure | The content is well-organized with clear section headers and appropriate use of tables, but it's a single monolithic file with no references to external files for deeper topics like import maps, advanced caching strategies, or detailed API reference. For its length (~100 lines) this is acceptable but could benefit from signposting to Netlify docs for advanced topics. | 2 / 3 |
Total | 10 / 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.