@vatio-ai/skills 1.26.4 → 1.27.0

package/.claude-plugin/marketplace.json

@@ -11,7 +11,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.",
+      "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.25.1",
       "homepage": "https://vatio.ai/docs/integrations/claude-code",
       "category": "development",

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

package/README.md

@@ -20,7 +20,6 @@ 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 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 |
@@ -53,7 +52,7 @@ auto-update**, or run `claude plugin update vatio@vatio`.
 Your coding agent then uses them on its own when you ask it to build, improve
 or fix a Vatio agent, to analyze its conversations, or to send the session to
 Vatio, or you can call them by
-name: `/vatio-init`, `/vatio-add-to-app`, `/vatio-improve`, `/vatio-analyze` and `/vatio-share-session`, or
+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

package/bin/install.mjs

@@ -10,8 +10,8 @@ import { fileURLToPath } from "node:url";
 
 const usage = `usage: npx @vatio-ai/skills [--dir PATH]
 
-Copies the Vatio skills (vatio-init, vatio-add-to-app, vatio-improve,
-vatio-analyze, vatio-share-session) into PATH/.agents/skills and
+Copies the Vatio skills (vatio-init, vatio-improve, vatio-analyze,
+vatio-share-session) into PATH/.agents/skills and
 PATH/.claude/skills. PATH defaults to the current directory.`;
 
 const args = process.argv.slice(2);
@@ -39,9 +39,9 @@ const source = join(dirname(fileURLToPath(import.meta.url)), "..", "skills");
 // 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"));
-// Skills this package used to ship under another name. Left in place, the old
-// copy would answer the same requests as the new one.
-const RENAMED = { "vatio-new": "vatio-init" };
+// Skills this package used to ship, and what replaced them (null: nothing).
+// Left in place, an old copy would keep answering requests.
+const RETIRED = { "vatio-new": "vatio-init", "vatio-add-to-app": null };
 const skills = readdirSync(source, { withFileTypes: true })
   .filter((entry) => entry.isDirectory())
   .map((entry) => entry.name);
@@ -53,11 +53,11 @@ for (const target of [".agents/skills", ".claude/skills"]) {
     writeFileSync(join(dest, VERSION_FILE), `${version}\n`);
     console.log(`  ${relative(process.cwd(), join(dest, "SKILL.md")) || dest}`);
   }
-  for (const [old, current] of Object.entries(RENAMED)) {
+  for (const [old, current] of Object.entries(RETIRED)) {
     const dest = join(root, target, old);
     if (!installedByUs(dest, old)) continue;
     rmSync(dest, { recursive: true, force: true });
-    console.log(`  removed ${relative(process.cwd(), dest) || dest} (now ${current})`);
+    console.log(`  removed ${relative(process.cwd(), dest) || dest}${current ? ` (now ${current})` : ""}`);
   }
 }
 

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@vatio-ai/skills",
-  "version": "1.26.4",
-  "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.27.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",
     "ai-agent",

package/skills/vatio-init/SKILL.md

@@ -61,8 +61,6 @@ you recommend, and ask them to confirm.
      publish yet and you need not explain preview and live. Every push says
      which of the two states the workspace is in; once it says visitors still
      get an older version, publish with `vatio publish` only when they ask.
-  6. 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
   starter agent, and pushing that replaces the real one. Work from the
   directory of the `vatio.yml` and follow **Joining an existing workspace**:

package/skills/vatio-share-session/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: vatio-share-session
 allowed-tools: AskUserQuestion
-description: Send this coding session to the Vatio team, so they can see where building or improving a Vatio agent got stuck. Use when the user asks to share, send or report this session (or "the conversation", "what we did") to Vatio, when the Vatio team asked them for it, when Vatio itself got in the way and they want the team to see exactly how, or when vatio-init, vatio-add-to-app or vatio-improve finish and say to offer it.
+description: Send this coding session to the Vatio team, so they can see where building or improving a Vatio agent got stuck. Use when the user asks to share, send or report this session (or "the conversation", "what we did") to Vatio, when the Vatio team asked them for it, when Vatio itself got in the way and they want the team to see exactly how, or when vatio-init or vatio-improve finish and say to offer it.
 ---
 
 # Send this session to the Vatio team
@@ -15,7 +15,7 @@ to see where Vatio got in the way and fix it; every read is logged, and it is
 deleted 30 days after it arrives (sooner on request to dpo@vatio.ai).
 
 It is sent in one of two ways: the user asked for it, or you offer it because
-`vatio-init`, `vatio-add-to-app` or `vatio-improve` just finished.
+`vatio-init` or `vatio-improve` just finished.
 
 1. **Only when you are offering it**, ask the CLI first:
 

package/skills/vatio-add-to-app/SKILL.md

@@ -1,79 +0,0 @@
----
-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 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
-
-The agent already exists: a `vatio.yml` in this repository, pushed at least
-once. If there is none, use the `vatio-init` skill first.
-
-Vatio keeps the procedure on the platform, so it is never out of date here.
-Read it first:
-
-```bash
-npx @vatio-ai/cli docs
-```
-
-Under **For coding agents**, follow **Putting the agent in the app**. It takes
-precedence over the summary below, and the pages it links (Web widget, iOS
-SDK, Android SDK, Flutter SDK, Authentication) have the details.
-
-## In short
-
-1. **Find where it goes.** Web, iOS, Android, Flutter, or several, and every origin a
-   build will call from: local and production web addresses,
-   `ios-app://BUNDLE_ID`, `android-app://APPLICATION_ID` (debug ids count).
-   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 keys, how signed-in users are passed, and ask
-   them to confirm.
-3. **Keys.** `vatio keys create publishable --env preview` for development builds and
-   `--env live` for release builds, each with its origins (`--json` when the
-   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
-   example in [vatio-ai/ios](https://github.com/vatio-ai/ios)
-   (`Example/VatioExample/Views.swift`),
-   [vatio-ai/android](https://github.com/vatio-ai/android)
-   (`example/src/main/kotlin/ai/vatio/example/Views.kt`) or
-   [vatio-ai/flutter](https://github.com/vatio-ai/flutter) (`example/lib/views.dart`).
-   For more than one screen (the conversation list, photos, voice notes, the
-   feedback card, settings), read a whole app built on the SDK:
-   [Vatio Chat for iOS](https://github.com/vatio-ai/vatio-chat-ios) or [for Android](https://github.com/vatio-ai/vatio-chat-android); each README
-   says which file shows what.
-5. **Signed-in users.** The app's own backend signs the visitor token (`vatio auth --new-key`,
-   then `auth: public_key:` in `vatio.yml`), the web widget and the SDKs take
-   it, 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 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.
-
-## Before you finish
-
-If an error or the docs left you guessing, say so:
-`vatio feedback "what you were doing and what was missing"`. Then, in Claude
-Code, offer to send this session to the Vatio team, as the
-`vatio-share-session` skill says; if `vatio share-session --should-ask` prints
-`no`, say nothing.
-
-There are two ways to run the CLI, and the package name appears once in
-either: `vatio ARGS` when it is installed globally, and
-`npx @vatio-ai/cli@latest ARGS` when it is not. Pick one per command and
-leave it whole — `npx @vatio-ai/cli @vatio-ai/cli push` is the commonest way
-to get this wrong, and the CLI reads the second name as the command and
-fails.
-
-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 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
-**Auto mode** on the docs' Claude Code page.