Content
78%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-density, highly actionable reference: every mechanism has executable code and precise limits/footguns, and the Cache-Status debugging section supplies a real verification loop. The main weaknesses are the absence of any progressive disclosure (all reference material inline in one long file) and a duplicated trailing house-rules section that pads the token budget.
Suggestions
Split reference-heavy sections (the Cache API method surface, the @netlify/cache module docs, and the purge REST API details) into files under references/ and keep SKILL.md as a concise overview with clearly signaled one-level-deep pointers.
Remove the duplicated 'house rules' footer (or the equivalent Footguns bullets it repeats) so each fact appears once, cutting ~20 lines of redundant tokens.
Add a short post-purge verification step to the invalidation workflow (e.g. re-request the URL and confirm Cache-Status shows fwd=miss) to close the feedback loop for this batch operation.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and fact-only ('Only GET is cached', 'Limits per invocation: 100 lookups, 20 insertions/deletions') with no explanations of concepts Claude already knows — mostly efficient. However, the appended 'house rules' section duplicates the Footguns bullets verbatim (query-string cache key, netlify dev, purge credentials), and merge-artifact comments add trailing padding. Fits 4 (minor trimming possible), not 5 (the duplication is a real, if bounded, inefficiency). | 4 / 5 |
Actionability | Every operation ships copy-paste-ready code: a complete Function response with the header, purgeCache for both the default and Lambda-compatible signatures with token handling, an executable curl for the purge API, and working cacheHeaders/fetchWithCache/getCacheStatus/needsRevalidation examples covering the common cases. Not 4: the examples are complete and cover common cases, including edge paths like the local-dev 'caches' import workaround. | 5 / 5 |
Workflow Clarity | 'Footguns (read first)' provides pre-flight checkpoints and the Cache-Status section gives an explicit verification loop ('Check it on a deployed URL' with hit/miss/stale values to look for). Not 5: purge — a site-wide batch/destructive operation — lacks an explicit post-purge verification step. Not 3: verification guidance for caching behavior is present and explicit, not missing. | 4 / 5 |
Progressive Disclosure | There are no bundle files at all — the full caches API surface, the @netlify/cache module reference, and the purge REST API details are all inlined in one ~310-line SKILL.md. Section headers are clear (better than 2), but API-reference material that clearly belongs in separate reference files is inline, matching the 3 anchor ('content that should be separate is inline') rather than 4. | 3 / 5 |
Total | 16 / 20 Passed |