@vruum/skills 0.2.0 → 0.4.1

package/README.md

@@ -1,99 +1,49 @@
-# Vruum AI — skills + MCP for your AI assistant
+# @vruum/skills
 
-**The easy way to connect ChatGPT, Claude, Cursor, and friends to Vruum.** Ships skills and a remote MCP server URL so your AI assistant can search people, start outreach, diagnose replies, and run your whole sales pipeline through natural conversation.
+Vruum AI skills for Claude Code, Codex CLI, and any AI assistant with a skill directory.
 
-Paired with [vruum.ai](https://vruum.ai).
-
----
+Pairs with the Vruum MCP server at [https://api.vruum.ai/mcp](https://api.vruum.ai/mcp). For MCP-native clients (Claude Code, Claude Desktop, Cursor, VS Code Copilot, Cline), connecting to the MCP URL surfaces these skills as native slash commands. This npm package is for assistants that don't yet support MCP prompts (Codex CLI, ChatGPT, Windsurf).
 
 ## Install
 
-Pick the path that matches your assistant.
-
-### Claude Code (recommended — one command)
-
 ```bash
-/plugin marketplace add vruum-gtm/skills
-/plugin install vruum@vruum-gtm
-```
-
-That's it. Skills appear as slash commands. The MCP server connects automatically with OAuth (no secret to paste).
-
-### Claude Desktop
-
-Settings → Connectors → Add custom connector → paste:
-
-```
-https://api.vruum.ai/mcp
+npx @vruum/skills install
 ```
 
-Skills appear as slash commands on connection. Approve the OAuth flow when prompted.
-
-### ChatGPT (Business / Enterprise / Edu)
-
-Enable Developer Mode → Settings → Apps & Connectors → Add → paste:
+Detects Claude Code (`~/.claude/skills/`) and Codex CLI (`~/.codex/skills/`). For other harnesses:
 
+```bash
+npx @vruum/skills install --target /path/to/skills/dir
 ```
-https://api.vruum.ai/mcp
-```
-
-Note: ChatGPT uses MCP tools directly and doesn't currently surface prompts as slash commands. You still get every Vruum tool through natural conversation.
-
-### Cursor
 
-Settings → MCP → Add server → paste:
+## Skills
 
-```
-https://api.vruum.ai/mcp
-```
+<!-- generated:skills-begin -->
+- `/diagnose-reply` — Diagnose why a reply happened — what worked or didn't in the outreach that triggered it. Use when: why did they reply, what worked, diagnose reply, reply diagnosis, analyze this reply, what caused this reply, reply analysis.
+- `/engagement-triage` — Review and approve your pending LinkedIn engagement drafts and demand-gen content posts. Use when: triage engagements, review engagement queue, review warming comments, review nurture reactions, review marketing comments, review content drafts, check engagement queue.
+- `/enrich-prospect` — Deep prospect diarization — synthesize everything known about a person into a structured intelligence profile. Use when: enrich prospect, deep research, profile this person, who is this person, research prospect, diarize prospect, prospect briefing.
+- `/outreach-triage` — Review and approve your pending outreach drafts across LinkedIn and email. Use when: triage, review queue, morning review, check messages, approve outreach, what needs review.
+- `/vruum-skills-upgrade` — Upgrade @vruum/skills to the latest npm version and re-sync ~/.vruum/. Use when: upgrade vruum skills, update vruum, pull latest vruum skills, or when the preamble reports UPGRADE_AVAILABLE.
+<!-- generated:skills-end -->
 
-Prompts appear as slash commands on connection.
+## Upgrade
 
-### Codex CLI, Windsurf, other harnesses
-
-These tools don't yet support MCP prompts natively, so we ship the skill files as an npm package you can install into your harness's skill directory:
+Skills auto-prompt to upgrade via the preamble. To upgrade explicitly:
 
 ```bash
 npx @vruum/skills install
 ```
 
-Auto-detects `~/.claude/skills/` and `~/.codex/skills/`. For anything else:
+## Uninstall
 
 ```bash
-npx @vruum/skills install --target <your harness skill dir>
+npx @vruum/skills uninstall
 ```
 
-See `npx @vruum/skills install --help` for all options.
-
----
-
-## What you get
-
-Four slash commands that wrap the most common Vruum workflows:
-
-- **`/enrich-prospect`** — synthesize everything known about a person (LinkedIn, research, conversation history, engagement signals) into a structured intelligence profile. Reveals the gap between what their bio says and what they actually focus on.
-- **`/diagnose-reply`** — when someone replies, explain exactly what worked in your outreach. Turns every reply into a learning event.
-- **`/outreach-triage`** — review your pending outreach drafts with parallel AI review. Dispatches subagents to evaluate each message in your queue, surfaces fixes, and lets you approve in bulk or one at a time. Handles T1s (first touches), follow-ups (with deep research), and reply responses (high-stakes).
-- **`/engagement-triage`** — review your LinkedIn engagement queue (warming comments, nurture reactions, marketing comments) and demand-gen content post drafts. Same parallel-subagent pattern, tuned for voice-fit and post-relevance.
-
-Plus the full Vruum MCP tool surface (60+ tools) accessible via natural conversation: search people, start outreach, review messages, manage deals, check analytics, run market research, and more.
-
-
----
-
-## Auth
-
-OAuth 2.1 with PKCE and Dynamic Client Registration — handled by your AI client automatically. You sign in with your Vruum account in a browser popup the first time. Your AI assistant never sees your password or any API key.
-
-Accounts: sign up at [vruum.ai](https://vruum.ai).
-
----
-
-## Support
-
-- Product questions: [vruum.ai](https://vruum.ai)
-- Issues with this plugin: [github.com/vruum-gtm/skills/issues](https://github.com/vruum-gtm/skills/issues)
+Removes all symlinks this installer created. Does not touch `~/.vruum/auth.json` or other co-resident tool state.
 
-## License
+## Links
 
-MIT.
+- [Vruum](https://vruum.ai)
+- [MCP server](https://api.vruum.ai/mcp)
+- [Issues](https://github.com/vruum-gtm/skills/issues)

package/agents/vruum-engagement-reviewer.md

@@ -26,7 +26,7 @@ The orchestrator will tell you which type and provide IDs.
 
 ## Step 1: Load your items
 
-Call `get_engagement_review` with your assigned `engagement_ids`, `content_length="full"`, and `for_company` parameter. This returns for each item:
+Call `get_engagement_review` with your assigned `engagement_ids` and `content_length="full"`. This returns for each item:
 - The draft comment text (if comment or repost_commentary)
 - The reaction type (if reaction)
 - The target post text (what the prospect posted)
@@ -137,7 +137,7 @@ ISSUES_FOUND: {comma-separated or "none"}
 
 ## Step 1: Load your posts
 
-Call `get_content_review` with `for_company` parameter. This returns for each post:
+Call `get_content_review`. This returns for each post:
 - The draft content, type, tags, status, scheduled date
 - Past performance stats (avg engagement for same content type)
 - Calendar neighbors (other posts within 3 days)

package/agents/vruum-outreach-reviewer.md

@@ -22,7 +22,7 @@ You do NOT approve or send messages. You review, edit if needed, and return a st
 
 ## Step 1: Load your messages
 
-Call `get_outreach_review` with your assigned `message_ids`, `content_length="full"`, and `for_company` parameter. This returns full context for each message including:
+Call `get_outreach_review` with your assigned `message_ids` and `content_length="full"`. This returns full context for each message including:
 
 - The draft message content
 - Person info (name, title, company, match score)
@@ -88,7 +88,7 @@ If personalization is surface level or basic, and you have the tools to go deepe
 
 If a message needs better personalization or you need to verify something, you have access to:
 
-- **Knowledge base** (`search_knowledge_base` with `for_company`): Search the company's uploaded sales docs. Browse without filters first to see what's available, then narrow with `doc_type` or `query`.
+- **Knowledge base** (`search_knowledge_base`): Search the company's uploaded sales docs. Browse without filters first to see what's available, then narrow with `doc_type` or `query`.
 - **Web search**: Search for recent news about the prospect's company, their recent activity, industry trends relevant to them
 - **LinkedIn data** (`fetch_linkedin_data`): Pull the prospect's recent posts if not already in the review data
 - **Company research** (`get_company_research`, `fetch_company_website`): Get deeper company context if the match analysis feels thin

package/bin/vruum-skills-update-check

@@ -0,0 +1,120 @@
+#!/usr/bin/env bash
+# vruum-skills-update-check — periodic version check for the @vruum/skills
+# npm package. Ported from gstack's gstack-update-check, simplified.
+#
+# Output (one line, or nothing):
+#   JUST_UPGRADED <old> <new>       — marker found from a recent upgrade
+#   UPGRADE_AVAILABLE <old> <new>   — npm registry reports a newer version
+#   (nothing)                       — up to date, snoozed, or check skipped
+#
+# Env overrides (for testing):
+#   VRUUM_STATE_DIR     — override ~/.vruum state directory
+#   VRUUM_REMOTE_URL    — override npm registry URL
+set -euo pipefail
+
+STATE_DIR="${VRUUM_STATE_DIR:-$HOME/.vruum}"
+VERSION_FILE="$STATE_DIR/VERSION"
+CACHE_FILE="$STATE_DIR/last-update-check"
+MARKER_FILE="$STATE_DIR/just-upgraded-from"
+SNOOZE_FILE="$STATE_DIR/update-snoozed"
+CONFIG_FILE="$STATE_DIR/config.yaml"
+REMOTE_URL="${VRUUM_REMOTE_URL:-https://registry.npmjs.org/@vruum/skills/latest}"
+
+# Force flag busts cache + snooze (used by /vruum-skills-upgrade directly)
+if [ "${1:-}" = "--force" ]; then
+  rm -f "$CACHE_FILE" "$SNOOZE_FILE"
+fi
+
+# Step 0: if config says updates disabled, bail.
+if [ -f "$CONFIG_FILE" ] && grep -qE '^[[:space:]]*update_check[[:space:]]*:[[:space:]]*false' "$CONFIG_FILE"; then
+  exit 0
+fi
+
+# Step 1: local version (written by install.js at install time)
+[ -f "$VERSION_FILE" ] || exit 0
+LOCAL="$(tr -d '[:space:]' < "$VERSION_FILE")"
+[ -n "$LOCAL" ] || exit 0
+
+# Step 2: just-upgraded marker — emit once, clear snooze, fall through to check
+# remote in case another release landed since the upgrade.
+if [ -f "$MARKER_FILE" ]; then
+  OLD="$(tr -d '[:space:]' < "$MARKER_FILE" 2>/dev/null || true)"
+  rm -f "$MARKER_FILE" "$SNOOZE_FILE"
+  [ -n "$OLD" ] && echo "JUST_UPGRADED $OLD $LOCAL"
+fi
+
+# Step 3: snooze helper — returns 0 if snoozed (stay quiet), 1 if not.
+# Snooze file: "<version> <level> <epoch>". Levels: 1=24h, 2=48h, 3+=7d.
+check_snooze() {
+  local remote_ver="$1"
+  [ -f "$SNOOZE_FILE" ] || return 1
+  local sv sl se
+  sv="$(awk '{print $1}' "$SNOOZE_FILE" 2>/dev/null || true)"
+  sl="$(awk '{print $2}' "$SNOOZE_FILE" 2>/dev/null || true)"
+  se="$(awk '{print $3}' "$SNOOZE_FILE" 2>/dev/null || true)"
+  [ -n "$sv" ] && [ -n "$sl" ] && [ -n "$se" ] || return 1
+  case "$sl" in *[!0-9]*) return 1 ;; esac
+  case "$se" in *[!0-9]*) return 1 ;; esac
+  # New version drop clears the snooze.
+  [ "$sv" = "$remote_ver" ] || return 1
+  local dur
+  case "$sl" in
+    1) dur=86400 ;;
+    2) dur=172800 ;;
+    *) dur=604800 ;;
+  esac
+  local now expires
+  now="$(date +%s)"
+  expires=$(( se + dur ))
+  [ "$now" -lt "$expires" ]
+}
+
+# Step 4: cache — UP_TO_DATE 60 min, UPGRADE_AVAILABLE 12 hours.
+if [ -f "$CACHE_FILE" ]; then
+  CACHED="$(cat "$CACHE_FILE" 2>/dev/null || true)"
+  case "$CACHED" in
+    UP_TO_DATE*)        TTL=60 ;;
+    UPGRADE_AVAILABLE*) TTL=720 ;;
+    *)                  TTL=0 ;;
+  esac
+  STALE=$(find "$CACHE_FILE" -mmin +"$TTL" 2>/dev/null || true)
+  if [ -z "$STALE" ] && [ "$TTL" -gt 0 ]; then
+    case "$CACHED" in
+      UP_TO_DATE*)
+        CV="$(echo "$CACHED" | awk '{print $2}')"
+        [ "$CV" = "$LOCAL" ] && exit 0
+        ;;
+      UPGRADE_AVAILABLE*)
+        CO="$(echo "$CACHED" | awk '{print $2}')"
+        if [ "$CO" = "$LOCAL" ]; then
+          CN="$(echo "$CACHED" | awk '{print $3}')"
+          check_snooze "$CN" && exit 0
+          echo "$CACHED"
+          exit 0
+        fi
+        ;;
+    esac
+  fi
+fi
+
+# Step 5: slow path — fetch latest from npm registry.
+mkdir -p "$STATE_DIR"
+RESP="$(curl -fsSL --max-time 5 "$REMOTE_URL" 2>/dev/null || true)"
+# Extract "version":"X.Y.Z" without jq.
+REMOTE="$(echo "$RESP" | grep -oE '"version"[[:space:]]*:[[:space:]]*"[^"]+"' | head -1 | sed -E 's/.*"([^"]+)"$/\1/')"
+REMOTE="$(echo "$REMOTE" | tr -d '[:space:]')"
+
+# Reject anything that doesn't look like a semver number.
+if ! echo "$REMOTE" | grep -qE '^[0-9]+\.[0-9]+\.[0-9]+'; then
+  echo "UP_TO_DATE $LOCAL" > "$CACHE_FILE"
+  exit 0
+fi
+
+if [ "$LOCAL" = "$REMOTE" ]; then
+  echo "UP_TO_DATE $LOCAL" > "$CACHE_FILE"
+  exit 0
+fi
+
+echo "UPGRADE_AVAILABLE $LOCAL $REMOTE" > "$CACHE_FILE"
+check_snooze "$REMOTE" && exit 0
+echo "UPGRADE_AVAILABLE $LOCAL $REMOTE"

package/install.js

@@ -27,7 +27,54 @@ const os = require('node:os');
 
 const VERSION = require('./package.json').version;
 const PACKAGE_ROOT = __dirname;
-const SKILLS_SRC = path.join(PACKAGE_ROOT, 'skills');
+const PKG_SKILLS = path.join(PACKAGE_ROOT, 'skills');
+const PKG_AGENTS = path.join(PACKAGE_ROOT, 'agents');
+
+// Installer-owned stable path. Mirrors gstack's ~/.claude/skills/gstack/
+// approach: package contents get copied here so symlinks target a path that
+// never moves, even when npm/npx wipes the original package directory.
+const VRUUM_ROOT = path.join(os.homedir(), '.vruum');
+const VRUUM_SKILLS = path.join(VRUUM_ROOT, 'skills');
+const VRUUM_AGENTS = path.join(VRUUM_ROOT, 'agents');
+const VRUUM_BIN = path.join(VRUUM_ROOT, 'bin');
+const VRUUM_VERSION_FILE = path.join(VRUUM_ROOT, 'VERSION');
+const PKG_BIN = path.join(PACKAGE_ROOT, 'bin');
+
+// Prelude prepended to every SKILL.md as it lands in ~/.vruum/skills/. Runs
+// an update check (1h cache), then gives Claude natural-language instructions
+// for how to react. Mirrors gstack's preamble pattern but injected at install
+// time rather than via a template-gen step.
+const SKILL_PRELUDE = `## Preamble (run first)
+
+\`\`\`bash
+_UPD=$(~/.vruum/bin/vruum-skills-update-check 2>/dev/null || true)
+[ -n "$_UPD" ] && echo "$_UPD" || true
+\`\`\`
+
+If output shows \`UPGRADE_AVAILABLE <old> <new>\`: read \`~/.vruum/skills/vruum-skills-upgrade/SKILL.md\` and follow the inline upgrade flow. If \`~/.vruum/config.yaml\` has \`auto_upgrade: true\`, run the upgrade silently; otherwise AskUserQuestion with four options — (A) upgrade now, (B) upgrade with changelog preview, (C) snooze, (D) skip this session. If user picks snooze, bump the snooze level in \`~/.vruum/update-snoozed\` (format: \`<new_version> <level> <unix_epoch>\`; level 1 = 24h, 2 = 48h, 3+ = 7d). Then continue with the skill.
+
+If output shows \`JUST_UPGRADED <from> <to>\`: tell the user "Running @vruum/skills v{to} (just updated!)" in one line, then continue.
+
+Otherwise proceed silently with the skill below.
+
+---
+`;
+
+function injectPrelude(skillDir) {
+  const skillFile = path.join(skillDir, 'SKILL.md');
+  if (!fs.existsSync(skillFile)) return;
+  const raw = fs.readFileSync(skillFile, 'utf8');
+  // Find end of YAML frontmatter. If missing, inject at top.
+  let insertAt = 0;
+  if (raw.startsWith('---\n')) {
+    const end = raw.indexOf('\n---\n', 4);
+    if (end !== -1) insertAt = end + 5;
+  }
+  const before = raw.slice(0, insertAt);
+  const after = raw.slice(insertAt);
+  const patched = before + '\n' + SKILL_PRELUDE + '\n' + after.replace(/^\n+/, '');
+  fs.writeFileSync(skillFile, patched);
+}
 
 // Known harness skill directories. Add a target here when a new harness
 // lands on a stable skill-dir convention.
@@ -90,13 +137,56 @@ other assistants that don't yet support MCP prompts.`);
 }
 
 function listAvailableSkills() {
-  if (!fs.existsSync(SKILLS_SRC)) return [];
+  if (!fs.existsSync(PKG_SKILLS)) return [];
   return fs
-    .readdirSync(SKILLS_SRC, { withFileTypes: true })
+    .readdirSync(PKG_SKILLS, { withFileTypes: true })
     .filter((entry) => entry.isDirectory())
     .map((entry) => entry.name);
 }
 
+function syncVruumRoot({ dryRun }) {
+  if (dryRun) {
+    const rows = [
+      `would sync ${PKG_SKILLS} -> ${VRUUM_SKILLS} (with auto-update prelude)`,
+    ];
+    if (fs.existsSync(PKG_AGENTS)) rows.push(`would sync ${PKG_AGENTS} -> ${VRUUM_AGENTS}`);
+    if (fs.existsSync(PKG_BIN)) rows.push(`would sync ${PKG_BIN} -> ${VRUUM_BIN}`);
+    rows.push(`would write ${VRUUM_VERSION_FILE} = ${VERSION}`);
+    return rows;
+  }
+  fs.mkdirSync(VRUUM_ROOT, { recursive: true });
+
+  // Skills — copy then inject prelude in-place on the ~/.vruum/ copy.
+  fs.rmSync(VRUUM_SKILLS, { recursive: true, force: true });
+  fs.cpSync(PKG_SKILLS, VRUUM_SKILLS, { recursive: true });
+  for (const skillName of listAvailableSkills()) {
+    injectPrelude(path.join(VRUUM_SKILLS, skillName));
+  }
+  const rows = [`synced ${VRUUM_SKILLS} (prelude injected)`];
+
+  if (fs.existsSync(PKG_AGENTS)) {
+    fs.rmSync(VRUUM_AGENTS, { recursive: true, force: true });
+    fs.cpSync(PKG_AGENTS, VRUUM_AGENTS, { recursive: true });
+    rows.push(`synced ${VRUUM_AGENTS}`);
+  }
+
+  // Bin scripts — update-check needs to land at a stable path and be exec.
+  if (fs.existsSync(PKG_BIN)) {
+    fs.rmSync(VRUUM_BIN, { recursive: true, force: true });
+    fs.cpSync(PKG_BIN, VRUUM_BIN, { recursive: true });
+    for (const entry of fs.readdirSync(VRUUM_BIN)) {
+      fs.chmodSync(path.join(VRUUM_BIN, entry), 0o755);
+    }
+    rows.push(`synced ${VRUUM_BIN}`);
+  }
+
+  // VERSION file — read by vruum-skills-update-check as the local version.
+  fs.writeFileSync(VRUUM_VERSION_FILE, VERSION + '\n');
+  rows.push(`wrote ${VRUUM_VERSION_FILE} = ${VERSION}`);
+
+  return rows;
+}
+
 function ensureTargetDir(target, dryRun) {
   if (fs.existsSync(target)) return { created: false };
   if (dryRun) return { created: 'would' };
@@ -159,7 +249,7 @@ function commandInstall({ targets: extraTargets, dryRun }) {
   const skills = listAvailableSkills();
   if (skills.length === 0) {
     throw new Error(
-      `No skills found under ${SKILLS_SRC}. This looks like a broken package.`
+      `No skills found under ${PKG_SKILLS}. This looks like a broken package.`
     );
   }
   const targets = detectTargets(extraTargets);
@@ -173,6 +263,8 @@ function commandInstall({ targets: extraTargets, dryRun }) {
     process.exit(1);
   }
 
+  const syncRows = syncVruumRoot({ dryRun });
+
   const summary = [];
   for (const target of targets) {
     const { created } = ensureTargetDir(target.dir, dryRun);
@@ -182,14 +274,18 @@ function commandInstall({ targets: extraTargets, dryRun }) {
       summary.push({ target: target.dir, detail: 'created target dir' });
     }
     for (const skillName of skills) {
-      const srcAbs = path.join(SKILLS_SRC, skillName);
+      const srcAbs = path.join(VRUUM_SKILLS, skillName);
       summary.push(linkSkill({ name: skillName, srcAbs, target: target.dir, dryRun }));
     }
   }
 
   const prefix = dryRun ? '[dry-run] ' : '';
   console.log(`${prefix}@vruum/skills v${VERSION}`);
-  console.log(`${prefix}skills source: ${SKILLS_SRC}`);
+  console.log(`${prefix}package source: ${PACKAGE_ROOT}`);
+  console.log(`${prefix}stable root:    ${VRUUM_ROOT}`);
+  for (const row of syncRows) {
+    console.log(`  ${prefix}${row}`);
+  }
   for (const target of targets) {
     console.log(`${prefix}target: ${target.dir}${target.autoDetected ? ' (auto)' : ''}`);
   }
@@ -213,19 +309,25 @@ function commandInstall({ targets: extraTargets, dryRun }) {
 function commandUninstall({ targets: extraTargets, dryRun }) {
   const skills = listAvailableSkills();
   const targets = detectTargets(extraTargets);
+  const prefix = dryRun ? '[dry-run] ' : '';
+  console.log(`${prefix}@vruum/skills v${VERSION} uninstall`);
+
   if (targets.length === 0) {
-    console.error('No AI harness skill directories detected. Nothing to remove.');
-    return;
+    console.error('No AI harness skill directories detected.');
   }
 
-  const prefix = dryRun ? '[dry-run] ' : '';
-  console.log(`${prefix}@vruum/skills v${VERSION} uninstall`);
+  // A symlink is "ours" if it points into ~/.vruum/skills/. We accept any
+  // target there (not just the current skill name) so stale links from
+  // renamed skills still get cleaned up.
+  const isOurLink = (linkTarget) => {
+    const resolved = path.resolve(linkTarget);
+    return resolved.startsWith(VRUUM_SKILLS + path.sep) || resolved === VRUUM_SKILLS;
+  };
 
   for (const target of targets) {
     console.log(`${prefix}target: ${target.dir}`);
     for (const skillName of skills) {
       const dst = path.join(target.dir, skillName);
-      const srcAbs = path.join(SKILLS_SRC, skillName);
       let existing = null;
       try {
         const lstat = fs.lstatSync(dst);
@@ -242,7 +344,7 @@ function commandUninstall({ targets: extraTargets, dryRun }) {
         console.log(`  ${prefix}not-installed  ${skillName}`);
         continue;
       }
-      if (existing.kind !== 'symlink' || existing.target !== srcAbs) {
+      if (existing.kind !== 'symlink' || !isOurLink(existing.target)) {
         console.log(`  ${prefix}skipped        ${skillName}  [not our symlink]`);
         continue;
       }
@@ -254,6 +356,33 @@ function commandUninstall({ targets: extraTargets, dryRun }) {
       }
     }
   }
+
+  // Only clean up our own subdirectories — ~/.vruum/ is a shared state dir
+  // (e.g. the .agents/ vruum-update-check keeps config.yaml + snooze state
+  // there, and both installers share that config).
+  for (const dir of [VRUUM_SKILLS, VRUUM_AGENTS, VRUUM_BIN]) {
+    if (!fs.existsSync(dir)) continue;
+    if (dryRun) {
+      console.log(`${prefix}would remove ${dir}`);
+    } else {
+      fs.rmSync(dir, { recursive: true, force: true });
+      console.log(`${prefix}removed ${dir}`);
+    }
+  }
+  if (fs.existsSync(VRUUM_VERSION_FILE)) {
+    if (dryRun) {
+      console.log(`${prefix}would remove ${VRUUM_VERSION_FILE}`);
+    } else {
+      fs.unlinkSync(VRUUM_VERSION_FILE);
+      console.log(`${prefix}removed ${VRUUM_VERSION_FILE}`);
+    }
+  }
+  // Best-effort rmdir the root if now empty; ignore ENOTEMPTY.
+  if (!dryRun && fs.existsSync(VRUUM_ROOT)) {
+    try { fs.rmdirSync(VRUUM_ROOT); } catch (err) {
+      if (err.code !== 'ENOTEMPTY' && err.code !== 'EEXIST') throw err;
+    }
+  }
 }
 
 function commandList({ targets: extraTargets }) {
@@ -273,7 +402,7 @@ function commandList({ targets: extraTargets }) {
     }
     for (const skillName of skills) {
       const dst = path.join(target.dir, skillName);
-      const srcAbs = path.join(SKILLS_SRC, skillName);
+      const srcAbs = path.join(VRUUM_SKILLS, skillName);
       try {
         const lstat = fs.lstatSync(dst);
         if (lstat.isSymbolicLink()) {

package/package.json

@@ -1,11 +1,12 @@
 {
   "name": "@vruum/skills",
-  "version": "0.2.0",
+  "version": "0.4.1",
   "description": "Vruum AI skills for Claude Code, Codex CLI, and any AI assistant with a skill directory. Pairs with the Vruum MCP server at https://api.vruum.ai/mcp.",
   "license": "MIT",
   "repository": {
     "type": "git",
-    "url": "https://github.com/vruum-gtm/skills.git"
+    "url": "https://github.com/vruum-gtm/vruum_ai.git",
+    "directory": ".agents"
   },
   "homepage": "https://vruum.ai",
   "bugs": {
@@ -18,9 +19,9 @@
     "install.js",
     "README.md",
     "LICENSE",
-    ".mcp.json",
     "skills/",
-    "agents/"
+    "agents/",
+    "bin/"
   ],
   "engines": {
     "node": ">=18"
@@ -34,5 +35,6 @@
     "sales",
     "outreach",
     "gtm"
-  ]
+  ],
+  "contentHash": "fc531edad0e9163122d472579d3f1a37b74201dd8041fe71056ca34671cf1c7f"
 }

package/skills/diagnose-reply/SKILL.md

@@ -1,6 +1,9 @@
 ---
 name: diagnose-reply
-description: "Diagnose why a reply happened — what worked or didn't in the outreach that triggered it. Use when: why did they reply, what worked, diagnose reply, reply diagnosis, analyze this reply, what caused this reply, reply analysis."
+description: >-
+  Diagnose why a reply happened — what worked or didn't in the outreach that
+  triggered it. Use when: why did they reply, what worked, diagnose reply, reply
+  diagnosis, analyze this reply, what caused this reply, reply analysis.
 ---
 
 # /diagnose-reply
@@ -9,9 +12,9 @@ You diagnose individual replies to understand what worked (or didn't) in the out
 
 ## Step 1: Identify the reply
 
-The operator will reference a person, a reply, or a conversation. Use `get_person_360` with `for_company` to load the full context: conversation thread, outreach plan, match analysis.
+The user will reference a person, a reply, or a conversation. Use `get_person_360` to load the full context: conversation thread, outreach plan, match analysis.
 
-If the operator doesn't specify a person, ask: "Which reply do you want to diagnose? Give me a name, company, or message."
+If the user doesn't specify a person, ask: "Which reply do you want to diagnose? Give me a name, company, or message."
 
 ## Step 2: Read the conversation
 
@@ -26,7 +29,7 @@ From the person_360 response, read the full conversation thread. Identify:
 
 ## Step 3: Diagnose
 
-Call `get_performance_metrics` with `for_company`, `view='funnel'`, and the segment_id to get segment-level reply rates by channel.
+Call `get_performance_metrics` with `view='funnel'` and the segment_id to get segment-level reply rates by channel.
 
 Synthesize a diagnosis: