vatio-ai/skills

Building an app with Claude Code, Cursor or Codex? Give it an agent that knows
the app and its users. In your app’s project:
Then, in Claude Code, run /vatio-init (in Cursor or Codex, ask it to use
vatio-init). It builds the agent from your project; Vatio
runs it with an inbox, human handoff and evaluation checks. You try the preview
and approve publication.
After launch, report mistakes in the inbox and make /vatio-improve your
daily routine. Your coding agent prepares fixes, Vatio tests the reported
cases, and you approve the update. You do not need to write code yourself; you
need your app’s project on your computer and Node.js 20 or newer.
| Skill | What it does |
|---|---|
| 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, gets a developer who joined the project up to speed |
| vatio-add-to-app | Puts the agent in your app once you have tried it: the web widget, or the iOS, Android or Flutter SDK with a chat screen in your app's style, a publishable token for development and one for release, and your signed-in users passed along |
| vatio-improve | Takes every reply your supervisors reported in the inbox in one session: reads vatio flags, fixes each cause, vatio push, proves it with vatio test (on Vatio's servers, in the background) and publishes with vatio publish after your approval |
| vatio-analyze | Reads what people talked about with the agent between two dates, from vatio chat export (redacted by Vatio before it leaves): topics with their counts, the questions it could not answer and the words people use, in a report for writing content, FAQs or knowledge. Anyone on the workspace's team can run it, viewers included |
| vatio-share-session | Sends the coding session to the Vatio team when you ask it to, or offers to when the others finish (send it, not now, or don't ask again), after showing you what goes (images left out, anything that looks like a secret redacted), with your feedback if you want to add some |
The skills are short on purpose. They tell your coding agent when to reach for
the Vatio CLI; the instructions themselves come from the platform when it runs
vatio docs or vatio flags, so they are never out of date.
Install
npx @vatio-ai/skills copies the skills into .claude/skills/, where Claude
Code reads them, and .agents/skills/, where Codex, Cursor, Gemini CLI,
GitHub Copilot and most other coding agents do. Run it again to update them.
As a Claude Code plugin
In Claude Code the same skills come as a plugin that can update itself. Run
these one at a time and follow the installation panel; the commands are then
/vatio:vatio-init and /vatio:vatio-improve: