Dense, high-signal reference that assumes Claude's competence (defines no basic concepts like middleware/cookies/redirects) and contains no opinion fluff; gotcha paragraphs are long but every clause is specific, non-obvious Netlify knowledge. Not score 2 because there is no unnecessary padding, only detail that earns its place.

Abundant executable TypeScript and TOML examples (syntax, full config object, middleware, geolocation, cookies, env vars, import map) that are complete and copy-paste ready. Not score 2 because the code is real and complete, not pseudocode.

The multi-step processes present (chaining order as a numbered 1–3 sequence, the edge-before-redirects lifecycle) are fully specified, and debugging guidance ('first confirm it declares a path') is provided; no destructive/batch ops exist so the missing-validation cap does not apply. Not score 2 because the sequences have no gaps.

Well-organized into clear titled sections with tables and code (not a monolithic wall), easy header navigation, no nested references, and one clearly-signaled one-level cross-reference (the sibling netlify-frameworks skill); for a focused self-contained domain skill, keeping content in one well-structured file is appropriate. Not score 2 because organization is strong and the reference is clearly signaled.

Lists multiple concrete capabilities — 'building middleware, geolocation-based logic, request/response manipulation, authentication checks, A/B testing' — matching the multiple-specific-actions anchor; not score 2 because the actions are comprehensive rather than partial.

Explicitly answers both: 'Guide for writing Netlify Edge Functions' (what) and 'Use when building middleware, geolocation-based logic...' (when, with an explicit trigger clause); not score 2 because the 'when' is explicit, not merely implied.

Natural developer terms a user would say — 'middleware', 'geolocation', 'authentication checks', 'A/B testing', 'edge vs serverless', 'Netlify Edge Functions' — give good coverage; not score 2 because common variations are present, not just a single keyword.

'Netlify Edge Functions' with an explicit 'edge vs serverless' distinction carves a clear niche unlikely to fire for the wrong skill; not score 2 because the domain and triggers are distinct rather than merely 'somewhat specific'.