@vatio-ai/skills 1.29.1 → 1.30.0

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

package/bin/install.mjs

@@ -4,10 +4,11 @@
 //   .agents/skills/   Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode, Cline, Amp
 //   .claude/skills/   Claude Code, which does not read .agents/
 // Running it again overwrites the copies with this version's.
+import { spawnSync } from "node:child_process";
 import { randomUUID } from "node:crypto";
 import { cpSync, existsSync, mkdirSync, readFileSync, readdirSync, rmSync, writeFileSync } from "node:fs";
-import { homedir } from "node:os";
-import { dirname, join, relative, resolve } from "node:path";
+import { homedir, platform } from "node:os";
+import { basename, dirname, join, relative, resolve } from "node:path";
 import { fileURLToPath } from "node:url";
 
 const usage = `usage: npx @vatio-ai/skills [--dir PATH]
@@ -116,7 +117,30 @@ function codingAgent() {
   if (env.GEMINI_CLI) return "gemini-cli";
   if (env.REPL_ID) return "replit";
   if (env.CI) return "ci";
-  return process.stdout.isTTY ? "human" : "unknown";
+  if (process.stdout.isTTY) return "human";
+  const parent = launcher();
+  return parent ? `unknown:${parent}` : "unknown";
+}
+
+// What started the installer, when no coding agent said so: the first
+// ancestor that is not a shell or Node, by its process name.
+function launcher() {
+  if (platform() === "win32") return null;
+  const skip = new Set(["sh", "bash", "zsh", "fish", "dash", "ksh", "env", "node", "npm", "npx", "pnpm", "yarn", "bun", "sudo", "xargs", "timeout", "login"]);
+  try {
+    let pid = process.ppid;
+    for (let depth = 0; depth < 6 && pid > 1; depth++) {
+      const out = spawnSync("ps", ["-o", "ppid=,comm=", "-p", String(pid)], { encoding: "utf8", timeout: 500 });
+      const match = /^\s*(\d+)\s+(.+?)\s*$/.exec(out.stdout ?? "");
+      if (!match) return null;
+      const name = basename(match[2]).replace(/^-/, "");
+      if (!skip.has(name)) return name.replace(/[^\w .-]/g, "").slice(0, 40) || null;
+      pid = Number(match[1]);
+    }
+  } catch {
+    return null;
+  }
+  return null;
 }
 
 // The CLI's session for this directory (~/.vatio/sessions.json), or a new

package/package.json

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

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
 
@@ -47,7 +50,9 @@ you recommend, and ask them to confirm.
   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); 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