@vatio-ai/skills 1.11.0 → 1.13.0

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "vatio",
   "description": "The Vatio plugin for Claude Code: build a conversational agent for your app with one prompt, then improve it daily with vatio-improve.",
-  "version": "1.11.0",
+  "version": "1.13.0",
   "author": { "name": "Vatio", "url": "https://vatio.ai" },
   "homepage": "https://vatio.ai/docs",
   "repository": "https://github.com/vatio-ai/skills",

package/README.md

@@ -13,7 +13,7 @@ your app’s project in Claude Code.
 | 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 eval` (in the background in Claude Code) and publishes with `vatio publish` after your approval |
+| `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-share-session` | Sends the Claude Code session to the Vatio team when you ask it to, or offers to when the other two 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

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vatio-ai/skills",
-  "version": "1.11.0",
+  "version": "1.13.0",
   "description": "The Vatio plugin for Claude Code: build a conversational agent for your app with one prompt, then improve it daily with vatio-improve.",
   "keywords": [
     "vatio",

package/skills/vatio-improve/SKILL.md

@@ -22,26 +22,38 @@ top. Follow those instructions; they take precedence over anything below.
 
 In short:
 
-1. Group the reports by cause, and fix each cause where it lives:
+1. Read each report's **Diagnosis** first: it says whose it is to fix, from
+   what that turn did. **Your backend**: a tool call to it failed. **Your
+   agent**: everything answered and the reply was still wrong, so the fix is
+   in `vatio.yml`, knowledge or a tool's definition. **Vatio**: the model
+   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`.
+2. Group the reports by cause, and fix each cause where it lives:
    `vatio.yml`, a knowledge entry, a tool, or the developer's backend a tool
    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.
-2. `vatio push`. It updates preview and runs no tests. No branch or
+3. `vatio push`. It updates preview and runs no tests. No branch or
    environment to set up: preview is the one.
-3. `vatio eval` tests every report against preview. It can take several
-   minutes, so in Claude Code start it with the Bash tool's
-   `run_in_background` and read its report when it finishes. Iterate (fix,
-   push, eval) until the reports pass and nothing that passes on live fails.
-   Name reports by id (`F-7K2QX`).
-4. Show the developer what passes now, and `vatio publish` once they agree:
+4. `vatio test` tests every report against preview, on Vatio's servers: it
+   starts the runs, prints their ids and returns. `vatio test --wait` waits
+   for the report (several minutes), so in Claude Code start that with the
+   Bash tool's `run_in_background` and read the report when it finishes;
+   `vatio test --show RUN_ID` prints a run so far. A case that did not pass
+   comes with the `vatio chat show CHAT_ID` of its replay. Iterate (fix, push,
+   test) until the reports pass and nothing that passes on live fails. A case
+   marked "not tested (Vatio's side)" says nothing about your fix: run
+   `vatio test --wait` again. Name reports by id (`F-7K2QX`). A CLI before
+   0.81.0 calls it `vatio eval`.
+5. Show the developer what passes now, and `vatio publish` once they agree:
    it changes what visitors get. If it is refused, follow its message: it
    says what to run. Never pass `--force` unless the developer explicitly
    asks for it.
-5. If the digest, an error or the docs left you guessing, say so:
+6. If the digest, an error or the docs left you guessing, say so:
    `vatio feedback "what you were doing and what was missing"`.
-6. Last, in Claude Code, offer to send this session to the Vatio team, as
+7. Last, in Claude Code, offer to send this session to the Vatio team, as
    the `vatio-share-session` skill says. It starts with
    `vatio share-session --should-ask`: if that prints `no`, say nothing.