@vatio-ai/skills 1.14.2 → 1.16.0

package/.claude-plugin/marketplace.json

@@ -11,8 +11,8 @@
     {
       "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, then improve it daily with /vatio-improve.",
-      "version": "1.14.2",
+      "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 or Android app with /vatio-add-to-app, then improve it daily with /vatio-improve.",
+      "version": "1.16.0",
       "homepage": "https://vatio.ai/docs/integrations/claude-code",
       "category": "development",
       "keywords": [
@@ -27,6 +27,9 @@
         "codex",
         "whatsapp",
         "supabase",
+        "ios",
+        "android",
+        "chat-widget",
         "agent-skills"
       ]
     }

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, then improve it daily with /vatio-improve.",
-  "version": "1.14.2",
+  "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 or Android app with /vatio-add-to-app, then improve it daily with /vatio-improve.",
+  "version": "1.16.0",
   "author": {
     "name": "Vatio",
     "url": "https://vatio.ai"
@@ -21,6 +21,9 @@
     "codex",
     "whatsapp",
     "supabase",
+    "ios",
+    "android",
+    "chat-widget",
     "agent-skills"
   ]
 }

package/README.md

@@ -19,9 +19,10 @@ 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-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 (with no account, as a trial) and hands over a link to try it and one to keep it. 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 or Android 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-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 coding 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 |
+| `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 |
 
 The skills are short on purpose. They tell your coding agent when to reach for
 the Vatio CLI; the instructions themselves come from the platform when it runs
@@ -50,7 +51,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, or to send the session to Vatio, or you can call them by
-name: `/vatio-init`, `/vatio-improve` and `/vatio-share-session`, or
+name: `/vatio-init`, `/vatio-add-to-app`, `/vatio-improve` 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,9 +10,9 @@ import { fileURLToPath } from "node:url";
 
 const usage = `usage: npx @vatio-ai/skills [--dir PATH]
 
-Copies the Vatio skills (vatio-init, vatio-improve, vatio-share-session) into
-PATH/.agents/skills and PATH/.claude/skills. PATH defaults to the current
-directory.`;
+Copies the Vatio skills (vatio-init, vatio-add-to-app, vatio-improve,
+vatio-share-session) into PATH/.agents/skills and PATH/.claude/skills. PATH
+defaults to the current directory.`;
 
 const args = process.argv.slice(2);
 let root = process.cwd();

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@vatio-ai/skills",
-  "version": "1.14.2",
-  "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.",
+  "version": "1.16.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 or Android app with /vatio-add-to-app, then improve it daily with /vatio-improve.",
   "keywords": [
     "vatio",
     "ai-agent",
@@ -14,6 +14,9 @@
     "codex",
     "whatsapp",
     "supabase",
+    "ios",
+    "android",
+    "chat-widget",
     "agent-skills",
     "skills"
   ],

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

@@ -0,0 +1,57 @@
+---
+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 — 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 or an Android 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, Authentication, Supabase) have the details.
+
+## In short
+
+1. **Find where it goes.** Web, iOS, Android, 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).
+   React Native, Expo and Flutter 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
+   them to confirm.
+3. **Tokens.** `vatio tokens create --env preview` for development builds and
+   `--env live` for release builds, each with its origins. `vatpub_` tokens
+   ship in the app's configuration; a `vat_` token never does.
+4. **Add it.** Web: the widget, once for the whole app. iOS and Android: 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`) or
+   [vatio-ai/android](https://github.com/vatio-ai/android)
+   (`example/src/main/kotlin/ai/vatio/example/Views.kt`).
+5. **Signed-in users.** With `auth: supabase:` the web widget needs nothing
+   and the SDKs take the session's access token; with `auth: public_key:` the
+   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.
+
+## 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.
+
+`vatio` is `npx @vatio-ai/cli` when it is not installed globally.

package/skills/vatio-init/SKILL.md

@@ -26,8 +26,8 @@ contract for `vatio.yml`, tools, knowledge and the CLI.
 - **The app.** What the project does and for whom; the API an agent could
   call (routes, controllers, an OpenAPI file); how its users sign in; and the
   docs, FAQs or policies an agent could read as knowledge.
-- **This machine.** `vatio doctor`: whether it is signed in, and which
-  workspace this directory resolves to.
+- **This machine.** `vatio doctor`: whether it is signed in, which
+  workspace this directory resolves to, and whether it pushed to a trial.
 
 ## 2. Say what you found, and recommend
 
@@ -45,9 +45,17 @@ you recommend, and ask them to confirm.
      `vatio.yml` (and `tools/` for their APIs).
   3. `vatio diff`, `vatio push`, then try it with `vatio chat`, including a
      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.
+  4. Give them what `vatio push` printed, with what you tried. With no
+     account on this machine, the first push deploys a trial preview and
+     prints a **Try it** link and a **Keep it** link: give them both. Try it
+     is a web chat anyone with the link can use; Keep it is where they sign
+     in (email, Google or GitHub) and keep the agent, which publishing,
+     secrets and tokens wait for. Never open Keep it yourself. Signed in,
+     `Try it:` is the inbox's Test page, with web chat, WhatsApp and
+     Instagram. 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 or Android SDK) with the `vatio-add-to-app` skill. A trial
+     has to be kept first.
 - **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**:
@@ -72,9 +80,11 @@ you recommend, and ask them to confirm.
    the `vatio-share-session` skill says. It starts with
    `vatio share-session --should-ask`: if that prints `no`, say nothing.
 
-`vatio` is `npx @vatio-ai/cli` when it is not installed globally. The first
-`vatio push` (or `vatio login`) signs the developer in: it opens the browser
-on their machine (if it doesn't, give them the link it prints). Tell them to
-sign in with email, Google or GitHub and check that the code on the page
-matches the one the terminal printed. If the command times out waiting, run
-it again after they have signed in: it picks up the same sign-in page.
+`vatio` is `npx @vatio-ai/cli` when it is not installed globally. Nothing
+asks for an account until they keep the trial (or you run `vatio login`).
+Once they have kept it, the next `vatio` command signs this terminal in: it
+opens the browser on their machine (if it doesn't, give them the link it
+prints). Tell them to sign in with the account that kept it and check that
+the code on the page matches the one the terminal printed. If the command
+times out waiting, run it again after they have signed in: it picks up the
+same sign-in page.

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 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, vatio-add-to-app 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` or `vatio-improve` just finished.
+`vatio-init`, `vatio-add-to-app` or `vatio-improve` just finished.
 
 1. **Only when you are offering it**, ask the CLI first: