Content
76%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 dense, actionable reference with excellent code coverage and clear sectioning. Its main weaknesses are duplicated guidance between 'Footguns' and 'Netlify house rules' and the absence of an explicit validation loop around the destructive purge workflow.
Suggestions
Remove or deduplicate the 'Netlify house rules' section, since its GET-only, Netlify-Vary query, and netlify-dev points already appear verbatim in 'Footguns'.
Add an explicit purge workflow with a validation checkpoint, e.g. purge → verify via Cache-Status on a deployed URL → retry with backoff on 429.
Consider splitting the @netlify/cache helper API (cacheHeaders/fetchWithCache/getCacheStatus/needsRevalidation) into a references file, keeping SKILL.md as a lean overview.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly lean, high-signal Netlify-specific detail, but the 'Netlify house rules' section repeats three points already covered in 'Footguns' (GET-only caching, Netlify-Vary query keying, netlify dev not emulating the cache), which is trimmable padding. | 4 / 5 |
Actionability | Copy-paste-ready TypeScript for caching, purgeCache (deployed + Lambda-compatible), the Cache API, cacheHeaders, fetchWithCache, needsRevalidation, plus a concrete curl for the direct purge API cover the common cases fully. | 5 / 5 |
Workflow Clarity | Content is organized by feature rather than as a sequenced workflow; the destructive purge operation has guard/rate-limit notes but no explicit validate→fix→retry checkpoint loop, leaving validation implicit. | 3 / 5 |
Progressive Disclosure | No bundle files exist and the single ~310-line file is organized into clear, navigable section headers; the cohesive reference is appropriately placed, though the detailed @netlify/cache API could justify a split. | 4 / 5 |
Total | 16 / 20 Passed |