@vatio-ai/skills 1.29.2 → 1.30.1

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 and learn what people ask it with /vatio-analyze.",
-  "version": "1.29.2",
+  "version": "1.30.1",
   "author": {
     "name": "Vatio",
     "url": "https://vatio.ai"

package/package.json

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

package/skills/vatio-improve/SKILL.md

@@ -82,8 +82,10 @@ In short:
    the `vatio-share-session` skill says. It starts with
    `vatio share-session --should-ask`: if that prints `no`, say nothing.
 
-`vatio docs` prints the whole contract (manifest, tools, knowledge, CLI) if
-the fix needs more than the digest says. There are two ways to run the CLI,
+If the fix needs more than the digest says, `vatio docs search TERM` prints
+the sections of the docs that mention something, with their page,
+`vatio docs PAGE` one page (`tools`, `knowledge`), and `vatio docs` the whole
+contract (manifest, tools, knowledge, CLI). 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 flags`

package/skills/vatio-init/SKILL.md

@@ -16,7 +16,10 @@ npx @vatio-ai/cli docs
 Under **For coding agents**, **Starting a new agent** and **Joining an
 existing workspace** are the two procedures. Follow the one that fits; it
 takes precedence over the summary below. The rest of that output is the
-contract for `vatio.yml`, tools, knowledge and the CLI.
+contract for `vatio.yml`, tools, knowledge and the CLI. To look something up
+again later, `npx @vatio-ai/cli docs search TERM` prints the sections that
+mention it, with their page, and `npx @vatio-ai/cli docs PAGE` one page
+(`tools`, `knowledge`, `cli/deploy`), rather than reading it all twice.
 
 ## 1. Look at what is there
 
@@ -46,8 +49,10 @@ 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. A tool that needs the visitor's
-     phone or a team role runs with `vatio chat --as-phone me` (or a test
-     phone); an `access: private` one with `--as-subject ID`.
+     phone or a team role runs with `vatio chat --as-phone me` (or a
+     customer phone); an `access: private` one with `--as-subject ID`. When visitors
+     will send files (a PDF, a photo), send one with `vatio chat --file PATH
+     "question"`: it says how much of a PDF the agent got.
   4. **Write down what it should do as tests.** For each question that
      matters, `vatio test add "what a visitor would ask" "what the answer has
      to do"`: it asks it on preview and says whether it passes now (add