Back to catalog / Developer tools
Vercel Optimize: metrics first
An observability-first workflow that investigates only routes and files backed by production metrics.
Skills
This specialized workflow gathers Vercel production signals first, then uses deterministic gates to select only routes or files worth investigating; it does not begin with a repository-wide scan. It requires Vercel CLI 53+, a linked project, an authenticated session, and Node.js 20+; route-level metric recommendations also require Observability Plus. Support is strongest for Next.js, SvelteKit, and Nuxt, limited for Astro, and may stop by default for other frameworks. Confirm the exact account, team, and project scope, protect tokens, and expect only private per-run audit artifacts to be written.
Permissions
Prerequisites
- A linked Vercel app, authenticated CLI, and Node.js 20+; some route analysis requires Observability Plus.
Permissions
- Reads project configuration and metrics/usage from the authenticated account, inspects selected code, and may write private audit files. Confirm account/team/project and protect tokens.
Limitations
CLI versions, plan features, and framework support can change; verify them against the actual environment and docs.
Pinned upstream source
- Repository
- vercel-labs/agent-skills
- File path
- skills/vercel-optimize/SKILL.md
- Pinned commit
063bee94c3f4df8453406c830b0a7df0f2860278- Source checked
- 2026-10-14 · Reviewed against the pinned upstream source
Repository metrics
These values describe the upstream repository, not popularity or likes for an individual skill or playbook.
- Stars
- Not collected
- Forks
- Not collected
- Observed at
- Not collected
No metrics snapshot is available yet.
License: MIT
Compatible tools
Codex · Claude Code · Gemini CLI · GitHub Copilot · Cursor · Windsurf · Cline · OpenCode
Main topic
Take a coding Agent change from context to verification