AI SDK
vercel-labs/ai-facts
Answer questions about the AI SDK and help build AI-powered features.
Create and launch benchmark test projects to exercise vercel-plugin skill injection across realistic scenarios.
OfficialCustom licenceAuto-check passed
Install Benchmark Testing
$ npx skills add vercel/vercel-plugin --skill benchmark-testing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install vercel/vercel-plugin benchmark-testing --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/vercel/vercel-plugin.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/benchmark-testing .claude/skills/benchmark-testing && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "benchmark-testing" agent skill from https://github.com/vercel/vercel-plugin/tree/main/.claude/skills/benchmark-testing into .claude/skills/benchmark-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "benchmark-testing", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/vercel/vercel-plugin/tree/main/.claude/skills/benchmark-testingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add vercel/vercel-plugin --skill benchmark-testing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install vercel/vercel-plugin benchmark-testing --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vercel/vercel-plugin.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/benchmark-testing .agents/skills/benchmark-testing && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "benchmark-testing" agent skill from https://github.com/vercel/vercel-plugin/tree/main/.claude/skills/benchmark-testing into .agents/skills/benchmark-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "benchmark-testing", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add vercel/vercel-plugin --skill benchmark-testing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install vercel/vercel-plugin benchmark-testing --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vercel/vercel-plugin.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/benchmark-testing .cursor/skills/benchmark-testing && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "benchmark-testing" agent skill from https://github.com/vercel/vercel-plugin/tree/main/.claude/skills/benchmark-testing into .cursor/skills/benchmark-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "benchmark-testing", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/vercel/vercel-plugin.git --path .claude/skills/benchmark-testing--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add vercel/vercel-plugin --skill benchmark-testing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install vercel/vercel-plugin benchmark-testing --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vercel/vercel-plugin.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/benchmark-testing .gemini/skills/benchmark-testing && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "benchmark-testing" agent skill from https://github.com/vercel/vercel-plugin/tree/main/.claude/skills/benchmark-testing into .gemini/skills/benchmark-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "benchmark-testing", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install vercel/vercel-plugin benchmark-testingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add vercel/vercel-plugin --skill benchmark-testing -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/vercel/vercel-plugin.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/benchmark-testing .github/skills/benchmark-testing && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "benchmark-testing" agent skill from https://github.com/vercel/vercel-plugin/tree/main/.claude/skills/benchmark-testing into .github/skills/benchmark-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "benchmark-testing", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add vercel/vercel-plugin --skill benchmark-testing -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install vercel/vercel-plugin benchmark-testing --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vercel/vercel-plugin.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/benchmark-testing .opencode/skills/benchmark-testing && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "benchmark-testing" agent skill from https://github.com/vercel/vercel-plugin/tree/main/.claude/skills/benchmark-testing into .opencode/skills/benchmark-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "benchmark-testing", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
benchmark-testing- GitHub stars
- 301
- Token cost
- ~946 tokens
- SKILL.md length
- 374 words
- Files
- 1
- Skills in repo
- 38
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Create and launch benchmark test projects to exercise vercel-plugin skill injection across realistic scenarios.
- Works in 3 steps: Create test directories → Install the plugin in each directory → Launch Claude Code in WezTerm panes
- SKILL.md covers Workflow, Prompt Guidelines and Cleanup
- Calls npx
What it does
Benchmark Testing is an agent skill from vercel/vercel-plugin, published by the product's own GitHub organization. Create and launch benchmark test projects to exercise vercel-plugin skill injection across realistic scenarios. Sets up isolated directories, installs the plugin, and spawns WezTerm panes running Claude Code with crafted prompts.
Its SKILL.md is about 950 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It works with Vercel, Next.js and Vercel AI SDK. The repository describes itself as: Comprehensive Vercel ecosystem plugin — relational knowledge graph, skills for every major product, specialized agents, and Vercel conventions. Turns any AI agent into a Vercel…
Example prompts
- “/benchmark-testing”
Requirements
- Node.js
Workflow steps
3 steps, taken from the step headings in SKILL.md.
- Create test directories
- Install the plugin in each directory
- Launch Claude Code in WezTerm panes
What it can do on your machine
Read from SKILL.md and the folder at commit 82fa491. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
npx
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npx, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Benchmark Testing loads about 946 tokens when it runs. Until then it costs about 62 tokens; SKILL.md has 374 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 374 words (~946 tokens).
“Create isolated test projects that exercise vercel-plugin skill injection with realistic, technology-agnostic prompts.”
- name
- benchmark-testing
Files
Just SKILL.md in .claude/skills/benchmark-testing of vercel/vercel-plugin.
Open the folder on GitHubat commit 82fa491
Compare with similar skills
Benchmark Testing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Benchmark Testing this skillvercel/vercel-plugin | 301 | — | ~946 | Automated safety check: Pass | Custom licence | |
| AI SDKvercel-labs/ai-facts | 168 | 21 repos | ~1.2k | Automated safety check: Pass | None | |
| Workflowzoonk/zoonk | 157 | — | ~3.1k | Automated safety check: Pass | MIT | |
| Vercel Optimize Auditvercel-labs/agent-skills | 32k | 8 repos | ~4.3k | Automated safety check: Pass | None | |
| Vercel React Best Practicessanity-io/sanity | 6.4k | 130 repos | ~1.6k | Automated safety check: Pass | MIT | |
| Mem0 Provider for Vercel AI SDKmem0ai/mem0 | 67k | — | ~1.9k | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
Workflow
zoonk/zoonk
Creates durable, resumable workflows using Vercel's Workflow DevKit.
- Official
Vercel Optimize Audit
vercel-labs/agent-skills
Runs a metrics-first audit of a deployed Vercel project, gating investigations on real signals to produce ranked, citation-backed cost and performance recommendations.
- Official
Vercel React Best Practices
sanity-io/sanity
React and Next.js performance optimization guidelines from Vercel Engineering.
Mem0 Provider for Vercel AI SDK
mem0ai/mem0
Adds persistent memory to Vercel AI SDK apps with the Mem0 provider, using a wrapped model or standalone retrieve and store utilities.
AI Elements Chat Components
mweinbach/agent-coworker
Adds AI Elements components such as conversations, messages, tool displays and prompt inputs to a Next.js project that uses shadcn/ui.
More from vercel/vercel-plugin
All 38 skills in this repo- Official
Deployments Cicd
vercel/vercel-plugin
Vercel deployment and CI/CD expert guidance. An agent skill from vercel/vercel-plugin.
- Official
Plugin Audit
vercel/vercel-plugin
Audit vercel-plugin performance on real-world projects. An agent skill from vercel/vercel-plugin.
- Official
Vercel CLI
vercel/vercel-plugin
Vercel CLI expert guidance. An agent skill from vercel/vercel-plugin.
- Official
AI Gateway
vercel/vercel-plugin
Vercel AI Gateway guidance for setup, model discovery, authentication, routing, fallbacks, virtual models, evaluation models, BYOK, budgets, spend reporting, observability, compatible APIs, and…
- Official
Vercel Services
vercel/vercel-plugin
Configure and troubleshoot Vercel Services for multiple frontends and backends in one project.
- Official
Access Protected Vercel Deployment
vercel/vercel-plugin
Access and test Vercel deployments protected by Vercel Authentication, SSO, or Deployment Protection.
Related
Works with
Questions about Benchmark Testing
What does Benchmark Testing do?
Create and launch benchmark test projects to exercise vercel-plugin skill injection across realistic scenarios. Benchmark Testing is an agent skill from vercel/vercel-plugin, published by the product's own GitHub organization. Create and launch benchmark test projects to exercise vercel-plugin skill injection across realistic scenarios.
How do I install Benchmark Testing in Claude Code?
Run `npx skills add vercel/vercel-plugin --skill benchmark-testing -a claude-code`. Or copy the skill folder (.claude/skills/benchmark-testing in vercel/vercel-plugin) into .claude/skills/benchmark-testing in your project. Claude Code loads it when a task matches its description.
How do I install Benchmark Testing in Codex?
Run `npx skills add vercel/vercel-plugin --skill benchmark-testing -a codex`. Or copy the skill folder (.claude/skills/benchmark-testing in vercel/vercel-plugin) into .agents/skills/benchmark-testing in your project. Codex loads it when a task matches its description.
Can I use Benchmark Testing in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add vercel/vercel-plugin --skill benchmark-testing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/benchmark-testing, .gemini/skills/benchmark-testing, .github/skills/benchmark-testing and .opencode/skills/benchmark-testing in your project.
What does Benchmark Testing need to run?
Going by SKILL.md and its folder, Benchmark Testing needs the command-line tools its instructions call (npx). Our summary lists: Node.js.
Does Benchmark Testing access the network?
SKILL.md contains no URLs. Its commands use npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Benchmark Testing safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Benchmark Testing use?
Benchmark Testing has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Benchmark Testing use?
About 946 tokens (SKILL.md is roughly 3.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Benchmark Testing?
Skills that share tags, products or a category with Benchmark Testing: AI SDK (vercel-labs/ai-facts, 168 stars), Workflow (zoonk/zoonk, 157 stars), Vercel Optimize Audit (vercel-labs/agent-skills, 32k stars) and Vercel React Best Practices (sanity-io/sanity, 6.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Benchmark Testing?
vercel (a GitHub organization, an official publisher) maintains it in vercel/vercel-plugin, which has 301 GitHub stars. The repository holds 38 skills in this directory. The repository was last updated on October 6, 2026.
Source: vercel/vercel-plugin on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.