What problem does it solve? Debugging why Vercel-served pages are stale, missing the cache, or generating unexpected ISR bills is hard because cache behavior spans multiple layers (CDN, ISR, PPR) and the raw metrics lump different causes together. This Skill provides a systematic runbook for measuring cache hit rate, explaining per-request cache outcomes, and reducing ISR spend. ## Core Features & Use Cases - Cache hit rate analysis: Group vercel.request.count by cache_result, path_type, and route to find where misses concentrate, excluding BYPASS traffic for an accurate ratio. - Per-request cache reasoning: Interpret cacheReason values (cold, collapsed, draft_mode, stale_tag, stale_error, etc.) and ppr_state to explain exactly why a request was a MISS, STALE, or BYPASS. - ISR cost reduction: Measure write units, compute write utilization, identify hot cache tags with large blast radius, and shift from time-based to tag-based revalidation. - Use Case: Your Next.js site's ISR bill spiked. Use this Skill to group write units by cache_tags, discover a broad blogPost tag invalidated by a CMS webhook on every event, and replace it with granular blogPost:<id> tags. ## Quick Start Ask the assistant to analyze why your Vercel site's cache hit rate is low and which routes are driving ISR write costs.