Index of every page on this site: llms.txt
All skills
robotostudio avatar

/vercel-optimize

@c0b29e4
Run it yourself

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.

  • 156 files
  • 828.6 KB
  • Updated 5 months ago
  • GitHub
Use this Skill: https://skilld.dev/gh/robotostudio/turbo-start-sanity/vercel-optimize

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

AGENTS.md

≈491 tokens on demand. Your agent reads this file only when SKILL.md points to it.

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.

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at c0b29e4. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 5 months ago
metadata
{
  "version": "1.2.0"
}

README badge

README badge for robotostudio/turbo-start-sanity/vercel-optimize