agentleFS
Sign inStart free
robotostudiorobotostudio/turbo-start-sanity/.agents/skills/vercel-optimize/AGENTS.md

turbo-start-sanity / vercel-optimize

AGENTS.md185 starsChanged 2 months agoMITView 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. Do not use it for projects that are not deployed on Vercel, greenfield projects with no traffic, or general code review. The hard rules are in references/doctrine.md: observability first, deterministic gates, candidate-bound scope,…

We split this AGENTS.md into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when the user asks to optimize a Vercel project, reduce a Vercel bill, investigate slow or expensive routes, find caching …

    line 5
  2. Distinctive:

    Do not use it for projects that are not deployed on Vercel, greenfield projects with no traffic, or general code review.

    line 7
  3. Distinctive:

    Verify recommendations mechanically before rendering the report.

    line 23

≈ “Common” is an estimate: at least 1 in 5 of the 36,368 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
AGENTS.md

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.

Download now (ZIP)

Trending

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Aug 30: 0 new projectsWeek of Sep 6: 0 new projectsWeek of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projects
Aug 2026Sep 2026Oct 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free