CtrlK
BlogDocsLog inGet started
Tessl Logo

netlify-caching

Cache dynamic and static responses on Netlify's CDN from Functions, Edge Functions, and proxies. Use when you add caching or cache-control headers to a function response, tune cache TTL or stale-while-revalidate, set up the durable cache, vary a cache key by query/header/cookie/country/language, purge or invalidate the cache by site or cache tag, use the programmatic Cache API (caches.open/match/put) or @netlify/cache helpers (fetchWithCache/cacheHeaders/getCacheStatus), speed up an expensive API call, add ISR or on-demand revalidation, or debug why a response is or isn't cached via the Cache-Status header.

72

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

76%Weight 40%Scale 1-5

Reviews 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.

DimensionReasoningScore

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

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A dense, well-targeted description that names concrete capabilities, natural trigger terms, an explicit 'Use when' clause, and a clear Netlify-specific niche. It earns top marks across all four dimensions.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'tune cache TTL or stale-while-revalidate', 'vary a cache key by query/header/cookie/country/language', 'purge or invalidate the cache', 'use the programmatic Cache API (caches.open/match/put)' — covering the surface comprehensively.

5 / 5

Completeness

Explicitly states what it does ('Cache dynamic and static responses on Netlify's CDN…') and when to use it ('Use when you add caching or cache-control headers…') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural user phrasing ('cache-control headers', 'cache TTL', 'purge or invalidate the cache', 'debug why a response is or isn't cached') alongside method/helper names and the Cache-Status header gives broad coverage with synonyms.

5 / 5

Distinctiveness Conflict Risk

Scoped tightly to Netlify's CDN/Vary/Cache API and @netlify/cache helpers, creating a clear niche with minimal overlap against other skills.

5 / 5

Total

20

/

20

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
netlify/context-and-tools
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.