Setting the file. One moment.
Subchapter 7.77
AGENTS.mdMarkdown2 KBView on GitHub
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.
Also bundled
AGENTSDo not use it for projects that are not deployed on Vercel, greenfield projects with no traffic, or general code review.
vercel metrics, vercel usage, vercel contract, and vercel api support; v53+ is this skill’s compatibility floorvercel 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.The hard rules are in references/doctrine.md: observability first, deterministic gates, candidate-bound scope, and version-aware citations.
Preferred:
npx skills add vercel-labs/agent-skills --skill vercel-optimizeManual 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.