@vatio-ai/skills 1.21.0 → 1.22.0

package/.claude-plugin/marketplace.json

@@ -12,7 +12,7 @@
       "name": "vatio",
       "source": "./",
       "description": "Vatio skills for Claude Code, Cursor and Codex: add an AI agent to the app you're building with /vatio-init, put it in your web, iOS, Android or Flutter app with /vatio-add-to-app, then improve it daily with /vatio-improve and learn what people ask it with /vatio-analyze.",
-      "version": "1.21.0",
+      "version": "1.22.0",
       "homepage": "https://vatio.ai/docs/integrations/claude-code",
       "category": "development",
       "keywords": [

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, put it in your web, iOS, Android or Flutter app with /vatio-add-to-app, then improve it daily with /vatio-improve and learn what people ask it with /vatio-analyze.",
-  "version": "1.21.0",
+  "version": "1.22.0",
   "author": {
     "name": "Vatio",
     "url": "https://vatio.ai"

package/package.json

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

package/skills/vatio-improve/SKILL.md

@@ -40,7 +40,12 @@ In short:
    failing tool rarely gets reported, because the agent apologizes and moves
    on. Fix those too.
 3. `vatio push`. It updates preview and runs no tests. No branch or
-   environment to set up: preview is the one.
+   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
+   the Vatio MCP in Claude or ChatGPT), run `vatio pull`, which writes them
+   into `vatio.yml` and `tools/` (commit your work first: it wants a clean
+   git tree), check `git diff` still carries your fix, and push again. Never
+   `vatio push --force` over them unless the developer says so.
 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

package/skills/vatio-init/SKILL.md

@@ -59,13 +59,18 @@ you recommend, and ask them to confirm.
   `vatio.yml` (what it is for, its tools, its knowledge, when it hands off)
   and recommend from what you see:
   - the folder differs from live: say so first, the repository may be behind;
+  - `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;
   - 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.
 - **A workspace slug but no `vatio.yml`.** Ask for the repository it lives
-  in: Vatio keeps what was deployed, not the files it came from. Do not
-  `vatio init` one instead.
+  in. If it was built from the Vatio MCP in Claude or ChatGPT, it has none
+  yet: `vatio init SLUG` in the repository it should live in, then, before
+  any push, `vatio pull --force` to replace the starter agent with the one
+  Vatio runs. Otherwise do not `vatio init` one instead.
 
 ## Claude Code permissions