@vruum/skills 0.5.3 → 0.6.1

package/README.md

@@ -13,7 +13,7 @@ Add to `~/.claude.json`:
 ```json
 {
   "mcpServers": {
-    "vruum-local": { "type": "http", "url": "https://api.vruum.ai/mcp" }
+    "vruum": { "type": "http", "url": "https://api.vruum.ai/mcp" }
   }
 }
 ```
@@ -22,23 +22,25 @@ Slash commands appear automatically once registered. You don't need this npm pac
 
 ### Codex CLI
 
-Add to `~/.codex/config.toml`:
+**Plugin (recommended)** — bundles the skills + Vruum MCP in one step:
 
-```toml
-[mcp_servers.vruum-local]
-url = "https://api.vruum.ai/mcp"
+```bash
+codex plugin marketplace add vruum-gtm/skills
+codex plugin add vruum@vruum-gtm
+codex mcp login vruum
 ```
 
-Then run this installer to bring the skill bundle into your Codex skills directory:
+**Manual / other harnesses** — register the MCP, then install the skills into the agent-standard skills dir:
 
-```bash
-npx @vruum/skills install
+```toml
+# ~/.codex/config.toml
+[mcp_servers.vruum]
+url = "https://api.vruum.ai/mcp"
 ```
 
-Detects `~/.codex/skills/` automatically. For other harnesses without a known path:
-
 ```bash
-npx @vruum/skills install --target /path/to/skills/dir
+npx @vruum/skills install                                # detects ~/.agents/skills/
+npx @vruum/skills install --target /path/to/skills/dir   # any other harness
 ```
 
 ### Cursor / VS Code Copilot / Cline
@@ -73,7 +75,7 @@ npx @vruum/skills install --target /path/to/skills/dir
 - `/yc-pipeline-fill` — YC harness source for /pipeline-fill. Scrapes YC's public Algolia index, extracts founder LinkedIn URLs, dedups, hands a candidate list to /pipeline-fill for deep research and import. Use when: YC pipeline fill, source from YC, fill segment with YC founders, sales nav dried up, source YC.
 - `/csv-pipeline-fill` — CSV harness source for /pipeline-fill. Reads a CSV, auto-detects headers, maps columns, hands off to /pipeline-fill for harness deep research and import. Use when: import CSV, paste a CSV, csv import, prospect list from CSV, csv harness mode.
 - `/create-content` — Co-produce an on-voice LinkedIn content post — pull your own signal, steer the angle conversationally, draft in your voice, then save as draft, schedule, or publish. Use when: write a post, draft LinkedIn content, create content, post about, content co-production, help me write a post.
-- `/segment-doctor` — Diagnose and fix struggling outreach segments. Use when: fix a segment, diagnose segment, why is my segment not working, segment health, low reply rate, check segments, which segments need help.
+- `/campaign-doctor` — Diagnose and fix struggling outreach campaigns. Use when: fix a campaign, diagnose campaign, why is my campaign not working, campaign health, low reply rate, check campaigns, which campaigns need help.
 - `/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.
 - `/winback-fill` — Source winback candidates from closed-lost deals or churned customers. Surfaces people who went silent or lost a deal >90 days ago, where the loss reason wasn't 'no_fit'. Use when: winback, win back churned, reactivate, revive cold deals, 90-day silent revival, lost deal recovery, lost customer outreach.
 <!-- generated:skills-end -->

package/install.js

@@ -78,9 +78,13 @@ function injectPrelude(skillDir) {
 
 // Known harness skill directories. Add a target here when a new harness
 // lands on a stable skill-dir convention.
+// `detect` = the harness's config dir (its presence means the harness is
+// installed); `dir` = where that harness actually reads skills from. Claude
+// Code reads ~/.claude/skills; Codex CLI (and other agents on the
+// agentskills.io standard) read ~/.agents/skills.
 const KNOWN_TARGETS = [
-  { name: 'Claude Code', dir: path.join(os.homedir(), '.claude', 'skills') },
-  { name: 'Codex CLI',   dir: path.join(os.homedir(), '.codex',  'skills') },
+  { name: 'Claude Code', detect: path.join(os.homedir(), '.claude'), dir: path.join(os.homedir(), '.claude', 'skills') },
+  { name: 'Codex CLI',   detect: path.join(os.homedir(), '.codex'),  dir: path.join(os.homedir(), '.agents', 'skills') },
 ];
 
 function parseArgs(argv) {
@@ -125,7 +129,7 @@ slash commands.
 
 Supported auto-detection:
   - Claude Code  ~/.claude/skills/
-  - Codex CLI    ~/.codex/skills/
+  - Codex CLI    ~/.agents/skills/
 
 Any other harness: pass --target <its skills directory>.
 
@@ -231,9 +235,11 @@ function linkSkill({ name, srcAbs, target, dryRun }) {
 
 function detectTargets(extraTargets) {
   const targets = [];
-  // Auto-detect only when the skills directory itself already exists.
+  // Auto-detect only when the harness's config dir exists (the skills dir may
+  // not exist yet — e.g. ~/.agents/skills for a fresh Codex user — and gets
+  // created at link time).
   for (const known of KNOWN_TARGETS) {
-    if (fs.existsSync(known.dir)) {
+    if (fs.existsSync(known.detect)) {
       targets.push({ ...known, autoDetected: true });
     }
   }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vruum/skills",
-  "version": "0.5.3",
+  "version": "0.6.1",
   "description": "Vruum AI skills for Claude Code, Claude Desktop, Codex CLI, and any AI assistant with a skill directory. Slash commands for outreach triage, engagement triage, pipeline filling, prospect enrichment, and reply diagnosis. Pairs with the Vruum MCP server at https://api.vruum.ai/mcp.",
   "license": "MIT",
   "repository": {
@@ -36,5 +36,5 @@
     "outreach",
     "gtm"
   ],
-  "contentHash": "b612084d29f288715842a2c9527811f6db59778759c9cb918819f84d10ca5d30"
+  "contentHash": "4bcdec8d3e471c8e08561b920faafca0c170aa2966ff5683576545aa2723b2f1"
 }

package/skills/{segment-doctor → campaign-doctor}/SKILL.md

@@ -1,20 +1,10 @@
 ---
-name: segment-doctor
+name: campaign-doctor
 description: >-
-  Diagnose and fix struggling outreach segments. Use when: fix a segment,
-  diagnose segment, why is my segment not working, segment health, low reply
-  rate, check segments, which segments need help.
+  Diagnose and fix struggling outreach campaigns. Use when: fix a campaign,
+  diagnose campaign, why is my campaign not working, campaign health, low reply
+  rate, check campaigns, which campaigns need help.
 ---
-
-## Auto-update check
-
-Before starting, run `~/.vruum/bin/vruum-skills-update-check` (path relative to this repo). Interpret output:
-- `UPGRADE_AVAILABLE <old> <new>` → mention the available upgrade in one line and offer `/vruum-upgrade`. Then continue.
-- `JUST_UPGRADED <old> <new>` → acknowledge in one line, then continue.
-- Empty → proceed silently.
-
-Never block skill execution on this check.
-
 # Segment Doctor
 
 You are a segment diagnostics and optimization agent. Your job is to identify struggling segments, diagnose root causes, and recommend (or apply) fixes.
@@ -23,21 +13,21 @@ You are a segment diagnostics and optimization agent. Your job is to identify st
 
 ### Step 1: Triage — health + trends
 
-Call `get_segments` to list all segments. For each segment, dispatch three calls in parallel:
-- `diagnose_segment(segment_id=X)` — returns `health_score` (0–100), reply-rate vs company average, and ranked root causes (targeting, messaging, channel, saturation, cadence, timing).
-- `get_performance_metrics(view='funnel', segment_id=X, start_date=<today_utc - 6d>, end_date=<today_utc + 1d>)` — current 7-day window (7 full days ending today, inclusive).
-- `get_performance_metrics(view='funnel', segment_id=X, start_date=<today_utc - 13d>, end_date=<today_utc - 7d>)` — prior 7-day window (7 full days ending the day before current starts — no shared days).
+Call `get_campaigns` to list all segments. For each segment, dispatch three calls in parallel:
+- `diagnose_campaign(campaign_id=X)` — returns `health_score` (0–100), reply-rate vs company average, and ranked root causes (targeting, messaging, channel, saturation, cadence, timing).
+- `get_performance_metrics(view='funnel', campaign_id=X, start_date=<today_utc - 6d>, end_date=<today_utc + 1d>)` — current 7-day window (7 full days ending today, inclusive).
+- `get_performance_metrics(view='funnel', campaign_id=X, start_date=<today_utc - 13d>, end_date=<today_utc - 7d>)` — prior 7-day window (7 full days ending the day before current starts — no shared days).
 
 Use **UTC** dates in `YYYY-MM-DD` format. The backend filters use inclusive `gte(start_date)` + `lte(end_date)` against timestamp columns — so passing `end_date = today_utc + 1d` captures all of today's activity (timestamps < tomorrow 00:00 UTC), and the current/prior windows share no days. Example: if today (UTC) is 2026-04-22, current = `(2026-04-16, 2026-04-23)`, prior = `(2026-04-09, 2026-04-15)`.
 
-If `get_segments` returns no segments, tell the user "No segments yet — create one in the Vruum app before running diagnosis" and stop.
+If `get_campaigns` returns no segments, tell the user "No segments yet — create one in the Vruum app before running diagnosis" and stop.
 
-Classify each segment by reply rate (from `diagnose_segment` output). Reply rate is a **diagnostic triage proxy** here — it cheaply flags which segments to look at. It is not segment health itself: the objective is client revenue, and a segment can post a strong reply rate while producing no deals (or a weak one while closing). Treat the band as "where to point the diagnosis," and in the operator flow always reconcile it against meetings and the downstream signal (Block 14 below) before calling a segment healthy.
+Classify each segment by reply rate (from `diagnose_campaign` output). Reply rate is a **diagnostic triage proxy** here — it cheaply flags which segments to look at. It is not segment health itself: the objective is client revenue, and a segment can post a strong reply rate while producing no deals (or a weak one while closing). Treat the band as "where to point the diagnosis," and in the operator flow always reconcile it against meetings and the downstream signal (Block 14 below) before calling a segment healthy.
 
 - **CRITICAL** — 30-day reply rate < 5% with ≥20 sent
 - **WARNING** — 30-day reply rate 5–10% with ≥20 sent
 - **HEALTHY** — 30-day reply rate ≥ 10% (reply-rate-healthy — confirm it also produces meetings/deals before treating it as truly healthy)
-- **INSUFFICIENT DATA** — `diagnose_segment` returned `insufficient_data: true` (fewer than 20 sent in 30d)
+- **INSUFFICIENT DATA** — `diagnose_campaign` returned `insufficient_data: true` (fewer than 20 sent in 30d)
 
 For WoW delta, compute `(current_reply_rate - prior_reply_rate) / prior_reply_rate`. Guards:
 - **Brand-new segment** (prior window sent = 0): show "new segment, WoW N/A".
@@ -67,11 +57,11 @@ Want me to diagnose the critical and warning segments?"
 Key behaviors:
 - Never auto-diagnose `insufficient_data` segments. They need more volume first.
 - If `get_performance_metrics` returns an empty funnel for the prior window, treat it as "new segment, WoW N/A" (not -100%).
-- If the funnel is empty for the current window too, fall back to the 30-day reply rate from `diagnose_segment` output — don't show a fake zero.
+- If the funnel is empty for the current window too, fall back to the 30-day reply rate from `diagnose_campaign` output — don't show a fake zero.
 
 ### Step 2: Diagnose root causes
 
-For each segment the user wants to diagnose, you already have the `diagnose_segment` output from Step 1's parallel calls. Present the findings:
+For each segment the user wants to diagnose, you already have the `diagnose_campaign` output from Step 1's parallel calls. Present the findings:
 
 "**'IT Directors'** — Health score: 25/100
 
@@ -91,18 +81,18 @@ Root causes (ranked):
 Want me to apply any of these fixes?"
 
 Key behaviors:
-- If `diagnose_segment` returned `insufficient_data`, surface the tool's own `message` field verbatim. Don't re-derive the threshold logic.
+- If `diagnose_campaign` returned `insufficient_data`, surface the tool's own `message` field verbatim. Don't re-derive the threshold logic.
 - When multiple segments share the same root cause dimension (e.g., all have messaging issues), recommend a cross-segment fix first.
 
 ### Step 3: Apply fixes (with approval)
 
 For each recommended fix the user approves:
 
-- **Targeting fix**: Suggest specific ICP field changes and call `update_segment` with new `target_titles`, `target_industries`, or `positioning_angle`.
+- **Targeting fix**: Suggest specific ICP field changes and call `update_campaign` with new `target_titles`, `target_industries`, or `positioning_angle`.
 
-- **Messaging fix**: Suggest revised `ai_tone_instructions` or `ai_selling_strategy` and call `update_segment`.
+- **Messaging fix**: Suggest revised `ai_tone_instructions` or `ai_selling_strategy` and call `update_campaign`.
 
-- **Channel fix**: Call `update_segment` with adjusted `allowed_channels`.
+- **Channel fix**: Call `update_campaign` with adjusted `allowed_channels`.
 
 - **Saturation fix (recommend only)**: The client flow doesn't manage pipeline sources directly. Instead:
   1. Explain the saturation issue in plain terms ("your saved search is drying up — fewer new profiles available each day than your target").
@@ -120,12 +110,12 @@ After all fixes are applied:
 - 'VP Engineering': Updated tone instructions
 - 'CFO Northeast': Suggested broader saved search; run /pipeline-fill once updated
 
-Monitor results over the next 7 days. Run /segment-doctor again next week to check progress."
+Monitor results over the next 7 days. Run /campaign-doctor again next week to check progress."
 
 ## Notes
 
-- `diagnose_segment` requires 20+ sent touches in 30 days for meaningful analysis. For newer segments, wait — do not attempt diagnosis.
-- Reply-rate thresholds for health bands match `diagnose_segment.health_score` output: <30 ≈ CRITICAL, 30–75 ≈ WARNING, ≥75 ≈ HEALTHY (see `health_score` field).
-- WoW comparison uses two `get_performance_metrics(view='funnel', segment_id=X)` calls — **always UTC dates in YYYY-MM-DD**, current = `(today-7d, today)`, prior = `(today-14d, today-7d)`. If prior-window sent < 5, show "low volume — WoW unreliable" instead of a percentage.
+- `diagnose_campaign` requires 20+ sent touches in 30 days for meaningful analysis. For newer segments, wait — do not attempt diagnosis.
+- Reply-rate thresholds for health bands match `diagnose_campaign.health_score` output: <30 ≈ CRITICAL, 30–75 ≈ WARNING, ≥75 ≈ HEALTHY (see `health_score` field).
+- WoW comparison uses two `get_performance_metrics(view='funnel', campaign_id=X)` calls — **always UTC dates in YYYY-MM-DD**, current = `(today-7d, today)`, prior = `(today-14d, today-7d)`. If prior-window sent < 5, show "low volume — WoW unreliable" instead of a percentage.
 - Root causes are ranked by severity. Focus on the highest-severity issues first.
 - Saturation fixes in the client flow are text recommendations only — clients cannot manage pipeline sources directly via MCP; they adjust Sales Nav and run `/pipeline-fill`.

package/skills/create-content/SKILL.md

@@ -6,7 +6,6 @@ description: >-
   publish. Use when: write a post, draft LinkedIn content, create content, post
   about, content co-production, help me write a post.
 ---
-
 # /create-content
 
 You co-produce a LinkedIn post in the seller's own voice. This is a conversation, not a one-shot generator: you pull the seller's real signal (their calls, posts, notes, knowledge), surface what's there, let them steer the angle, draft on-voice, and then save it the way they want — draft, scheduled, or (only on explicit confirmation) published.

package/skills/csv-pipeline-fill/SKILL.md

@@ -6,16 +6,6 @@ description: >-
   when: import CSV, paste a CSV, csv import, prospect list from CSV, csv harness
   mode.
 ---
-
-## Auto-update check
-
-Before starting, run `~/.vruum/bin/vruum-skills-update-check` (path relative to this repo). Interpret output:
-- `UPGRADE_AVAILABLE <old> <new>` → mention the available upgrade in one line and offer `/vruum-upgrade`. Then continue.
-- `JUST_UPGRADED <old> <new>` → acknowledge in one line, then continue.
-- Empty → proceed silently.
-
-Never block skill execution on this check.
-
 # CSV Pipeline Fill (harness source)
 
 You are the CSV harness-mode source for `/pipeline-fill`. You read a CSV the operator provides (Apollo export, ZoomInfo, hand-built spreadsheet, LinkedIn export — anything), normalize columns to the canonical candidate-list shape, and hand off to the orchestrator.

package/skills/deal-triage/SKILL.md

@@ -6,16 +6,6 @@ description: >-
   review deals, triage deals, check pipeline, deal review, morning deals,
   pipeline review, deal health, at-risk deals.
 ---
-
-## Auto-update check
-
-Before starting, run `~/.vruum/bin/vruum-skills-update-check` (path relative to this repo). Interpret output:
-- `UPGRADE_AVAILABLE <old> <new>` → mention the available upgrade in one line and offer `/vruum-upgrade`. Then continue.
-- `JUST_UPGRADED <old> <new>` → acknowledge in one line, then continue.
-- Empty → proceed silently.
-
-Never block skill execution on this check.
-
 # Deal Triage
 
 You are a deal pipeline orchestrator. Your job is to efficiently review the seller's active deals by dispatching subagents that do deep deal analysis (timeline, stakeholders, MEDDIC qualification), then presenting structured results back to the seller for decisions.

package/skills/diagnose-reply/SKILL.md

@@ -5,16 +5,6 @@ description: >-
   triggered it. Use when: why did they reply, what worked, diagnose reply, reply
   diagnosis, analyze this reply, what caused this reply, reply analysis.
 ---
-
-## Auto-update check
-
-Before starting, run `~/.vruum/bin/vruum-skills-update-check` (path relative to this repo). Interpret output:
-- `UPGRADE_AVAILABLE <old> <new>` → mention the available upgrade in one line and offer `/vruum-upgrade`. Then continue.
-- `JUST_UPGRADED <old> <new>` → acknowledge in one line, then continue.
-- Empty → proceed silently.
-
-Never block skill execution on this check.
-
 # /diagnose-reply
 
 You diagnose individual replies to understand what worked (or didn't) in the outreach that preceded them. This turns every reply into a learning event.

package/skills/engagement-triage/SKILL.md

@@ -6,16 +6,6 @@ description: >-
   warming comments, review nurture reactions, review marketing comments, review
   content drafts, check engagement queue.
 ---
-
-## Auto-update check
-
-Before starting, run `~/.vruum/bin/vruum-skills-update-check` (path relative to this repo). Interpret output:
-- `UPGRADE_AVAILABLE <old> <new>` → mention the available upgrade in one line and offer `/vruum-upgrade`. Then continue.
-- `JUST_UPGRADED <old> <new>` → acknowledge in one line, then continue.
-- Empty → proceed silently.
-
-Never block skill execution on this check.
-
 ## MCP smoke test (run early)
 
 Before triaging, confirm Vruum MCP is reachable. Call `get_marketing_overview` as a lightweight liveness check. On failure, surface this error and stop:

package/skills/enrich-prospect/SKILL.md

@@ -6,16 +6,6 @@ description: >-
   profile this person, who is this person, research prospect, diarize prospect,
   prospect briefing.
 ---
-
-## Auto-update check
-
-Before starting, run `~/.vruum/bin/vruum-skills-update-check` (path relative to this repo). Interpret output:
-- `UPGRADE_AVAILABLE <old> <new>` → mention the available upgrade in one line and offer `/vruum-upgrade`. Then continue.
-- `JUST_UPGRADED <old> <new>` → acknowledge in one line, then continue.
-- Empty → proceed silently.
-
-Never block skill execution on this check.
-
 # /enrich-prospect
 
 You diarize a prospect. Read everything available — LinkedIn, company research, match analysis, conversation history, knowledge base — and synthesize a one-page structured profile that reveals the gap between what the data says and what's actually going on.

package/skills/expansion-fill/SKILL.md

@@ -6,14 +6,6 @@ description: >-
   Use when: expand customer, find upsell opportunities, NRR play, expansion
   opportunities, customers ripe for expansion, who can we expand to.
 ---
-
-## Auto-update check
-
-Before starting, run `~/.vruum/bin/vruum-skills-update-check`. Interpret output:
-- `UPGRADE_AVAILABLE <old> <new>` → mention upgrade in one line, offer `/vruum-upgrade`, continue.
-- `JUST_UPGRADED <old> <new>` → acknowledge in one line, continue.
-- Empty → proceed silently.
-
 # Expansion Fill
 
 You are an expansion-side pipeline filler. While `/pipeline-fill` sources cold prospects, this skill surfaces *existing customers* who are due for an expansion conversation — new product, larger seat count, multi-team rollout, renewal-with-uplift, etc.

package/skills/outreach-triage/SKILL.md

@@ -5,16 +5,6 @@ description: >-
   when: triage, review queue, morning review, check messages, approve outreach,
   what needs review.
 ---
-
-## Auto-update check
-
-Before starting, run `~/.vruum/bin/vruum-skills-update-check` (path relative to this repo). Interpret output:
-- `UPGRADE_AVAILABLE <old> <new>` → mention the available upgrade in one line and offer `/vruum-upgrade`. Then continue.
-- `JUST_UPGRADED <old> <new>` → acknowledge in one line, then continue.
-- Empty → proceed silently.
-
-Never block skill execution on this check.
-
 # Outreach Triage
 
 You are an outreach queue orchestrator. Your job is to efficiently process pending outreach messages by dispatching subagents who do review, research, and editing, then presenting results for approval.

package/skills/pipeline-fill/RESEARCH-ENGINE.md

@@ -41,7 +41,7 @@ Before any other Step 3 work, call `get_research_playbook(segment_id=<id>)`. If
 
 > Vruum MCP not configured as a user-scoped server. Run:
 >
-> Register the Vruum MCP server in your assistant once: Claude Code → `~/.claude.json` `mcpServers.vruum-local = {"type":"http","url":"https://api.vruum.ai/mcp"}`; Codex CLI → `~/.codex/config.toml` `[mcp_servers.vruum-local]` with `url = "https://api.vruum.ai/mcp"`; other assistants → connect to `https://api.vruum.ai/mcp` (HTTP, OAuth via standard MCP flow).
+> Register the Vruum MCP server in your assistant once: Claude Code → `~/.claude.json` `mcpServers.vruum = {"type":"http","url":"https://api.vruum.ai/mcp"}`; Codex CLI → `~/.codex/config.toml` `[mcp_servers.vruum]` with `url = "https://api.vruum.ai/mcp"`; other assistants → connect to `https://api.vruum.ai/mcp` (HTTP, OAuth via standard MCP flow).
 >
 > and retry. (The cloud `claude.ai Vruum` connector doesn't propagate to subagents — they need `vruum` configured at the user scope in `~/.claude.json`.)
 

package/skills/pipeline-fill/SKILL.md

@@ -7,16 +7,6 @@ description: >-
   gate. Use when: fill pipeline, import prospects, daily imports, need more
   prospects, discover prospects from scratch, deep research before import.
 ---
-
-## Auto-update check
-
-Before starting, run `~/.vruum/bin/vruum-skills-update-check` (path relative to this repo). Interpret output:
-- `UPGRADE_AVAILABLE <old> <new>` → mention the available upgrade in one line and offer `/vruum-upgrade`. Then continue.
-- `JUST_UPGRADED <old> <new>` → acknowledge in one line, then continue.
-- Empty → proceed silently.
-
-Never block skill execution on this check.
-
 # Pipeline Fill
 
 You are a source-agnostic pipeline filler. You pick segments to fill, pick a source per segment (Sales Nav / YC / CSV / discovery), and orchestrate harness deep research that gates against the segment ICP before saving prospects into the backend pipeline.
@@ -45,8 +35,8 @@ This skill uses two subagents (defined in `.claude/agents/`):
 
 Subagents need access to the Vruum MCP server. Register it once in your AI assistant:
 
-- **Claude Code**: `~/.claude.json` → `mcpServers.vruum-local` = `{"type": "http", "url": "https://api.vruum.ai/mcp"}`
-- **Codex CLI**: `~/.codex/config.toml` → `[mcp_servers.vruum-local]` with `url = "https://api.vruum.ai/mcp"`
+- **Claude Code**: `~/.claude.json` → `mcpServers.vruum` = `{"type": "http", "url": "https://api.vruum.ai/mcp"}`
+- **Codex CLI**: `~/.codex/config.toml` → `[mcp_servers.vruum]` with `url = "https://api.vruum.ai/mcp"`
 - **Other**: connect to `https://api.vruum.ai/mcp` (HTTP, OAuth via standard MCP flow)
 
 The orchestrator's MCP precheck at the top of Step 3 (`get_research_playbook` call) catches misconfiguration upfront. Don't skip it.
@@ -66,7 +56,7 @@ The orchestrator's MCP precheck at the top of Step 3 (`get_research_playbook` ca
 
 ## Workflow — Step 1: Show pipeline status & pick segments
 
-Call `manage_sales_nav_searches(action="list")` + `get_outreach_stats` for queue depth + `get_segments` for non-Sales-Nav segments. Present a numbered table with **per-segment ETA**:
+Call `manage_sales_nav_searches(action="list")` + `get_outreach_stats` for queue depth + `get_campaigns` for non-Sales-Nav segments. Present a numbered table with **per-segment ETA**:
 
 ```
 Pipeline status:
@@ -137,13 +127,13 @@ Drop blank lines and lines starting with `#` (treat as comments).
 **Path B — operator describes an ICP** (you want the harness to discover candidates)
 Operator gives a brief like "Series A-C SaaS founders, US, 50-500 ppl" or "directors of operations at MSPs in DFW, recently posted about hiring". Harness sources candidates from scratch:
 
-1. **Anchor on segment ICP** — read the segment's existing ICP/company profile (via `get_segment` and `get_company_profile`) and merge with the operator's brief. Show a one-line synthesis ("OK so: Series A-C SaaS, US, 50-500 ppl, founder/CEO/CTO titles") and confirm before sourcing.
+1. **Anchor on segment ICP** — read the segment's existing ICP/company profile (via `get_campaign` and `get_company_profile`) and merge with the operator's brief. Show a one-line synthesis ("OK so: Series A-C SaaS, US, 50-500 ppl, founder/CEO/CTO titles") and confirm before sourcing.
 2. **Source companies first** — use harness tools to find candidate companies matching the brief:
    - `WebSearch` for funding announcements, news, lists ("Series A SaaS 2026", "TechCrunch Series B SaaS announcements")
    - `WebFetch` on Crunchbase / PitchBook / company directories
-   - `mcp__vruum-local__search_linkedin_people` for company-fitting roles when the brief is people-shaped (e.g. "VPs of Eng at Series A SaaS")
-3. **Source people from each company** — for each candidate company, use `mcp__vruum-local__find_people_at_company` (Unipile-backed; respects LinkedIn rate limits) to find titles matching the segment ICP. Cap at ~5 people per company to spread the discovery surface.
-4. **Dedup against existing pipeline** — for each discovered person, check `mcp__vruum-local__search_existing_people` so you don't research someone the segment already has.
+   - `mcp__vruum__search_linkedin_people` for company-fitting roles when the brief is people-shaped (e.g. "VPs of Eng at Series A SaaS")
+3. **Source people from each company** — for each candidate company, use `mcp__vruum__find_people_at_company` (Unipile-backed; respects LinkedIn rate limits) to find titles matching the segment ICP. Cap at ~5 people per company to spread the discovery surface.
+4. **Dedup against existing pipeline** — for each discovered person, check `mcp__vruum__search_existing_people` so you don't research someone the segment already has.
 5. **Show the discovered list to the operator** before handoff. Format: `Name (title) — Company [linkedin]`. Cap the surface at 2x daily_target so we don't over-source. Get a "go" / "drop X" before continuing.
 
 Discovery-path candidates produced in either path use the canonical shape in `RESEARCH-ENGINE.md` and feed into Step 3 the same way.

package/skills/sales-nav-deep-fill/SKILL.md

@@ -6,16 +6,6 @@ description: >-
   /pipeline-fill for deep research and import. Use when: sales nav with deep
   research, sales nav harness mode, in-chat sales nav.
 ---
-
-## Auto-update check
-
-Before starting, run `~/.vruum/bin/vruum-skills-update-check` (path relative to this repo). Interpret output:
-- `UPGRADE_AVAILABLE <old> <new>` → mention the available upgrade in one line and offer `/vruum-upgrade`. Then continue.
-- `JUST_UPGRADED <old> <new>` → acknowledge in one line, then continue.
-- Empty → proceed silently.
-
-Never block skill execution on this check.
-
 # Sales Nav Deep Fill (harness source)
 
 You are the Sales Nav harness-mode source for `/pipeline-fill`. You produce a candidate list from a Sales Nav saved search and hand off to the orchestrator for deep research, harness gate, and save chain.

package/skills/winback-fill/SKILL.md

@@ -7,14 +7,6 @@ description: >-
   revive cold deals, 90-day silent revival, lost deal recovery, lost customer
   outreach.
 ---
-
-## Auto-update check
-
-Before starting, run `~/.vruum/bin/vruum-skills-update-check`. Interpret output:
-- `UPGRADE_AVAILABLE <old> <new>` → mention upgrade in one line, offer `/vruum-upgrade`, continue.
-- `JUST_UPGRADED <old> <new>` → acknowledge in one line, continue.
-- Empty → proceed silently.
-
 # Winback Fill
 
 You are a winback-side pipeline filler. While `/expansion-fill` targets won-and-quiet customers, this skill surfaces *lost or churned* relationships where re-engagement is still plausible.

package/skills/yc-pipeline-fill/SKILL.md

@@ -6,16 +6,6 @@ description: >-
   /pipeline-fill for deep research and import. Use when: YC pipeline fill,
   source from YC, fill segment with YC founders, sales nav dried up, source YC.
 ---
-
-## Auto-update check
-
-Before starting, run `~/.vruum/bin/vruum-skills-update-check` (path relative to this repo). Interpret output:
-- `UPGRADE_AVAILABLE <old> <new>` → mention the available upgrade in one line and offer `/vruum-upgrade`. Then continue.
-- `JUST_UPGRADED <old> <new>` → acknowledge in one line, then continue.
-- Empty → proceed silently.
-
-Never block skill execution on this check.
-
 # YC Pipeline Fill (harness source)
 
 You are the YCombinator harness-mode source for `/pipeline-fill`. You scrape YC's public directory, extract founder LinkedIn URLs, dedup, and hand a candidate list to the orchestrator. No deep research, no harness gate, no save chain in this skill — that's all in `pipeline-fill/RESEARCH-ENGINE.md`.