

Caching and CDN Checkup
Your agent learns to check why pages load slowly or show old content and fix images and caching.
Your agent reads every image, the hosting and framework config, and every place the app stores data for reuse, then checks image format and size, how long files are cached, whether updates reach users after a deploy, whether per-user pages are wrongly cached for everyone, how cached data gets refreshed, and font and code loading. It fixes what is safe in code and config, starting with any signed-in page that is publicly cached. It tells you to run a browser performance audit on the live site, watch the network panel on reload, test from a phone on mobile data and confirm file names change after your next deploy.
Spend 100 tokens on Caching and CDN Checkup? You have 350 tokens.
You need 50 more tokens.
Get tokensBought. It's in your Library.
Token purchases are final. Tokens do not expire and can be used at any time.
Your first skill is on us. Every new account starts with 100 welcome tokens.
A look inside
## Standard
Eight checks, every time, across the whole repository. Each one gets a pass or fail with the file that proves it. Content that is the same for everyone is cached hard; content that differs per user is never cached for everyone; every cached item has a stated way to go fresh. Fix what is safe to fix in code and report what only the builder can measure on the deployed app.
## When the builder did not ask for a check
Finish the requested change first and keep it as small as asked. Then run the procedure below across the app as a read-only check. Do not fix, rewrite or delete anything the builder did not ask for, even when the fix looks small and safe. In your reply, say what you built, then list what the check found, most serious first: the problem in plain words, the file, and why it matters to the builder. Then ask the builder whether you should fix them, and stop. Fix only after the builder says go.
## Procedure
First read the whole repository: every image tag and image file with its pixel size, the hosting and framework config (headers, rewrites, build output), every route or page that sets cache headers, every place data is stored for reuse (in-memory maps, a cache store, fetch cache options, timed page regeneration, a service worker), font loading, and the page entry points. Then check all eight.
How to use it
- Download the file.
- Add it to whatever agent you build with.
- Ask your agent to run it.
Checkups also run on their own when your agent works on that layer. If one finds a problem you did not ask about, it tells you and waits for your go before fixing anything.
Learn the method free
This skill comes out of a free course in the community: The Foundation, Layer 10: Caching & CDN.
Packs that include this skill
All 13 Checkups, one for every layer of your app.
Version 1.0.0 · Last updated November 14, 2026