What problem does it solve? Debugging why Vercel-served pages are stale, uncached, or expensive is hard because caching spans multiple layers (CDN, ISR, PPR) with opaque outcomes. This Skill turns raw cache signals into a concrete diagnosis of hit rate, revalidation cost, and bypass causes. ## Core Features & Use Cases - Cache hit rate analysis: Measure cacheable traffic with vercel metrics grouped by cache_result, then drill into MISS buckets by path type and route. - ISR cost investigation: Quantify read/write units, compute write utilization, and find hot cache tags with large blast radius driving revalidation spend. - Per-request debugging: Interpret x-vercel-cache status and the nine cacheReason values (cold, collapsed, draft_mode, stale_tag, etc.) via curl and vercel logs. - Use Case: Your ISR bill spiked after a CMS webhook change. Use this Skill to group write units by cache_tags, discover a broad blogPost tag invalidating thousands of pages, and switch to granular blogPost:<id> tags. ## Quick Start Ask the agent to analyze why your Vercel site's cache hit rate dropped and which routes are driving ISR write costs.