Eve Agent Skill
Build durable backend AI agents with the eve framework. Use when creating, editing, or debugging an eve project — agent instructions, skills, tools, connections, channels, sandboxes, subagents, schedules, or evals.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/vercel/vercel-plugin --skill eveWhat it tells the agent to use
found in the instruction textThe instruction itself
3 sections, as written by the authoreve
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.
Vercel Agent Runs
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
Source of truth
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.
Other skills for the same job
different authors, same section of the catalogue
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Replace with description of the skill and when Claude should use it.
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
This skill should be used when the user wants to "create a skill", "add a skill to plugin", "write a new skill", "improve skill description", "organize skill content", or needs guidance on skill structure, progressive disclosure, or skill development best practices for Claude Code plugins.
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
Use when creating new skills, editing existing skills, or verifying skills work before deployment
How to use it
Take vercel/vercel-plugin-eve from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.
The instructions reference npm, npx.
Without those the skill loads but fails at the first command.