@vatio-ai/skills 1.23.0 → 1.25.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.23.0",
+      "version": "1.25.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.23.0",
+  "version": "1.25.0",
   "author": {
     "name": "Vatio",
     "url": "https://vatio.ai"

package/README.md

@@ -59,6 +59,36 @@ name: `/vatio-init`, `/vatio-add-to-app`, `/vatio-improve`, `/vatio-analyze` and
 `vatio init` also writes a pointer to `vatio flags` into the workspace's
 `AGENTS.md`, which most coding agents read without installing anything.
 
+## What it runs and sends
+
+The skills are instructions for your coding agent, with no hooks, MCP servers
+or anything that runs by itself. What they have your agent run is one
+program, the [Vatio CLI](https://github.com/vatio-ai/cli)
+(`npx @vatio-ai/cli`, downloaded from npm), and it talks to one service,
+[vatio.ai](https://vatio.ai):
+
+- **Sign-in.** The first `vatio push` (or `vatio login`) opens vatio.ai in your
+  browser; the token it gets back is saved in `~/.vatio/config.json`.
+- **Your agent's files.** `vatio check` and `vatio push` send the directory
+  that holds `vatio.yml` (its tools and knowledge, never hidden files such as
+  `.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
+  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
+  code and, on failure, what it printed; never arguments, file contents,
+  secrets or what a chat said. `VATIO_TELEMETRY=0` turns it off.
+- **Feedback.** `vatio feedback "..."` sends the text your agent writes about
+  what got in its way.
+- **Your coding session, only if you say yes.** `vatio-share-session` shows
+  you what would go (images left out, anything that looks like a secret
+  redacted) and sends it to the Vatio team only after you agree.
+
+What Vatio keeps and for how long is in its
+[privacy policy](https://vatio.ai/legal/privacy-policy).
+
 ## Docs
 
 [Improve your agent from flags](https://vatio.ai/docs/improve) ·

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vatio-ai/skills",
-  "version": "1.23.0",
+  "version": "1.25.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-add-to-app/SKILL.md

@@ -50,8 +50,10 @@ SDK, Android SDK, Flutter SDK, Authentication, Supabase) have the details.
    app's backend signs the visitor token, and the private key never goes into
    the app.
 6. **Try it in a development build**, signed out and signed in, then say what
-   you added and where each token lives. Release builds answer once the agent
-   is published: `vatio publish` only when they ask.
+   you added and where each token lives. While the workspace is a draft
+   (nobody outside the team has talked to the agent yet) live follows every
+   push, so release builds answer right away; after that they answer with
+   what is published, and `vatio publish` runs only when they ask.
 
 ## Before you finish
 

package/skills/vatio-improve/SKILL.md

@@ -63,7 +63,9 @@ In short:
    marked "not tested (Vatio's side)" says nothing about your fix: run
    `vatio test --wait` again. Name reports by id (`F-7K2QX`).
 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
+   it changes what visitors get. In a draft (no conversation from outside
+   the team yet) live already runs every push, and `vatio publish` says
+   there is nothing to publish. If it is refused, follow its message: it
    says what to run. Never pass `--force` unless the developer explicitly
    asks for it.
 6. If the digest, an error or the docs left you guessing, say so:

package/skills/vatio-init/SKILL.md

@@ -48,7 +48,11 @@ you recommend, and ask them to confirm.
      conversation that should hand off.
   4. Give them the link `vatio push` prints after `Try it:` (the inbox's
      Test page, with web chat, WhatsApp and Instagram) with what you
-     tried. Publish with `vatio publish` only when they ask.
+     tried. Until someone outside their team talks to the agent the
+     workspace is a draft: live follows every push, so there is nothing to
+     publish yet and you need not explain preview and live. Once `vatio push`
+     says live still runs an older version, publish with `vatio publish`
+     only when they ask.
   5. Once they have tried it, offer to put it in the app (the web widget,
      or the iOS, Android or Flutter SDK) with the `vatio-add-to-app` skill.
 - **A `vatio.yml`: the agent exists.** Never `vatio init` here: it writes a