vercel-labs/agent-skills / skills/vercel-optimize
vercel-optimize
VerifiedUse 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.
references/voice.md
View on GitHub# Voice
Use Vercel's customer-facing voice: sharp teammate, clear, competent, no fluff.
Write for a user deciding what to fix next. Lead with the observed signal, the specific change, and how to verify it. Do not explain the skill's internals unless the user asked for debug details.
## Rules
- Use plain words. Prefer "use" over "leverage," "reduce" over "optimize" when the action is specific.
- Be direct. No apologetic preambles, no marketing language, no "For context" wrap-up paragraphs.
- Keep every recommendation tied to a route, file, metric, or project setting.
- Use observed numbers only. Never invent savings, traffic, latency, or percentages.
- Use cost magnitude language, not precise savings: "hundreds of dollars per month at current traffic," not "$340/mo."
- Use precise performance language when measured: "95th percentile duration is 1,240ms."
- Frame prerequisites as engineering constraints, not upsells. Explain the decision impact: what the missing data prevents, what the limited fallback can still do, and what the user should choose next.
- Use short bullets and tables. Avoid long paragraphs in reports and final chat messages.
- Write full sentences with punctuation in reports.
## Avoid
- `seamlessly`, `effortlessly`, `powerful`, `robust`, `leverage`, `unleash`, `blazing`, `lightning-fast`, `turnkey`, `holistic`, `best-in-class`, `next-generation`, `cutting-edge`, `world-class`, `streamline`, `elevate`, `harness`, `crafted`, `myriad`, `plethora`, `empower`, `utilize`
- Filler adverbs: `just`, `simply`, `actually`
- Hedge starts: `Consider`, `You may want to`, `It is important to note`
- Rhetorical reframes: `It's not X, it's Y`
- Unicode arrows in prose: `->`, `→`, `⇒`
- Internal process terms in customer output: `sub-agent`, `abstention`, `abstained`, `passRate`, `quality score`, `sanitizer`
Use customer-facing replacements:
| Internal | Customer-facing |
|---|---|
| `sub-agent` | `investigation` |
| `abstained` | `found no supported change` |
| `abstention` | `investigated, no change recommended` |
| `passRate` | `verification result` |
| `quality score` | `review result` |
| `inv` | `function invocations` or `requests`, based on the metric |
| `p95` | `95th percentile` |
| `perf` | `performance` |
| `CWV` | `Core Web Vitals` |
## Product names
Use these spellings:
| Right | Wrong |
|---|---|
| `Observability Plus` | `OPlus`, `Oplus`, `O11y Plus`, `o11y+`, `obs+` |
| `Vercel Functions` | `serverless functions` when referring to Vercel's product |
| `fluid compute` mid-sentence | `Fluid Compute` mid-sentence |
| `BotID` | `Bot ID`, `botID` |
| `AI Gateway` | `Vercel AI Gateway`, `ai gateway` |
| `AI SDK` | `Vercel AI SDK` |
| `Edge Config` | `EdgeConfig` |
| `Routing Middleware` | `Edge Middleware` |
| `Web Analytics` | `Vercel Analytics` |
| `Hobby`, `Pro`, `Enterprise` | `hobby`, `pro`, `enterprise` as plan names |
Mirror billing names from the user's dashboard. If a dashboard still says `Edge Requests`, use `Edge Requests`; do not rename it.
## Recommendation shape
| Field | Pattern |
|---|---|
| `what` | Verb + change + scope. Example: `Add shared caching to /api/products`. |
| `why` | State the metric and code evidence. Example: `The route handled 1,200,000 requests with a 0% cache hit rate; src/app/api/products/route.ts returns no Cache-Control header.` |
| `fix` | Numbered steps. Start each step with a verb. |
| `verify` | Tell the user exactly which metric or command to re-check. |
Good:
> Add `Cache-Control: s-maxage=300, stale-while-revalidate=86400` to `/api/products`. The route handled 1,200,000 GET requests with a 0% cache hit rate.
Bad:
> Consider leveraging a robust caching strategy to unlock better performance.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |