Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
vercel-labs avatar

Vercel Optimize

  • 41.5k installs
  • 29.5k repo stars
  • Updated July 24, 2026
  • vercel-labs/agent-skills

Vercel Optimize is a skill that audits Vercel deployments for performance and cost optimization using production metrics.

About

Skill for auditing Vercel-deployed projects with an observability-first approach. Collects production metrics, scans codebases, and produces ranked recommendations grounded in verified files and framework-aware Vercel documentation. Supports Next.js, SvelteKit, Nuxt, and Astro with limited Hono/Remix support.

  • Observability-first audits using production metrics before code investigation
  • Framework-specific optimization for Next.js, SvelteKit, Nuxt, and Astro
  • Cost analysis covering Function Invocations, Build Minutes, and Data Transfer

Vercel Optimize by the numbers

  • 41,528 all-time installs (skills.sh)
  • +4,055 installs in the week ending Jul 28, 2026 (Skillselion tracking)
  • Ranked #27 of 1,041 Cloud & Infrastructure skills by installs in the Skillselion catalog
  • Data as of Jul 28, 2026 (Skillselion catalog sync)
At a glance

vercel-optimize capabilities & compatibility

Capabilities
metrics collection · performance audit · cost analysis · framework specific optimization
Works with
vercel
Use cases
seo · web design
Runs
Hosted SaaS
npx skills add https://github.com/vercel-labs/agent-skills --skill vercel-optimize

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs41.5k
repo stars29.5k
Last updatedJuly 24, 2026
Repositoryvercel-labs/agent-skills

What it does

Audit Vercel deployments for performance and cost optimization using production metrics and codebase analysis.

Who is it for?

Developers maintaining Vercel-deployed applications who want to reduce costs and improve Core Web Vitals

Skip if: Greenfield projects without Vercel traffic, non-Vercel deployments, or general code review unrelated to Vercel billing or observability signals.

When should I use this skill?

The user asks to optimize a Vercel project, reduce a Vercel bill, find caching opportunities, cut function invocations, or produce a Vercel cost and performance report.

What you get

Metric-backed recommendations identify specific code and configuration changes to reduce costs and improve performance

  • optimization report
  • verified recommendations
  • signals.json audit bundle

By the numbers

  • Skill version 1.2.0 requiring Vercel CLI v53+
  • Default investigation gate budgets 6 code-scope candidates on a 14-day metrics window

Files

SKILL.mdMarkdownGitHub ↗

vercel-optimize

Cross-agent entry point for the Vercel Optimize skill. The full procedure is in SKILL.md.

Use this skill when the user asks to optimize a Vercel project, reduce a Vercel bill, investigate slow or expensive routes, find caching opportunities, reduce function invocations, or produce a Vercel cost/performance report.

Do not use it for projects that are not deployed on Vercel, greenfield projects with no traffic, or general code review.

Requirements

  • Node.js 20+
  • Vercel CLI with vercel metrics, vercel usage, vercel contract, and vercel api support; v53+ is this skill's compatibility floor
  • Authenticated Vercel CLI session
  • Linked Vercel project directory (vercel link) for route metrics. VERCEL_PROJECT_ID can help resolve project config, but it does not replace directory linkage for vercel metrics. The project must resolve to a CLI-safe team or personal scope so vercel metrics, vercel usage, and vercel contract all run against the same account.
  • Observability Plus for per-route metric analysis

Procedure

1. Read SKILL.md. 2. Collect Vercel signals before reading source files. 3. Gate candidates with deterministic scripts. 4. Investigate only files named by launched candidates. 5. Verify recommendations mechanically before rendering the report.

The hard rules are in references/doctrine.md: observability first, deterministic gates, candidate-bound scope, and version-aware citations.

Install

Preferred:

npx skills add vercel-labs/agent-skills --skill vercel-optimize

Manual project install:

mkdir -p .agents/skills
cp -R <agent-skills-repo>/skills/vercel-optimize .agents/skills/

Then add this to the project AGENTS.md:

When optimizing Vercel cost or performance, follow
`.agents/skills/vercel-optimize/SKILL.md` before proposing changes.
Collect Vercel metrics before reading source files.

Contributing to vercel-optimize

Keep changes small, metric-grounded, and fixture-tested. Runtime code lives in skills/vercel-optimize; tests and fixtures live in packages/vercel-optimize-tests so installed skills stay small.

Common changes

ChangeEditTest
Gatelib/gates/<id>.mjs, lib/gates/index.mjsnode --test packages/vercel-optimize-tests/test/*gate*.test.mjs
Scannerlib/scanners/<id>.mjs, lib/scanners/index.mjsScanner-specific test in packages/vercel-optimize-tests/test/
Citationreferences/docs-library.jsonnode skills/vercel-optimize/scripts/check-citations.mjs
Support topicreferences/support-topics/<id>.mdnode --test packages/vercel-optimize-tests/test/support-topics.test.mjs
Playbookreferences/playbooks/<profile>.md and selection matrix in references/scoring.mdnode --test packages/vercel-optimize-tests/test/support-topics.test.mjs packages/vercel-optimize-tests/test/investigation-brief.test.mjs
Renderer or verifierlib/render-report.mjs, lib/verify-claim.mjs, or related moduleFocused test plus full test suite

Generated docs:

node skills/vercel-optimize/scripts/build-docs.mjs
node skills/vercel-optimize/scripts/check-docs-fresh.mjs

Full test loop:

node --test packages/vercel-optimize-tests/test/*.test.mjs
node skills/vercel-optimize/scripts/check-docs-fresh.mjs
node skills/vercel-optimize/scripts/check-citations.mjs

Rules

  • No runtime dependencies. Scripts use Node.js 20+ built-ins and the Vercel CLI.
  • No recommendation without a Vercel metric signal, code evidence when code changes are proposed, and an allow-listed citation.
  • No invented URLs, exact savings projections, or version-mismatched framework APIs.
  • No internal repo paths, service names, customer names, or captured private output in fixtures.
  • Keep generated report copy customer-facing. Put debug details behind --debug-out.

Output contracts

Every JSON-emitting script mus

Related skills

How it compares

Use vercel-optimize for metric-backed Vercel cost and route audits; use general Next.js performance guides when the app is not deployed on Vercel or lacks production traffic signals.

FAQ

What prerequisites does vercel-optimize require?

vercel-optimize requires Node.js 20+, an authenticated Vercel CLI session, a linked project directory via vercel link, and Vercel CLI v53+ exposing vercel metrics, vercel usage, vercel contract, and vercel api commands.

Which frameworks does vercel-optimize fully support?

vercel-optimize provides strongest route mapping for Next.js App Router and Pages Router, plus supported SvelteKit and Nuxt audits. Astro support is limited; Hono, Remix, and unknown frameworks trigger a user prompt before limited platform-only audits.

How does vercel-optimize decide what code to inspect?

vercel-optimize runs collect-signals.mjs and gate-investigations.mjs first, producing signals.json and gate.json. Only metric-backed candidates in toLaunch get briefs; default budget selects 6 code-scope candidates before deep-dive and verification scripts run.

Cloud & Infrastructuredeploymonitoringinfra

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.