@vatio-ai/skills 1.28.1 → 1.29.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.28.1",
+  "version": "1.29.1",
   "author": {
     "name": "Vatio",
     "url": "https://vatio.ai"

package/README.md

@@ -77,8 +77,10 @@ program, the [Vatio CLI](https://github.com/vatio-ai/cli)
   before it leaves) bring your workspace's conversations to your terminal.
   `vatio docs` fetches the docs.
 - **How each command ended.** The CLI tells Vatio which command ran, its exit
-  code and, on failure, what it printed; never arguments, file contents,
-  secrets or what a chat said. `VATIO_TELEMETRY=0` turns it off.
+  code, how long it took, which version of these skills the project has and,
+  on failure, what it printed; never arguments, file contents, secrets or what
+  a chat said. Installing these skills tells Vatio once, with their version
+  and the coding agent. `VATIO_TELEMETRY=0` turns both off.
 - **Feedback.** `vatio feedback "..."` sends the text your agent writes about
   what got in its way.
 - **Your coding session, only if you say yes.** `vatio-share-session` shows

package/bin/install.mjs

@@ -4,8 +4,10 @@
 //   .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 { cpSync, existsSync, readFileSync, readdirSync, rmSync, writeFileSync } from "node:fs";
-import { dirname, join, relative } from "node:path";
+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 { fileURLToPath } from "node:url";
 
 const usage = `usage: npx @vatio-ai/skills [--dir PATH]
@@ -72,3 +74,67 @@ function installedByUs(dir, name) {
 console.log(`
 Ask your coding agent to build or improve a Vatio agent and it will use them.
 Docs: https://vatio.ai/docs/integrations/claude-code`);
+
+await reportInstall();
+
+// One event saying the skills were installed: this version, which coding
+// agent ran it, and the CLI's session for this directory, so the commands
+// that follow here read as the same session. Nothing about the project.
+// VATIO_TELEMETRY=0 (or DO_NOT_TRACK=1) skips it, as it does for the CLI.
+async function reportInstall() {
+  const off = ["0", "false", "off", "no"].includes(String(process.env.VATIO_TELEMETRY ?? "").trim().toLowerCase()) ||
+    ["1", "true"].includes(String(process.env.DO_NOT_TRACK ?? "").trim().toLowerCase());
+  if (off) return;
+
+  console.log("Letting Vatio know these skills were installed (their version and the coding agent, nothing else).\nVATIO_TELEMETRY=0 skips it.");
+  const base = String(process.env.VATIO_BASE_URL ?? "").trim().replace(/\/+$/, "") || "https://vatio.ai";
+  try {
+    await fetch(`${base}/api/developer/v1/cli/events`, {
+      method: "POST",
+      headers: {
+        "Content-Type": "application/json",
+        "User-Agent": `vatio-skills/${version}`,
+        "X-Vatio-Session": sessionId(),
+        "X-Vatio-Agent": codingAgent()
+      },
+      body: JSON.stringify({ kind: "install", command: "skills install", exit_code: 0, skills: `copy ${version}` }),
+      signal: AbortSignal.timeout(1_500)
+    });
+  } catch {
+    // Telemetry never fails an install.
+  }
+}
+
+// The same detection as the CLI's (cli/lib/telemetry.mjs), which this
+// package cannot import.
+function codingAgent() {
+  const env = process.env;
+  if (env.VATIO_AGENT) return String(env.VATIO_AGENT).slice(0, 64);
+  if (env.CLAUDECODE) return "claude-code";
+  if (env.CURSOR_AGENT || env.CURSOR_TRACE_ID) return "cursor";
+  if (env.CODEX_THREAD_ID || env.CODEX_SESSION_ID || env.CODEX_SANDBOX || env.CODEX_MANAGED_BY_NPM) return "codex";
+  if (env.GEMINI_CLI) return "gemini-cli";
+  if (env.REPL_ID) return "replit";
+  if (env.CI) return "ci";
+  return process.stdout.isTTY ? "human" : "unknown";
+}
+
+// The CLI's session for this directory (~/.vatio/sessions.json), or a new
+// one it will pick up: a session ends after 30 minutes without a command.
+function sessionId() {
+  const home = String(process.env.VATIO_HOME ?? "").trim();
+  const path = join(home === "" ? join(homedir(), ".vatio") : resolve(home), "sessions.json");
+  const key = resolve(root);
+  try {
+    const sessions = existsSync(path) ? JSON.parse(readFileSync(path, "utf8")) : {};
+    const now = Date.now();
+    const current = sessions[key];
+    const id = current && now - Date.parse(current.last_used_at) < 30 * 60 * 1000 ? current.id : randomUUID();
+    sessions[key] = { id, last_used_at: new Date(now).toISOString() };
+    mkdirSync(dirname(path), { recursive: true });
+    writeFileSync(path, JSON.stringify(sessions));
+    return id;
+  } catch {
+    return randomUUID();
+  }
+}

package/package.json

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

@@ -15,10 +15,9 @@ here. Start by reading them:
 vatio test list
 ```
 
-(`vatio flags` on a CLI older than 0.120.0.) Run it from the directory with
-the workspace's `vatio.yml` (or below it). It prints every open report — the
-conversation, each tool call with what the backend answered, and the
-supervisor's note — then the tests that fail on preview and the ones the
+Run it from the directory with the workspace's `vatio.yml` (or below it).
+It prints every open report — the conversation, each tool call with what
+the backend answered, and the supervisor's note — then the tests that fail on preview and the ones the
 agent answers differently each time, with how to work them at the top, and
 every test last. Follow those instructions; they take precedence over
 anything below.