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
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.
en todo el repo
0–100, la ruta de este skill
último commit aquí
últimos 90 días
146 tok en reposo
12 KB
Funciona con cualquier agente que lea SKILL.md
npx -y skills add vercel/vercel-plugin --skill eve --agent claude-codeSe instala solo en este repositorio.
eve is a filesystem-first framework for durable backend AI agents. An agent is a directory on disk — instructions, skills, tools, connections, channels, subagents, and schedules are all files — and eve compiles and runs it.
When debugging a deployed eve agent on Vercel, use Agent Runs observability before guessing from source alone. Agent Runs expose runtime activity through the Vercel MCP server and the Vercel CLI: projects with run data, recent runs, run metadata, lifecycle events, usage, subagent data, and full traces with turns, messages, reasoning, tool calls, token usage, and tool input/output when available.
To inspect runs through Vercel MCP, list the available Vercel MCP tools and use the Agent Runs tools exposed by the server. Tool names and schemas can change, so inspect the tool list/schema before hard-coding a name from memory.
For CLI usage, ask the installed CLI for the current Agent Runs surface:
vercel agent-runs --help
vercel agent-runs <subcommand> --help
Use --json when the subcommand help exposes it and machine-readable output is
needed.
If vercel agent-runs is missing, check vercel --version and upgrade first:
npm i -g vercel@latest
vercel agent-runs --help
The complete documentation ships inside the eve package. Do not rely on this
skill for guidance — always read the bundled docs, which match the installed
version exactly:
node_modules/eve/docs/
Start with node_modules/eve/docs/README.md. It contains the full
index and recommended reading order. Before writing any eve code, read the
relevant guide there first.
If eve is not installed yet, install it (npm install eve) or scaffold a new
agent with npx eve init <agent-name>, then read the bundled docs.
Reproducido de vercel/vercel-plugin bajo licencia NOASSERTION. Leer esta página en markdown.
3 archivos en el paquete. Solo se lee SKILL.md al activarse — las referencias se cargan si el skill decide que las necesita.
Necesita en el PATH:npm
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.
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.
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.
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.
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.
Default guidance for building AI agents. Use for generic requests to build, create, scaffold, design, architect, or implement an AI agent, agent app, tool-calling agent, durable agent, multi-agent system, or scheduled agent.
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.
Vercel AI Gateway expert guidance. Use when configuring model routing, provider failover, cost tracking, or managing multiple AI providers through a unified API.
Vercel AI SDK expert guidance. Use when building AI-powered features — chat interfaces, text generation, structured output, tool calling, agents, MCP integration, streaming, embeddings, reranking, image generation, or working with any LLM provider.