Skills Agentes

Benchmark Testing

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.

Oficial
Estrellas
263

en todo el repo

Actividad
33

0–100, la ruta de este skill

Actualizado
hace 5 meses

último commit aquí

Commits
0

últimos 90 días

Contexto
947 tok

57 tok en reposo

Paquete
1 archivo

4 KB

Instalar

Funciona con cualquier agente que lea SKILL.md

npx -y skills add vercel/vercel-plugin --skill benchmark-testing --agent claude-code

Se instala solo en este repositorio.

Este skill makes network requests, reads environment config.

SKILL.md

En inglés

Benchmark Testing

Create isolated test projects that exercise vercel-plugin skill injection with realistic, technology-agnostic prompts.

Workflow

1. Create test directories

BASE=~/dev/vercel-plugin-testing
mkdir -p "$BASE"/{01-slug,02-slug,...}

2. Install the plugin in each directory

for dir in "$BASE"/*/; do
  echo "=== $(basename "$dir") ==="
  cd "$dir" && npx add-plugin https://github.com/vercel/vercel-plugin -s project -y 2>&1 | tail -1
done

This creates .claude/settings.json with enabledPlugins in each directory.

3. Launch Claude Code in WezTerm panes

Critical details that must all be followed:

  • Use --cwd <absolute-path> to set the working directory
  • Use unset CLAUDECODE before x to avoid nested-session errors
  • Use --settings .claude/settings.json (not --settings project) to load the plugin
  • Use double quotes on the outer -ic string, single quotes around the prompt
  • Wait 10 seconds between each launch to avoid overwhelming the system
  • Always use spawn (new tabs) — split-pane runs out of space after ~4 panes

Working command template:

wezterm cli spawn --cwd /absolute/path/to/test-dir -- /bin/zsh -ic "unset CLAUDECODE; x 'YOUR PROMPT HERE. Link the project to my vercel-labs team so we can deploy it later.' --settings .claude/settings.json; exec zsh"

Prompt Guidelines

  • Never name specific technologies (no "Next.js", "Stripe", "Vercel KV", etc.)
  • Describe the product and features — let the plugin infer which skills to inject
  • Make prompts ambitious and multi-featured to exercise multiple skill triggers
  • Always append: "Link the project to my vercel-labs team so we can deploy it later."

Example prompts

Slug Prompt Expected skills
recipe-platform "Build a recipe sharing platform where users sign up, upload photos of their dishes, write ingredients and steps, and browse a feed with infinite scroll..." auth, vercel-storage, nextjs
trivia-game "Create a multiplayer trivia game where players join a room with a 6-letter code, answer questions in real-time with a 15-second countdown..." vercel-storage, nextjs
code-review-bot "Build an AI-powered code review dashboard with webhook API routes, LLM streaming analysis, and stats over time..." ai-sdk, nextjs
conference-tickets "Create a conference ticketing system with tiered checkout, QR code emails, admin panel, and payment webhook handling..." payments, email, auth
content-aggregator "Build a content aggregator with hourly scheduled RSS fetching, LLM summaries, category filters, and bookmarks..." cron-jobs, ai-sdk
finance-tracker "Build a personal finance tracker with bank connection, spending charts, and weekly email digest via scheduled job..." cron-jobs, email
multi-tenant-blog "Create a multi-tenant blog where each user gets a subdomain, with request-level routing, headless content API, and role-based auth..." routing-middleware, cms, auth
status-page "Build a SaaS status page with scheduled endpoint pinging, uptime charts, incident logging, and KV-stored history..." cron-jobs, vercel-storage, observability
dog-walking-saas "Build a dog walking SaaS with user accounts, pet photos, booking, monthly invoicing, admin dashboard, and separate dev/prod env configs..." payments, auth, vercel-storage, env-vars

Cleanup

rm -rf ~/dev/vercel-plugin-testing

Reproducido de vercel/vercel-plugin bajo licencia NOASSERTION. Leer esta página en markdown.

Archivos

1 archivo en el paquete. Solo se lee SKILL.md al activarse — las referencias se cargan si el skill decide que las necesita.

Antes de instalar

Necesita en el PATH:npx

Variables de entorno:BASE

Detalles

Creador
vercel
Licencia
NOASSERTION
Recursos incluidos
Solo SKILL.md
Código fuente
Ver SKILL.md

Etiquetas

Más de vercel/vercel-plugin

Este repo incluye 43 skills. Si instalas uno, normalmente ya tienes los demás.

Corrects outdated LLM knowledge about the Vercel platform and introduces new products. Injected at session start.

Costo de contexto al activarse
1.8k tok
Tamaño del paquete
1 archivo
Última actualización
hace 14 días
Oficialbases de datos

Vercel Connect expert guidance — securely obtain scoped OAuth tokens for third-party services (Slack, GitHub, MCP servers, OAuth, Snowflake) on behalf of apps or users via Vercel OIDC. Use when wiring up third-party API access, connecting to MCP servers, sending Slack messages, accessing GitHub APIs, receiving webhook events from Slack/Linear/GitHub and forwarding them to your agents and apps, or building eve agent connections.

Costo de contexto al activarse
4.8k tok
Tamaño del paquete
1 archivo
Última actualización
hace 14 días
Oficialdesarrollo apis

Debug Vercel CDN caching — cache hit rate, stale content, revalidation behavior, ISR + PPR, per-request cache reasons (cacheReason) and PPR state (ppr_state), and costs.

Costo de contexto al activarse
5.2k tok
Tamaño del paquete
1 archivo
Última actualización
hace 21 días
Oficialdevops infraestructura

Vercel Functions expert guidance — Serverless Functions, Edge Functions, Fluid Compute, streaming, Cron Jobs, and runtime configuration. Use when configuring, debugging, or optimizing server-side code running on Vercel.

Costo de contexto al activarse
5.6k tok
Tamaño del paquete
1 archivo
Última actualización
hace 13 días
Oficialherramientas desarrollo

Backend architecture guidance. Use when planning, building, or migrating an API or backend; choosing between Functions, Services, containers, Workflow, Queues, and Marketplace databases; or selecting a supported backend framework or runtime.

Costo de contexto al activarse
1.5k tok
Tamaño del paquete
2 archivos
Última actualización
hace 5 días
Oficialdevops infraestructura

Eve

263

eve framework guidance for durable AI agents and agent-powered applications. Use when creating, editing, or debugging an eve project, when the user explicitly asks for eve, or when the build-agents skill has selected eve as the default framework. Covers eve's filesystem-first runtime, durable sessions, tools, skills, connections, channels, sandboxes, subagents, schedules, evals, frontend clients, and Agent Runs observability. Do not use for incidental agent mentions, generic agent-building prompts, or established non-eve stacks unless the user asks for comparison or migration.

Costo de contexto al activarse
1.5k tok
Tamaño del paquete
3 archivos
Última actualización
hace 14 días
Oficialherramientas desarrollo

Skills relacionados

Vercel Connect expert guidance — securely obtain scoped OAuth tokens for third-party services (Slack, GitHub, MCP servers, OAuth, Snowflake) on behalf of apps or users via Vercel OIDC. Use when wiring up third-party API access, connecting to MCP servers, sending Slack messages, accessing GitHub APIs, receiving webhook events from Slack/Linear/GitHub and forwarding them to your agents and apps, or building eve agent connections.

Costo de contexto al activarse
4.8k tok
Tamaño del paquete
1 archivo
Última actualización
hace 14 días
Oficialdesarrollo apis

Vercel Workflow SDK expert guidance. Use when building durable workflows, long-running tasks, API routes or agents that need pause/resume, retries, step-based execution, or crash-safe orchestration with Vercel Workflow.

Costo de contexto al activarse
11k tok
Tamaño del paquete
3 archivos
Última actualización
hace 13 días
Oficialdesarrollo apis

Access and test Vercel deployments protected by Vercel Authentication, SSO, or Deployment Protection. Use when curl, agent-browser, Playwright, or another automated request reaches a Vercel login or protection page; when a protected preview or production URL returns 401 or 403; when TRUSTED_SOURCES_ENVIRONMENT_MISMATCH appears; or when choosing between `vercel curl` and the `x-vercel-trusted-oidc-idp-token` header.

Costo de contexto al activarse
1.9k tok
Tamaño del paquete
1 archivo
Última actualización
hace 25 días
Oficialherramientas desarrollo