Content
82%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A high-quality, actionable reference with executable examples and strong decision guidance throughout. The main weakness is mild redundancy between the main body and the appended 'house rules' section, plus some reference material that could be externalized.
Suggestions
Collapse the trailing 'Netlify house rules (edge-functions)' section into the relevant earlier sections (or remove it) to eliminate the duplicated path-scoping, no-route, edge-vs-serverless, and cache guidance.
Consider extracting the Context object field list, config/routing property reference, and limits into a one-level-deep reference file (e.g. REFERENCE.md) linked from the overview, keeping SKILL.md as a leaner entry point.
Add a short explicit workflow or checklist for the common end-to-end flow (write handler → scope path → opt into cache if needed → netlify dev → deploy) with a verification checkpoint to lift workflow_clarity.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is a lean, reference-style document that mostly assumes Claude's competence, but the trailing 'Netlify house rules (edge-functions)' section restates path-scoping, no-route silent-fail, edge-vs-serverless, and cache both-or-neither points already covered above, adding redundancy that could be trimmed. | 4 / 5 |
Actionability | Fully executable, copy-paste-ready code covers the common cases — redirect, rewrite, middleware transform, body read with re-injected request, conditional requests, caching opt-in, and SSR (.tsx) — alongside specific CLI flags such as 'netlify dev', '--geo=mock', and '--edge-inspect'. | 5 / 5 |
Workflow Clarity | Decision guidance is clear (edge vs serverless, fail closed vs open, modern vs avoid) and troubleshooting callouts like 'check the route first' act as implicit checkpoints, but there is no explicit multi-step workflow with validation steps; no destructive or batch operations are present to invoke the cap. | 4 / 5 |
Progressive Disclosure | Single-file skill with no bundle directories and well-organized section headers providing easy navigation; however, API-reference material (Context fields, config properties, limits) is inlined rather than split into one-level-deep reference files, leaving minor organization gaps. | 4 / 5 |
Total | 17 / 20 Passed |