Vercel Optimize

This is a metrics-first auditor for Vercel bills and slow routes. It pulls real production data from Vercel's Observability Plus API, gates what to investigate using actual invocation counts and P95 latency, then scans only the code files that correspond to expensive or slow candidates. The pipeline is rigid by design: no guessing at optimizations until signals.json exists, no repo-wide grep, and every recommendation must cite version-aware framework docs from a frozen library. It handles Next.js App and Pages Router best, supports SvelteKit and Nuxt with weaker route mapping, and blocks or warns on unsupported frameworks. You'll want CLI v53+, a linked project directory, and Observability Plus enabled to get route-level recommendations instead of a code-only fallback audit.

skills.sh installs: 126K
GitHub stars: 33.8K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add vercel-labs/agent-skills --skill vercel-optimize --agent claude-code

Installs into .claude/skills of the current project.

Files

Vercel Optimize

Run an observability-first Vercel optimization audit. Do not inspect source files until signals.json exists and a deterministic gate points to a route, file, or project setting.

Core doctrine: read references/doctrine.md if any rule is unclear.

Metrics first. Recommendations start from Vercel production signals, not repo-wide grep.
Deterministic gates. scripts/gate-investigations.mjs decides what deserves investigation.
Candidate-bound scope. Read only files named by a candidate or a route-local import chain.
Version-aware citations. Use only references/docs-library.json; invalid or version-mismatched citations are stripped.
Customer copy. Read references/voice.md before writing report text or chat output.