Localized reading guide
vercel-optimizePurpose, usage and source
Use for Vercel cost and performance optimization on deployed projects, especially Next.js, SvelteKit, Nuxt, and limited Astro apps. Collect Vercel metrics, usage, project config, and code scan results first; investigate only metric-backed candidates; produce ranked recommendations grounded in verified files and version-aware Vercel/framework docs. Trigger for Vercel bill reduction, slow or expensive routes, caching opportunities, Function Invocations, Build Minutes, Fast Data Transfer, Core Web Vitals, Bot Management, Fluid compute, or cost breakdown requests.
Source retrieved:
- Source repository
- vercel-labs/agent-skills
- SKILL.md
skills/vercel-optimize/SKILL.md- Repository stars
- 33,269
- Repository updated
- 2026-10-29
- Categories
- Development
- Last collected
License: Unspecified
Workflow excerpts are reading aids, not executable instructions from Codez. No third-party Skill was run to produce this page.
The purpose and workflow passages below are upstream material, organized and translated for reading. They are distinct from the separately labeled Codez editorial analysis.
What this Skill does
Use for Vercel cost and performance optimization on deployed projects, especially Next.js, SvelteKit, Nuxt, and limited Astro apps. Collect Vercel metrics, usage, project config, and code scan results first; investigate only metric-backed candidates; produce ranked recommendations grounded in verified files and version-aware Vercel/framework docs. Trigger for Vercel bill reduction, slow or expensive routes, caching opportunities, Function Invocations, Build Minutes, Fast Data Transfer, Core Web Vitals, Bot Management, Fluid compute, or cost breakdown requests.
How the upstream workflow works
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.
Framework Support
The preflight reads package.json and sets expectations before metric fan-out. If unsupported, stop and ask before scanning or gating:
Run Directory
Use a fresh run directory for every audit. Do not reuse briefs, sub-agent outputs, or reports across runs.
Upstream passage · L53 ↗This project uses <framework>. Vercel Optimize supports metric-backed code recommendations for Next.js, SvelteKit, and Nuxt. Astro support is limited. For <framework>, I can still run a limited platform/scanner audit, but route-level Vercel metrics may not map back to source files.
Do you want me to continue with the limited audit, or stop here?Requirements and setup
Prerequisites
Vercel CLI v53+ with vercel metrics, vercel usage, vercel contract, and vercel api. Authenticated CLI session: vercel login.
Limits and quality checks
No separate limits passage was selected from this file. This does not mean the Skill is safe for every input or environment. Review the complete source and validate your own result.
Start with a safe trial
- Check the supported host and the repository installation instructions. Keep the Skill directory and its referenced scripts, assets and documentation together; SKILL.md alone may omit dependencies.
- Give the agent your real input, desired output and acceptance criteria. Invocation syntax and available tools depend on the host; this site does not assume a universal install command.
- Try the source workflow in a disposable project or on a copy. Review operations that change files, remote services or billable resources before allowing them.
- Validate the output against the source quality checks and your own requirements. A successful trigger or a high repository Star count does not establish a correct result.
Read further in the source
- Vercel Optimize
- Prerequisites
- Framework Support
- Run Directory
- 1. Collect, scan, and merge signals
- 1.1 Stop on blockers
- 2. Gate candidates
- 2.1 Ask about audit scope when needed
- 2.2 Deep-dive and reconcile
- 2.3 Generate briefs and investigate
- 2.4 Collect outputs
- 3. Verify recommendations
- 4. Render report and final message
- Recommendation Rules
- Scanner Rules
- Final Customer Terms
- Failure Copy
Related Skills
Translation and scope
This reading guide selects passages from the pinned upstream SKILL.md. Translation is assisted. It is not a complete manual or a claim of tested compatibility. Read the original and its referenced files before use.
This introduction refers to the pinned version below; current repository activity and collection time are shown separately.
- Pinned source
- Read the original ↗
- Source retrieved
- Source commit
1a2c79d4e6c4a2283dc2c614b6538cbe1ed5ca62- Source SHA-256
95ae2683b30d892d165af92a350c5628b68106f395a59b448857b654e306ed91