netlify-caching
Guide for controlling caching on Netlify's CDN. Use when configuring cache headers, setting up stale-while-revalidate, implementing on-demand cache purge, or understanding Netlify's CDN caching behavior. Covers Cache-Control, Netlify-CDN-Cache-Control, cache tags, durable cache, and framework-specific caching patterns.
76
93%
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 an excellent skill description that clearly defines its scope (Netlify CDN caching), lists specific capabilities and concepts covered, and includes an explicit 'Use when...' clause with natural trigger terms. It uses proper third-person voice and is concise yet comprehensive, making it easy for Claude to select this skill when appropriate and avoid it when not.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and concepts: configuring cache headers, setting up stale-while-revalidate, implementing on-demand cache purge, Cache-Control, Netlify-CDN-Cache-Control, cache tags, durable cache, and framework-specific caching patterns. | 3 / 3 |
Completeness | Clearly answers both 'what' (guide for controlling caching on Netlify's CDN, covers specific headers and patterns) and 'when' (explicit 'Use when...' clause listing configuring cache headers, setting up stale-while-revalidate, implementing on-demand cache purge, or understanding Netlify's CDN caching behavior). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms a user would use: 'cache headers', 'stale-while-revalidate', 'cache purge', 'CDN caching', 'Cache-Control', 'Netlify-CDN-Cache-Control', 'cache tags', 'durable cache', 'Netlify', 'CDN'. These are all terms developers would naturally use when asking about this topic. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: Netlify-specific CDN caching. The mention of Netlify-specific headers like 'Netlify-CDN-Cache-Control' and Netlify-specific concepts like 'durable cache' and 'cache tags' make it very unlikely to conflict with generic caching or other CDN skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality skill that efficiently covers Netlify CDN caching with concrete, executable examples and excellent organization. Its main weakness is the lack of explicit validation workflows — the debugging section exists but isn't woven into step-by-step processes for implementing or verifying caching behavior. Overall, it's concise, actionable, and well-structured.
Suggestions
Integrate the Cache-Status debugging info as an explicit validation step in a brief workflow, e.g., '1. Set headers → 2. Deploy → 3. Verify Cache-Status is HIT → 4. If MISS, check header precedence'
Add a verification step after purgeCache calls (e.g., confirm Cache-Status returns MISS on next request) to create a feedback loop for destructive cache operations
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every section is lean and information-dense. No unnecessary explanations of what CDNs or caching are. The table format for header comparison is efficient, and code examples are minimal but complete. | 3 / 3 |
Actionability | Provides fully executable code examples for every major pattern (CDN caching, stale-while-revalidate, durable cache, cache tags, purging, cache key variation, immutable assets). The netlify.toml and TypeScript snippets are copy-paste ready. | 3 / 3 |
Workflow Clarity | Individual patterns are clear, but there's no explicit workflow for implementing caching end-to-end (e.g., set headers → deploy → verify with Cache-Status header → iterate). The debugging section mentions Cache-Status but doesn't integrate it as a validation checkpoint in a workflow. For cache purge operations, there's no feedback loop for verifying purge success. | 2 / 3 |
Progressive Disclosure | For a standalone skill with no bundle files, the content is well-organized into logical sections with clear headers. The progression from defaults → headers → tags/purge → variation → framework-specific → debugging → constraints is natural and easy to navigate. Content length is appropriate for inline presentation. | 3 / 3 |
Total | 11 / 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.