# The Vatio plugin for Claude Code

Already building an app with Claude Code? Vatio adds a conversational agent
that can serve its users. Describe what you need; `vatio-init` reads your app,
sets up the agent and gives you a preview. Vatio hosts the conversations,
and your team follows them in the [inbox](https://vatio.ai/docs/channels/inbox).

After launch, make `vatio-improve` your daily routine: report a mistake,
let Claude prepare a fix, review Vatio's tests and approve publication.
You do not need to learn the CLI to follow this path.

## Install

Open Claude Code in your app's project. Run these commands one at a time:

```
/plugin marketplace add vatio-ai/skills
/plugin install vatio@vatio
```

Follow the installation panel and select the scope you want. If Claude asks
for a plugin reload, follow its message before continuing. The commands come
from the [Claude Code plugin installation guide](https://code.claude.com/docs/en/discover-plugins).

## Create your agent with one prompt

[Create your account](https://vatio.ai/session/new), then tell Claude:

```text
Use vatio-init to build a support agent for this app. Connect it to our
existing users and features, define its permissions and human handoff,
and give me a preview to try before publishing.
```

Claude reads your project and asks only what it cannot infer: what the agent
may do, what it must never promise and when a person should take over.
Try the preview and ask Claude to publish when it is ready.

## Your daily routine

1. Read real conversations in the inbox. Report a wrong reply and write what
   should have happened.
2. In your app's project in Claude Code, run `/vatio:vatio-improve`.
3. Review which reported cases now pass and approve publication of the fix.

Claude can fix instructions, knowledge, tools or the backend they call.
Vatio tests the reported cases against preview; publication checks reject a
case that was passing live and now fails. It does not guarantee every possible
answer. The daily email gives you the same command when new reports arrive.
See [Improve your agent](https://vatio.ai/docs/improve) for the full process.

## Hand work to Claude from a chat

The plugin is Claude Code working on your agent. The other direction works
too: your agent can hand a request from a WhatsApp chat to a Claude Code
routine, which works on your code and answers in the same chat. See
[Connect Vatio to Claude Code](https://vatio.ai/docs/connect-claude-code).

## Install without the plugin

From the root of your project:

```
npx @vatio-ai/skills
```

That copies the skills into `.claude/skills/` and `.agents/skills/`, and
Claude Code lists them as `/vatio-init`, `/vatio-improve` and
`/vatio-share-session`. Run it again to update them. This is also the installation path for
other coding agents that read skills.

### Keeping them up to date

Claude Code does not update plugins from other people's marketplaces on its
own. Turn it on once in `/plugin` → **Marketplaces** → **vatio** → **Enable
auto-update**, or update by hand with `claude plugin update vatio@vatio` (or
`/plugin` → **Installed** → **Update now**). Copies made with
`npx @vatio-ai/skills` update by running it again. `vatio flags` and
`vatio eval` say so when the skills are missing or older than the published
ones.

## The skills

| Skill | What it does | Call it directly |
|---|---|---|
| `vatio-init` | The first one in a project: looks at what is already there (a `vatio.yml` anywhere in the repository, the app's code) and recommends from it. With no agent yet, builds one: asks the owner what the code does not answer, writes `vatio.yml`, pushes it and hands over a link to try. With one, explains it, compares it with live and says what to work on | `/vatio:vatio-init` |
| `vatio-improve` | Takes every reply supervisors flagged in the inbox in one session: reads `vatio flags`, fixes each cause, pushes to preview, proves it with `vatio eval` in the background, and publishes through the [publish checks](https://vatio.ai/docs/deployments#publishing) | `/vatio:vatio-improve` |
| `vatio-share-session` | Sends this Claude Code session to the Vatio team when you ask it to, or offers to when the other two finish: shows what would go, asks you first with Claude Code's own question (send it, send it with a comment, not now, don't ask again), and runs `vatio share-session` | `/vatio:vatio-share-session` |

Claude Code picks the right one on its own when you ask to build, improve or
fix a Vatio agent, or to send the session to Vatio; the commands are there when
you want to be explicit.

The skills are short on purpose. They only say *when* to use the CLI; the
instructions come from the platform each time `vatio docs` or `vatio flags`
runs, so those are always current. See
[Starting a new agent](https://vatio.ai/docs/#starting-a-new-agent),
[Improve from flags](https://vatio.ai/docs/improve) and
[Share a session](https://vatio.ai/docs/cli/workspace#share-a-session) for what each one follows.

## Share a session with the Vatio team

When something got in the way and a sentence will not explain it, say "send
this session to Vatio" or run `/vatio-share-session`. Claude Code asks you
before anything is sent, and `vatio share-session` shows which session goes,
with images left out, anything that looks like a secret replaced with
`[REDACTED]`, and email addresses and phone numbers with `[EMAIL]` and
`[PHONE]`. It also suggests adding feedback in your own words — what got in
the way, what you expected — which goes with the session if you give some.
Only the Vatio team reads it, every read is logged, and it is deleted 30 days
after it arrives. If Claude Code's auto mode refuses to send it,
Claude Code gives you the command to run yourself and then checks with
`vatio share-session --list` that it went.

When `vatio-init` or `vatio-improve` finish, Claude Code offers to send it, with
three answers: send it, not now, or don't ask again. It offers at most once a
week and never twice in a session, and after don't ask again it stops for
good ([When your coding agent offers it](https://vatio.ai/docs/cli/workspace#when-your-coding-agent-offers-it)).

## Other coding agents

- **Any agent that reads skills** (Codex, Cursor, Gemini CLI, GitHub Copilot,
  OpenCode and others): `npx @vatio-ai/skills` from the root of your project
  puts them in `.agents/skills/`, where those agents look, without asking
  anything. Or `npx skills add vatio-ai/skills`, the open
  [skills](https://skills.sh) CLI, which asks which agents you use. The
  package is [`@vatio-ai/skills`](https://www.npmjs.com/package/@vatio-ai/skills),
  and its source is [vatio-ai/skills](https://github.com/vatio-ai/skills).
- **Any agent at all:** `vatio init` writes a short Vatio section into the
  workspace's `AGENTS.md`, which most coding agents read without installing
  anything, and the prompt on [vatio.ai](https://vatio.ai) has any agent
  install the skills first and follow `vatio-init`.

Bugs and ideas for the skills go to
[vatio-ai/skills issues](https://github.com/vatio-ai/skills/issues).