What problem does it solve? Vercel bills and slow routes are hard to diagnose because cost and latency signals live in observability dashboards while fixes live in source code. This Skill connects the two: it collects Vercel metrics, usage, and project config first, then investigates only the routes and files the metrics actually implicate, producing verified recommendations instead of guesswork. ## Core Features & Use Cases - Metric-first auditing: Collects route-level function invocations, duration, cold starts, cache hit rates, Core Web Vitals, ISR reads/writes, and billing usage via the Vercel CLI before reading any source files. - Deterministic gating: Pure-JavaScript threshold gates (no LLM judgment) decide which candidates deserve investigation, with a default budget of 6 code-scope candidates and an interactive scope checkpoint. - Verified recommendations: Every recommendation is checked against real files, an allow-listed version-aware documentation library, and project config, then rendered into a ranked Markdown report with before/after code. - Use Case: A team notices their Vercel bill doubled. They run the audit from the linked project directory; the Skill finds an uncached high-traffic route and an over-aggressive ISR revalidate interval, then delivers cited, code-backed fixes. ## Quick Start From a linked Vercel project directory, ask your coding agent to optimize this Vercel project and reduce its bill.
