floatboat
Open navigation menu

Vercel Optimize by Vercel Labs

Use Vercel Optimize by Vercel Labs to investigate cost and performance in a deployed Vercel project. Start with usage and production signals, identify routes or settings supported by evidence, and review prioritized recommendations tied to the project’s framework, source files, and available observability access.

Install and get started

Choose your agent to see how to get started. In Floatboat, copy a request that asks the agent to read the original instructions. Other options show the Skill installation command or the publisher’s native setup steps.

Choose an agent

Start in Floatboat

Copy the request into a Floatboat conversation

Read the original Vercel Optimize instructions at https://github.com/vercel-labs/agent-skills/blob/main/skills/vercel-optimize/SKILL.md. Explain its purpose, required tools, and installation options, then help me use it.

Let the agent read the original instructions and check how to use them in your environment.

Download Floatboat ↗

Try this request

Investigate last month's Vercel function-cost increase. Confirm the project scope, use available metrics, and rank only evidence-backed opportunities.

About Vercel Optimize

Vercel Optimize is a Vercel Labs Skill for investigating deployed-project cost and performance using production evidence. Its bundled scripts collect signals and select candidates before the agent reads the related source files. This keeps recommendations tied to observed routes and settings rather than a broad search for suspicious code. The source describes framework-specific support for Next.js, SvelteKit, Nuxt, and limited Astro use. It requires a linked project, suitable CLI and Node versions, and the intended account scope; route-level metric-backed advice also needs Observability Plus. The workflow produces ranked recommendations, whose effects should be checked against the same workload after any implementation.

Use Cases for Vercel Optimize

Explore optimization questions backed by a deployed project’s usage and route signals. Investigate unexpected function consumption, a slow or expensive route, or a proposed cache change, and use the available evidence to decide which source files and settings deserve closer inspection.

Function usage rose unexpectedly

Check usage and route metrics before attributing the bill change to a particular endpoint or cache setting.

One page seems expensive or slow

Let measured route signals identify which source files and settings deserve investigation.

A cache change is being proposed

Confirm the current hit pattern and framework behavior before recommending ISR, middleware, or response-cache changes.

How to Audit a Project with Vercel Optimize

Confirm the linked project, account scope, and observability prerequisites before collecting data. Let the bundled workflow select evidence-backed candidates, inspect only the relevant files, and review ranked recommendations with their supporting signals and any gaps in the available data.

  1. 01

    Check scope and prerequisites

    Confirm the linked Vercel project, account, and framework. Check the source’s CLI, Node, and observability requirements before collecting signals.

  2. 02

    Collect and select evidence

    Use the bundled collection workflow to gather production signals. Let its gate identify candidates before investigating source files.

  3. 03

    Review ranked recommendations

    Inspect only the selected routes or settings with the agent. Review evidence, framework-version fit, and a validation plan for each proposed change.

Explore More Agent Skills

Read another Skill guide and check its original source before using it.

Vercel Optimize FAQ

Does Vercel Optimize scan the entire repository first?
No. Its documented doctrine collects production signals first and gates code investigation to metric-backed candidates.
Can it estimate savings without Observability Plus?
Route-level metric-backed recommendations require the stated observability access. Missing data should be reported as a limitation, not replaced with invented precision.
Which frameworks does it address?
The source lists strong support for Next.js, support for SvelteKit and Nuxt, limited Astro support, and a restricted path for others. Check the current source before running an audit.
Is it only a prose checklist?
No. The Skill bundles scripts and references for signal collection, gating, and report generation. Those still depend on authorized Vercel access.
What evidence is useful before starting an optimization review?
Provide the affected routes, a representative time window, and available latency, error, or resource signals. A concrete baseline makes recommendations more useful than a broad request to reduce every possible cost.
How should I validate a proposed optimization?
Compare the same workload before and after the change and check correctness as well as performance. A lower resource figure is not an improvement if errors increase or the user’s task stops working.
What prerequisites should I check before running Vercel Optimize?
The source lists Vercel CLI v53+, Node.js 20+, an authenticated CLI, and a linked project with the intended account scope. Route-level metric-backed recommendations require Observability Plus. Confirm the current source requirements before running its scripts.