caching SKILL.md skillA
caching from zebbern/claude-code-guide is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add zebbern/claude-code-guide/caching@git:20260531.164971dPins git:20260531.164971d in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- zebbern/claude-code-guide
- Path
skills/caching/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260531.164971d, committed May 31, 2026
- Size
- 6,223 bytes
- Repository stars
- 4,666
- License
- MIT
Caching strategies — invalidation, TTL guidelines, cache keys, cache layers, and when not to cache. Use when implementing or reviewing caching logic.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
## WHEN_TO_USE - When implementing a cache layer (in-memory, Redis, CDN) for an API or service. - When choosing TTL values or invalidation strategies for cached data. - When designing cache key schemas to avoid collisions or stale-data bugs. - When reviewing code that reads from or writes to any cache. - When debugging stale data, cache stampedes, or inconsistent responses. - When configuring TanStack Query `staleTime`/`gcTime` for client-side caching. ## INVALIDATION - [P0-MUST] Define an invalidation strategy for every cache. Stale data is worse than no cache. - [P0-MUST] Invalidate caches when the underlying data changes — do not rely solely on TTL expiry. - [P1-SHOULD] Prefer event-driven invalidation (on write/update/delete) over time-based expiry alone. - [P1-SHOULD] Use cache versioning (include a version key) when data schemas change. ## TTL_GUIDELINES - [P1-SHOULD] Set TTLs based on data volatility: static config (hours/days), user profiles (minutes), real-time data (seconds or no cache). - [P1-SHOULD] Use stale-while-revalidate: serve stale data immediately while refreshing in the background. - [P2-MAY] Use shorter TTLs in development and longer TTLs in production. …
Read the whole file at its exact version.
How to install
mdr add zebbern/claude-code-guide/caching@sha256:0d4edff8dcc7c777The line at the top of this page pins the label git:20260531.164971d, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_vs2mxrsktr6gjspu)
5 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on May 31, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (6223 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
zebbern/claude-code-guide · 4,666 stars · license MIT · pushed 2026-10-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_vs2mxrsktr6gjspu GET https://markdownregistry.com/api/v1/resolve?ref=zebbern/claude-code-guide/caching GET https://markdownregistry.com/api/v1/blob/0d4edff8dcc7c7778e4977c0b362a58987194e04c106995c81f73f9a5456709e
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from zebbern/claude-code-guide
Every file in zebbern/claude-code-guide