caching
HTTP caching, service workers, cache invalidation, and CDN configuration.
npx skills add a5c-ai/babysitter --skill caching --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Caching Skill Expert assistance for caching strategies. ## Capabilities - Configure HTTP caching - Implement service workers - Set up CDN caching - Handle cache invalidation - Design caching architecture ## HTTP Cache Headers ```typescript // Immutable assets headers['Cache-Control'] = 'public, max-age=31536000, immutable'; // Dynamic content headers['Cache-Control'] = 'private, no-cache, must-revalidate'; // Stale-while-revalidate headers['Cache-Control'] = 'public, max-age=60, stale-while-revalidate=300'; ``` ## Service Worker ```javascript self.addEventListener('fetch', (event) => { event.respondWith( caches.match(event.request).then((response) => { return response || fetch(event.request); }) ); }); ``` ## Target Processes - caching-strategy - performance-optimization - pwa-development
- Capabilities
- HTTP Cache Headers
- Service Worker
- Target Processes
What does the caching skill do?
HTTP caching, service workers, cache invalidation, and CDN configuration.
How do I install it?
Run `npx skills add a5c-ai/babysitter --skill caching --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From a5c-ai/babysitter, a repository with 1,642 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.