@vruum/skills 0.6.30 → 0.6.32

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "vruum",
-  "version": "0.6.30",
+  "version": "0.6.32",
   "description": "Vruum AI skills + remote MCP server for B2B GTM teams. Slash commands for outreach triage, engagement triage, pipeline filling, prospect enrichment, and reply diagnosis, paired with the full Vruum MCP tool surface over OAuth 2.1.",
   "author": {
     "name": "Vruum AI",

package/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "vruum",
-  "version": "0.6.30",
+  "version": "0.6.32",
   "description": "Vruum AI skills + remote MCP server for B2B GTM teams. Skills for outreach triage, engagement triage, pipeline filling, prospect enrichment, and reply diagnosis, paired with the full Vruum MCP tool surface over OAuth 2.1.",
   "author": {
     "name": "Vruum AI",

package/install.js

@@ -86,6 +86,7 @@ const KNOWN_TARGETS = [
   { 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') },
 ];
+const LEGACY_CODEX_SKILLS_DIR = path.join(os.homedir(), '.codex', 'skills');
 
 function parseArgs(argv) {
   const args = { command: 'install', targets: [], dryRun: false, help: false };
@@ -243,6 +244,14 @@ function pruneStaleLinks({ target, skills, dryRun }) {
   return results;
 }
 
+// Older releases linked Codex skills into ~/.codex/skills. Modern Codex also
+// scans ~/.agents/skills, so an upgrade otherwise leaves duplicate skills in
+// two registries. Reuse the ownership predicate and remove every public-bundle
+// link from the legacy directory while preserving operator and user links.
+function pruneLegacyCodexLinks({ dryRun }) {
+  return pruneStaleLinks({ target: LEGACY_CODEX_SKILLS_DIR, skills: [], dryRun });
+}
+
 function ensureTargetDir(target, dryRun) {
   if (fs.existsSync(target)) return { created: false };
   if (dryRun) return { created: 'would' };
@@ -342,6 +351,14 @@ function commandInstall({ targets: extraTargets, dryRun }) {
     }
   }
 
+  // Only remove the legacy copy after every canonical target reconciles. If a
+  // non-symlink collision blocks any current skill, keep the legacy links so a
+  // failed migration cannot turn duplicate skills into missing skills.
+  const skipped = summary.filter((row) => row.action === 'skipped');
+  if (skipped.length === 0) {
+    summary.push(...pruneLegacyCodexLinks({ dryRun }));
+  }
+
   const prefix = dryRun ? '[dry-run] ' : '';
   console.log(`${prefix}@vruum/skills v${VERSION}`);
   console.log(`${prefix}package source: ${PACKAGE_ROOT}`);
@@ -361,7 +378,6 @@ function commandInstall({ targets: extraTargets, dryRun }) {
     console.log(`  ${prefix}${label} ${row.name}${row.reason ? `  [${row.reason}]` : ''}`);
   }
 
-  const skipped = summary.filter((row) => row.action === 'skipped');
   if (skipped.length > 0) {
     console.log('');
     console.log(`Skipped ${skipped.length} skill(s); remove the conflicting file(s) and re-run.`);
@@ -378,6 +394,11 @@ function commandUninstall({ targets: extraTargets, dryRun }) {
     console.error('No AI harness skill directories detected.');
   }
 
+  for (const row of pruneLegacyCodexLinks({ dryRun })) {
+    const action = dryRun ? 'would-remove' : 'removed';
+    console.log(`  ${prefix}${action.padEnd(15)} ${row.name} (legacy ~/.codex/skills link)`);
+  }
+
   // Scan each target dir and remove every symlink we own — not just the
   // current skill names — so stale links left by renamed/removed skills are
   // cleaned up too. Foreign symlinks and non-symlinks are left untouched
@@ -523,6 +544,7 @@ module.exports = {
   linkSkill,
   isOurLink,
   pruneStaleLinks,
+  pruneLegacyCodexLinks,
   commandInstall,
   commandUninstall,
   commandList,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vruum/skills",
-  "version": "0.6.30",
+  "version": "0.6.32",
   "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": {
@@ -42,5 +42,5 @@
     "outreach",
     "gtm"
   ],
-  "contentHash": "edb317856c2825036b1d3d8017b14b908386a977b3d0f05efc61e0db0cee7762"
+  "contentHash": "1260466ed188fc52cb23f0c351c8bc175a7e0560ec62237f4d4e411a9972e7f4"
 }

package/skills/vruum-guide/SKILL.md

@@ -11,14 +11,14 @@ description: >-
 
 You are the guide to the seller's revenue engine. You do three things, in order: **orient** (show them where their revenue engine stands today, in their numbers), **recommend** (the single next most valuable action), and **hand off** (invoke the skill that does it, narrating as it works). You are a tour guide, not a textbook: lesson content lives in the specialist skills, never duplicated here.
 
-**The one rule that overrides everything: every session ends with something real shipped** — a profile completed, a campaign created, a queue cleared, a first draft reviewed. Never end a session on explanation alone.
+**The one rule that overrides everything: every session ends with something real shipped** — a profile completed, a buying hypothesis produced, a campaign created, a post drafted, a queue cleared, a deal advanced, or an account play approved. Never end a session on explanation alone.
 
 ## Step 0: Load progress
 
 Read `~/.vruum/guide-state.json` if it exists (create the directory if needed). Shape:
 
 ```json
-{"milestones": {"profile": null, "channels": null, "first_campaign": null, "first_import": null, "first_drafts": null, "first_review": null}, "last_session": null, "notes": ""}
+{"milestones": {"profile": null, "chosen_motion": null, "first_result": null, "channels": null, "first_campaign": null, "first_import": null, "first_drafts": null, "first_review": null}, "last_session": null, "notes": ""}
 ```
 
 Missing file = brand-new user. Update the file at the end of every session (stamp completed milestones with ISO dates, set `last_session`, leave yourself a one-line note for next time).
@@ -33,29 +33,31 @@ Build "your revenue engine today" from live reads — never from memory or assum
 - `search` type=people limit=1 filters={research_status: "all"} → total contacts (read the total, not the rows)
 - `search` type=deals limit=5 → deal pipeline existence
 - `fetch` type=stats subtype=outreach → sends, replies, meetings
+- `search` type=content → whether an organic content motion is active
 
-Present a compact snapshot (5-8 lines, their numbers), positioned on the bowtie map (Step 2). If the company record or knowledge base shows a referral source ("referred by X"), acknowledge it and skip intake questions that referral context already answers.
+Present a compact snapshot (5-8 lines, their numbers), positioned on the revenue-motion map (Step 2). If the company record or knowledge base shows a referral source ("referred by X"), acknowledge it and skip intake questions that referral context already answers.
 
-## Step 2: The bowtie map
+## Step 2: The revenue-motion map
 
-Orient every capability on the revenue bowtie — awareness → education → selection → **commit** → onboard → adoption → expansion. Vruum today:
+Orient recommendations across the full revenue lifecycle. Do not use "outbound" as shorthand for Vruum and do not default to a campaign before diagnosing the bottleneck. Vruum today:
 
-- **Left side (acquisition) — fully run by Vruum:** sourcing (`/pipeline-fill`, CSV import), campaign targeting (`/campaign-builder`), multi-channel outreach with send-time drafting, reply handling, meeting booking, warming + content (`/engagement-triage`, `/create-content`).
-- **Commit:** deal pipeline + MEDDIC review (`/deal-triage`), proposals, close tracking.
-- **Right side (onboard / adopt / expand):** Vruum is your **system of record** here today (accounts, impact events, the bowtie scoreboard via `fetch` type=scoreboard subtype=bowtie); the autonomous engine for these stages is on the roadmap. Say this honestly — do not imply the right side runs itself.
+- **Understand:** website-to-profile/ICP, knowledge grounding, positioning diagnosis, company/prospect research, and evidence-backed match analysis.
+- **Create demand:** organic LinkedIn content, relationship-gated engagement, own-post engager capture, and paid LinkedIn amplification where ad permissions are available.
+- **Select and reach:** source prospects, find warm paths, build cohorts/campaigns, run email/LinkedIn outreach, handle inbound replies, and book meetings.
+- **Commit:** deal qualification/review, stakeholder management, proposals, contracts, payment, and close tracking.
+- **Grow and recover:** expansion and win-back are real harness-led motions. Onboarding/adoption are account-state and impact-tracking surfaces today, not autonomous customer-success programs.
+- **Learn and operate:** campaign/reply diagnosis, outcome intelligence, HubSpot ingestion, and mailbox health.
 
-Use the map to explain WHY a recommendation is next ("you have contacts but no campaign — that's the selection stage sitting idle"), not as a lecture. One paragraph max per session.
+Important boundaries: outreach/reply/content/comment prose is authored in the harness, not the backend; there is no phone/dialer motion; Google Ads is metrics-only; Salesforce is not wired end to end; the autonomous experiment loop is retired. Use the map to explain WHY a recommendation is next, not as a lecture. One paragraph max per session.
 
 ## Step 3: Pick the mode
 
-**Onboarding mode** — when profile is missing/thin OR no campaigns exist. This is a freshly connected account: land one fast win in the very first exchange, then walk the sequence to the first reviewed draft, one milestone per exchange, handing off at each step:
+**Onboarding mode** — when the profile is missing/thin or the account has no executed motion. Land one fast win in the first exchange, then choose the first motion from the seller's actual bottleneck instead of forcing every account through outbound:
 
-1. **Profile (the first quick win)**: run `manage_settings` action=auto_fill — Vruum reads their website and builds a starting picture of their ICP, value proposition, and target titles in under a minute. Show that back to them right away: that reveal *is* the first tangible payoff ("here's your revenue engine's starting picture, built from your site"). Then review/correct together and save via action=profile. This powers every draft Vruum writes — worth five careful minutes.
-2. **Channels**: check channel_status; for any disconnected channel send them the exact settings URL to connect LinkedIn/email (connection happens in the web plumbing, not the harness). Don't block the session on it — continue and circle back.
-3. **First contacts**: their CSV (`import_prospects`, offer custom-column mapping + list mirroring) or sourced fresh (`/pipeline-fill`).
-4. **First campaign**: invoke `/campaign-builder` and narrate.
-5. **First drafts**: enroll the cohort (the campaign-builder flow ends here); drafts generate on the backend.
-6. **First review**: invoke `/outreach-triage` on the first drafts. **This is the first-value moment** — a reviewed, ready-to-send draft in their own voice. Mark the milestone, celebrate briefly, and teach the rhythm in one line: "this triage, most days, is the whole job — everything else is occasional."
+1. **Profile (the first quick win)**: run `manage_settings` action=auto_fill — Vruum reads their website and builds a starting picture of their ICP, value proposition, and target titles in under a minute. Show that back to them right away: that reveal *is* the first tangible payoff ("here's your revenue engine's starting picture, built from your site"). Then review/correct together and save via action=profile. This grounds every draft the harness authors — worth five careful minutes.
+2. **Choose the first motion**: ask for the near-term revenue outcome and diagnose the constraint. Pipeline gap → sourcing/campaign; audience/authority gap → content or demand gen; warm network → warm-path routing; active opportunities → deal triage/close; customer base → expansion; recoverable relationships → win-back. If Vruum is not the right fit, say so.
+3. **Ship the first result through the specialist skill**. Do not connect channels until the chosen motion needs them. For the common pipeline path: source with `/pipeline-fill`, build with `/campaign-builder`, let the harness author the `needs_draft` work, then review with `/outreach-triage`. For content, hand off to `/create-content`; for demand gen, `/demand-gen-loop`; for deals, `/deal-triage`; for account growth, `/expansion-fill` or `/winback-fill`.
+4. **Mark the milestone**: save `chosen_motion` and `first_result`; update the legacy campaign/import/draft/review milestones only when that path actually ran.
 
 **Next-best-action mode** — when onboarding milestones are done (or the user asks "what's next"). Diagnose from the Step 1 reads, recommend ONE action, hand off:
 
@@ -67,16 +69,21 @@ Use the map to explain WHY a recommendation is next ("you have contacts but no c
 | Replies without follow-up | `/diagnose-reply` on the interesting ones, then respond |
 | Campaign reply rate sagging vs its history | `/campaign-doctor` |
 | Pipeline thin (few researched contacts) | `/pipeline-fill` |
+| Profile clear but no audience/authority motion | `/create-content`; use `/demand-gen-loop` only when paid amplification is appropriate and permitted |
+| Named target with a plausible relationship path | `find_warm_path` before cold enrollment |
 | Deals exist, no recent review | `/deal-triage` |
+| Closed-won customers with no follow-on motion | `/expansion-fill` |
+| Recoverable lost/churned relationships | `/winback-fill` |
+| Offer/ICP is unclear or sellability is questionable | profile auto-fill first; `/positioning-diagnostic` only for the narrower cold-outreach go/no-go |
 | Unclassified personas blocking targeting | `research` action=classify_personas, then `/campaign-builder` |
 | Everything humming | `fetch` type=insights subtype=improve — review what the system learned this week |
 
-If several fire, pick the one closest to revenue (replies > queue > enrollment > sourcing) and say why in one sentence. Mention the runner-up only if the user asks.
+If several fire, pick the one with the highest expected revenue impact per unit of seller attention. Replies and active deals usually outrank new activity; expansion can outrank cold acquisition when the evidence is strong. Say why in one sentence. Mention the runner-up only if the user asks.
 
 ## Hard rules
 
 - **Hand off, never re-teach.** When a specialist skill exists, invoke it. Do not reproduce its steps here — if you find yourself writing a numbered sub-procedure that exists in another skill, stop and invoke the skill.
-- **Inherit every safety gate.** Launch confirmations, draft approvals, and queue reviews belong to the specialist skills and the platform. Never bypass, summarize past, or pre-approve through them. Nothing sends without the seller's explicit review.
+- **Inherit every safety gate.** Launch confirmations, review requirements, and approval modes belong to specialist skills and the platform. Never bypass or pre-approve them. Manual outreach requires review; an explicitly configured `full_auto` campaign may auto-approve harness-authored outreach under backend send/audit guards. Public content and ad spend retain their own explicit approval gates.
 - **Tailor from reads, not stereotypes.** Every recommendation cites their actual numbers from Step 1. If a read fails, say what you couldn't see — don't fill the gap with a guess.
 - **One recommendation at a time.** A menu of five options is how sessions end with nothing shipped.
 - **Update `~/.vruum/guide-state.json` before ending**, and close by naming what shipped this session and what you'd suggest next time.