@vatio-ai/skills 1.26.1 → 1.26.3

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.26.1",
+  "version": "1.26.3",
   "author": {
     "name": "Vatio",
     "url": "https://vatio.ai"

package/README.md

@@ -20,7 +20,7 @@ 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-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 key 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 |

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vatio-ai/skills",
-  "version": "1.26.1",
+  "version": "1.26.3",
   "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

@@ -1,6 +1,6 @@
 ---
 name: vatio-add-to-app
-description: Puts a Vatio agent where the app's users talk to it — the web widget in a web app, the Swift package in an iOS app, the Kotlin library in an Android app, the Dart package in a Flutter app — with a publishable token per environment, the signed-in user passed along, and, on mobile, a chat screen in the app's own style. Use after vatio-init, or when asked to add the agent, the chat, the widget or the Vatio SDK to a website, a web app, an iPhone/iOS app, an Android app or a Flutter app.
+description: Puts a Vatio agent where the app's users talk to it — the web widget in a web app, the Swift package in an iOS app, the Kotlin library in an Android app, the Dart package in a Flutter app — with a publishable key per environment, the signed-in user passed along, and, on mobile, a chat screen in the app's own style. Use after vatio-init, or when asked to add the agent, the chat, the widget or the Vatio SDK to a website, a web app, an iPhone/iOS app, an Android app or a Flutter app.
 ---
 
 # Put the agent in the app
@@ -27,11 +27,11 @@ SDK, Android SDK, Flutter SDK, Authentication, Supabase) have the details.
    A Flutter app needs both app origins. React Native and Expo have no Vatio SDK yet: say so, and
    `vatio feedback` that one was asked for.
 2. **Tell the user what you will add before changing anything**: which
-   screens or layout, which tokens, how signed-in users are passed, and ask
+   screens or layout, which keys, how signed-in users are passed, and ask
    them to confirm.
-3. **Tokens.** `vatio tokens create --env preview` for development builds and
+3. **Keys.** `vatio keys create publishable --env preview` for development builds and
    `--env live` for release builds, each with its origins (`--json` when the
-   token goes straight into a config or secrets store). `vatpub_` tokens
+   key goes straight into a config or secrets store). `vatpub_` keys
    ship in the app's configuration; a `vat_` token never does.
 4. **Add it.** Web: the widget, once for the whole app. iOS, Android and Flutter: the
    SDK has no UI, so write the chat screen in the app's own style from the
@@ -50,7 +50,7 @@ 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. While the workspace is a draft
+   you added and where each key 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.
@@ -74,7 +74,7 @@ A command you hand the developer to run themselves, because a permission
 check refused it or it needs their own credentials, says
 `npx @vatio-ai/cli@latest`, never `vatio`: the `vatio` installed on their
 machine can be too old for Vatio to accept. When one command's output feeds
-another (a token into a secrets store), take it with `--json` and chain with
+another (a key into a secrets store), take it with `--json` and chain with
 `&&`, never through `grep`, so a failure stops there instead of passing on an
 empty value. If Claude Code's auto mode refused a `vatio` command and the
 project's `.claude/settings.json` has no `Bash(vatio *)` rule, also mention

package/skills/vatio-improve/SKILL.md

@@ -33,13 +33,8 @@ In short:
    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.
-   A report can also say **What Vatio did**: when the cause was the agent's
-   instructions or a knowledge entry, Vatio already tried its own fix on
-   preview and tested it. One it kept is done: do not fix it again. One it
-   is still testing: leave what it changes alone until it settles. An
-   instructions fix is a change made outside the files, so before you edit
-   `vatio.yml` run `vatio pull` (commit your work first: it wants a clean git
-   tree) and check `git diff`.
+   Vatio changes nothing on preview by itself: every open report is yours to
+   fix.
 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
@@ -89,7 +84,7 @@ A command you hand the developer to run themselves, because a permission
 check refused it or it needs their own credentials, says
 `npx @vatio-ai/cli@latest`, never `vatio`: the `vatio` installed on their
 machine can be too old for Vatio to accept. When one command's output feeds
-another (a token into a secrets store), take it with `--json` and chain with
+another (a key into a secrets store), take it with `--json` and chain with
 `&&`, never through `grep`, so a failure stops there instead of passing on an
 empty value. If Claude Code's auto mode refused a `vatio` command and the
 project's `.claude/settings.json` has no `Bash(vatio *)` rule, also mention

package/skills/vatio-init/SKILL.md

@@ -123,7 +123,7 @@ A command you hand the developer to run themselves, because a permission
 check refused it or it needs their own credentials, says
 `npx @vatio-ai/cli@latest`, never `vatio`: the `vatio` installed on their
 machine can be too old for Vatio to accept. When one command's output feeds
-another (a token into a secrets store), take it with `--json` and chain with
+another (a key into a secrets store), take it with `--json` and chain with
 `&&`, never through `grep`, so a failure stops there instead of passing on an
 empty value. If Claude Code's auto mode refused a `vatio` command and the
 project's `.claude/settings.json` has no `Bash(vatio *)` rule, also mention