@vatio-ai/skills 1.27.1 → 1.28.0

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "vatio",
   "description": "Vatio skills for Claude Code, Cursor and Codex: add an AI agent to the app you're building with /vatio-init, then improve it daily with /vatio-improve and learn what people ask it with /vatio-analyze.",
-  "version": "1.27.1",
+  "version": "1.28.0",
   "author": {
     "name": "Vatio",
     "url": "https://vatio.ai"

package/README.md

@@ -20,13 +20,13 @@ 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-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-improve` | Takes every reply your supervisors reported in the inbox in one session: reads `vatio test list`, 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.
+`vatio docs` or `vatio test list`, so they are never out of date.
 
 ## Install
 
@@ -55,7 +55,7 @@ Vatio, or you can call them by
 name: `/vatio-init`, `/vatio-improve`, `/vatio-analyze` and `/vatio-share-session`, or
 `/vatio:vatio-init` and so on from the plugin.
 
-`vatio init` also writes a pointer to `vatio flags` into the workspace's
+`vatio init` also writes a pointer to `vatio test list` into the workspace's
 `AGENTS.md`, which most coding agents read without installing anything.
 
 ## What it runs and sends
@@ -73,7 +73,7 @@ program, the [Vatio CLI](https://github.com/vatio-ai/cli)
   `.env` or `.git/`) to vatio.ai, which runs the agent. `vatio secrets set`
   sends a secret you name, stored encrypted.
 - **Conversations.** `vatio chat` sends what you type to your agent.
-  `vatio flags`, `vatio chat show` and `vatio chat export` (redacted by Vatio
+  `vatio test list`, `vatio chat show` and `vatio chat export` (redacted by Vatio
   before it leaves) bring your workspace's conversations to your terminal.
   `vatio docs` fetches the docs.
 - **How each command ended.** The CLI tells Vatio which command ran, its exit

package/bin/install.mjs

@@ -35,7 +35,7 @@ if (!existsSync(root)) {
 }
 
 const source = join(dirname(fileURLToPath(import.meta.url)), "..", "skills");
-// Left next to each copy, so `vatio flags` can tell a project whose copies are
+// Left next to each copy, so `vatio test list` can tell a project whose copies are
 // older than the published skills (cli/lib/skills-hint.mjs).
 const VERSION_FILE = ".vatio-skills-version";
 const { version } = JSON.parse(readFileSync(join(source, "..", "package.json"), "utf8"));

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vatio-ai/skills",
-  "version": "1.27.1",
+  "version": "1.28.0",
   "description": "Vatio skills for Claude Code, Cursor and Codex: add an AI agent to the app you're building with /vatio-init, then improve it daily with /vatio-improve and learn what people ask it with /vatio-analyze.",
   "keywords": [
     "vatio",

package/skills/vatio-improve/SKILL.md

@@ -12,13 +12,16 @@ instructions for working them on the platform, so they are never out of date
 here. Start by reading them:
 
 ```bash
-vatio flags
+vatio test list
 ```
 
-Run it from the directory with the workspace's `vatio.yml` (or below it). It
-prints every open report — the conversation, each tool call with what the
-backend answered, and the supervisor's note — with how to work them at the
-top. Follow those instructions; they take precedence over anything below.
+(`vatio flags` on a CLI older than 0.120.0.) Run it from the directory with
+the workspace's `vatio.yml` (or below it). It prints every open report — the
+conversation, each tool call with what the backend answered, and the
+supervisor's note — then the tests that fail on preview and the ones the
+agent answers differently each time, with how to work them at the top, and
+every test last. Follow those instructions; they take precedence over
+anything below.
 
 In short:
 
@@ -29,7 +32,7 @@ In short:
    provider or Vatio failed and Vatio wrote the reply itself. Do not change
    the agent for those: tell the developer, who can remove the report, and
    if they keep happening, `vatio feedback`.
-   `vatio flags rm ID` removes a report and its test for everyone. It is the
+   `vatio test rm ID` removes a report and its test for everyone. It is the
    developer's call: propose it (a report Vatio caused, one that asks for
    something the agent must not do, one whose fix is in but the tests cannot
    reproduce) and run it only when they say so.
@@ -40,7 +43,17 @@ In short:
    calls. `vatio tools --env live` shows each tool's error rate, timeouts and
    latency, and the calls that failed with what the backend answered: a
    failing tool rarely gets reported, because the agent apologizes and moves
-   on. Fix those too.
+   on. Fix those too. After the reports come the tests that fail on preview
+   (one the developer added for something the agent does not do yet, or a
+   regression) and the tests the agent answers differently each time (the
+   same version passes and fails them): work those too, as their sections
+   say. For an unsteady one the agent is usually inconsistent and the fix is
+   in `vatio.yml` or knowledge; when the note is what is vague, rewrite it;
+   when it no longer applies, propose removing it to the developer. Never
+   remove a test because it fails. Something the developer asks the agent to
+   do that no report covers is a test first:
+   `vatio test add "QUESTION" "WHAT IT SHOULD DO"` asks it on preview and
+   says whether it passes now; then fix until it does.
 3. `vatio push`. It updates preview and runs no tests. No branch or
    environment to set up: preview is the one. If it is refused because
    preview has changes made outside the files (someone edited the agent from

package/skills/vatio-init/SKILL.md

@@ -48,9 +48,11 @@ you recommend, and ask them to confirm.
      conversation that should hand off. A tool that needs the visitor's
      phone or a team role runs with `vatio chat --as-phone me` (or a test
      phone); an `access: private` one with `--as-subject ID`.
-  4. **Keep the replies that came out right.** For each one,
-     `vatio test add "what the answer has to say"` right after the
-     `vatio chat` that produced it. Three or four is enough to start. This is
+  4. **Write down what it should do as tests.** For each question that
+     matters, `vatio test add "what a visitor would ask" "what the answer has
+     to do"`: it asks it on preview and says whether it passes now (add
+     `--as-phone` or `--as-subject` as in `vatio chat`). Three or four is
+     enough to start. This is
      the only thing that makes a later version's mistake visible: `vatio
      test` replays them on every push, and once the workspace is published
      `vatio publish` refuses a version that breaks one. A workspace with no
@@ -74,7 +76,7 @@ you recommend, and ask them to confirm.
   - `vatio status` lists changes made outside the files (from the Vatio MCP
     in Claude or ChatGPT): `vatio pull` writes them into `vatio.yml` and
     `tools/` before anything is pushed;
-  - open reports in `vatio flags`: work them with the `vatio-improve` skill;
+  - open reports in `vatio test list`: work them with the `vatio-improve` skill;
   - tool calls failing in `vatio tools`: the fix is in the backend they call;
   - `workspace_forbidden`: they are not in the workspace yet, and the owner
     invites them from **Team** in the inbox.