
Vercel Optimize
SkillVercel's official cost and performance skill: gathers production metrics, usage and project config, investigates only the routes and files the metrics point to, and returns ranked, doc-backed recommendations. Supports Next.js, SvelteKit and Nuxt; needs Vercel CLI v53+ logged in and linked.
vercel-optimize
Optimize cost and performance for supported projects on Vercel.
This skill uses Vercel metrics to find high-impact improvements in your app. Every recommendation is backed by observed data, scoped code evidence, and version-aware docs.
Install
Install just this skill:
npx skills add vercel-labs/agent-skills --skill vercel-optimize
Manual install: copy skills/vercel-optimize into .agents/skills/vercel-optimize and reference SKILL.md from your project AGENTS.md.
Requirements
- Node.js 20+
- Vercel CLI with
vercel metrics,vercel usage,vercel contract, andvercel apisupport (npm i -g vercel@latest). The skill enforces v53+ as its compatibility floor. - Authenticated Vercel CLI session (
vercel login) - Linked Vercel project directory (
vercel link) for route metrics.VERCEL_PROJECT_IDcan resolve project config, but it does not replace directory linkage forvercel metrics. The project must resolve to a CLI-safe team or personal scope sovercel metrics,vercel usage, andvercel contractall run against the same account. - Observability Plus for metric-backed route ranking
- Code-backed recommendation coverage is strongest for Next.js and SvelteKit, supported for Nuxt route mapping with generic checks, and limited for Astro. Hono, Remix, and unknown frameworks pause up front.
If route-level metrics are unavailable, the skill pauses before scanner-only mode. Scanner-only can catch traffic-independent code issues, but it cannot rank hot routes or prove cost impact.
Use
From the Vercel project directory, ask your coding agent:
optimize this Vercel project
The agent should collect metrics first. If it starts by reading source files or guessing from vercel.json, the skill was not loaded correctly.
Roadmap
| Attribute | Status |
|---|---|
| Route-level Vercel Function invocations, duration, TTFB, and cold starts | Supported |
| Vercel Function CPU, memory, and GB-hours | Supported |
| Request volume, cache hit rate, HTTP status, and method distribution | Supported |
| Fast Data Transfer and bot traffic patterns | Supported |
| ISR reads, writes, and over-revalidation | Supported |
| Routing Middleware volume and duration | Supported |
| External API latency, volume, and transfer bytes | Supported |
| Core Web Vitals from Speed Insights | Supported |
| Image Optimization usage, source hosts, and source bytes | Supported |
| Build Minutes fan-out | Supported |
| Usage spikes by billing service | Supported |
| Bot Protection and BotID configuration | Supported |
| Fluid Compute configuration and compute signals | Supported |
| Region pinning and project configuration mismatches | Supported |
| Observability Events cost attribution | Supported |
| Route-to-file recommendations for Next.js and SvelteKit | Supported |
| Nuxt route mapping with generic/platform checks | Supported |
| Generic route mapping and platform checks for Astro | Supported |
| Hono route-to-file mapping | Planned |
| Remix route-to-file mapping | Planned |
| AI Gateway usage and cost optimization | Planned |
| Sandbox usage and cost optimization | Planned |
| Blob, Edge Config, Runtime Cache, Workflows, Queues, Flags, and Microfrontends billing dimensions | Planned |
What You Get
- Ranked recommendations tied to observed Vercel metrics
- Specific route and file references when source changes are justified
- Before/after code for ready recommendations
- Citations from a curated, version-aware documentation allow-list
- Held-back findings when evidence is real but not strong enough for a recommendation
- A concise final message plus a full Markdown report
Trust Model
- Metrics come first. Code investigation starts only after signals are collected.
- Gates are deterministic JavaScript thresholds. No LLM decides whether a metric qualifies.
- Citations are allow-listed. Unknown URLs and version-mismatched framework docs are stripped.
- Project config contradictions are rejected. For example, the verifier blocks "enable Fluid Compute" when Fluid Compute is already on.
- Cost impact uses magnitude framing, not invented exact savings.
Contributing
See CONTRIBUTING.md. New gates, scanners, playbooks, citations, and sanitizers need fixture coverage in packages/vercel-optimize-tests.
License
MIT
관련 리소스

Vercel Plugin
PluginVercel's official plugin: a knowledge graph of the Vercel ecosystem, dozens of skills, expert subagents for deployment and performance, and commands for deploys, env vars and project status, covering Next.js, the AI SDK, storage and CI/CD. Needs Node.js 18+ and Bun; telemetry is opt-out.
vercel/vercel-plugin306
Vercel React Best Practices
SkillReact and Next.js performance rules from Vercel's engineering team: 70 rules ranked by impact covering request waterfalls, bundle size, server performance and re-renders, for writing, reviewing and refactoring. Maintained by Vercel.
vercel-labs/agent-skills32.5k
Next.js Skills
PluginOfficial Next.js plugin shipped in the vercel/next.js repo: guides enabling and tuning Cache Components and Partial Prefetching, and verifies changes on a running dev server with the Next.js MCP and agent-browser.
vercel/next.js143k
Deploy to Vercel
SkillVercel's official deployment skill: checks the git remote, project link and CLI login, then deploys a preview (default) or production via git push or vercel deploy. When login isn't possible in a sandbox, it can create a claimable preview link.
vercel-labs/agent-skills32.5k
Vercel CLI
CLIVercel's official CLI: deploy frontend and full-stack projects with one command and manage preview environments, environment variables, domains and logs. Requires a Vercel account (free tier available).
vercel/vercel16.4k
next-dev-loop
SkillAfter code changes, has the agent check routes, errors and page behavior in the running Next.js app via /_next/mcp and agent-browser to confirm the change really works. Maintained by Next.js; needs Next.js 16.3+ (Turbopack) and agent-browser.
vercel/next.js143k