@vatio-ai/skills 1.19.0 → 1.20.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.19.0",
+      "version": "1.20.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.19.0",
+  "version": "1.20.0",
   "author": {
     "name": "Vatio",
     "url": "https://vatio.ai"

package/README.md

@@ -19,7 +19,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 (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-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-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 |

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vatio-ai/skills",
-  "version": "1.19.0",
+  "version": "1.20.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-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, which
-  workspace this directory resolves to, and whether it pushed to a trial.
+- **This machine.** `vatio doctor`: whether it is signed in, and which
+  workspace this directory resolves to.
 
 ## 2. Say what you found, and recommend
 
@@ -46,17 +46,11 @@ you recommend, and ask them to confirm.
      team when a person should take over: **Human in the loop** in the docs).
   3. `vatio diff`, `vatio push`, then try it with `vatio chat`, including a
      conversation that should hand off.
-  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.
+  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.
   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 trial
-     has to be kept first.
+     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**:
@@ -96,14 +90,12 @@ that same section.
    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. 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.
+`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.
 
 A command you hand the developer to run themselves, because a permission
 check refused it or it needs their own credentials, says