What problem does it solve? Vercel bills and slow routes are hard to diagnose without connecting production metrics to source code. This Skill runs an observability-first audit that collects Vercel metrics, usage, and project config before reading any source files, so every recommendation is grounded in real traffic data rather than guesswork. ## Core Features & Use Cases - Metric-backed investigation: Collects route-level function invocations, duration, cache hit rates, Core Web Vitals, and billing usage via the Vercel CLI, then applies deterministic gates to decide what deserves investigation. - Verified recommendations: Produces ranked recommendations with before/after code, file and line citations, and version-aware documentation links from a curated allow-list; unsafe or unverifiable suggestions are withheld. - Framework-aware analysis: Supports Next.js (App and Pages Router), SvelteKit, and Nuxt with route-to-file mapping, plus limited Astro support. - Use Case: Ask your agent to "optimize this Vercel project" from a linked project directory, and receive a Markdown report ranking issues like uncached hot routes, cold starts, ISR over-revalidation, and Build Minutes fan-out. ## Quick Start From a linked Vercel project directory, ask your coding agent to optimize this Vercel project and reduce its bill.
