agents
Use when designing, deploying, or debugging a Butterbase Agent (declarative LLM/tool graph), registering an MCP server for tool use, or wiring access controls and rate limits. Agents are first-class app resources defined by a `graph_spec` and invoked over `/v1/<app_id>/agents/<name>/runs`.
Profile →npx skills add butterbase-ai/butterbase-skills --skill agents --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Butterbase Agents A Butterbase agent is a **declarative graph** of LLM and tool nodes — not a free-running chat loop. The runtime traverses the graph, calls tools (builtin / MCP / function), and resolves the `end` node's `output_template`. State, rate limits, and budgets are enforced by the control plane. ## When to use - The user wants to add a workflow that combines an LLM with tool calls (DB writes, storage reads, MCP servers, app functions). - The user wants to expose an agent endpoint to end users (`visibility: public` or `authenticated`). - Debugging a failing agent run (look at `list_agent_runs`, then `get_agent_run`). - Registering an external MCP server for the agent to use. Don't use for plain LLM chat completions — use the `ai` skill (`manage_ai` / `/v1/ai/chat`). Agents are for stateful, multi-step, tool-using workflows. ## Concepts ### `graph_spec` (validated by `validate_agent_spec` before anything is persisted) | Field | Required | Notes | |---|---|---| | `spec_version` | yes | Literal `"1"`. | | `entry` | yes | ID of the first node. | | `nodes` | yes | Record `{ id → node }`. | | `edges` | yes | `[{ from, to }]`. Both endpoints must exist in `nodes`. | | `tools` |
- When to use
- Concepts
- graphspec (validated by validateagentspec before anything is persisted)
- Builtin tools (always available, no setup)
- MCP servers
- Access & limits
- Procedure
- Designing a new agent
- Editing
- Debugging a failing run
- CLI
- Anti-patterns
What does the agents skill do?
Use when designing, deploying, or debugging a Butterbase Agent (declarative LLM/tool graph), registering an MCP server for tool use, or wiring access controls and rate limits. Agents are first-class app resources defined by a `graph_spec` and invoked over `/v1/<app_id>/agents/<name>/runs`.
How do I install it?
Run `npx skills add butterbase-ai/butterbase-skills --skill agents --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From butterbase-ai/butterbase-skills, a repository with 532 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.