@vruum/skills

Vruum AI skills for Claude Code, Codex CLI, and any AI assistant with a skill directory.

Vruum is a revenue operating system. It researches prospects, runs outreach objectives across email and LinkedIn, triages replies, and tracks deals and revenue. Outreach drafts wait for your approval before they send. These skills need a Vruum account (vruum.ai).

Once installed, run /vruum-guide in your harness — it takes you from an empty account to your first reviewed outreach draft, then keeps recommending the next most valuable action.

Pairs with the Vruum MCP server at https://api.vruum.ai/mcp. The MCP server lists saved team skills with search type=skills, reads one with fetch type=skill, and publishes one with the skill tool (action=publish). This package installs Vruum-shipped skills into the standard skill directories used by Claude Code, Codex CLI, and other compatible harnesses.

You do not need @vruum/cli to use Vruum. Connect the Vruum MCP and install this skills package; the CLI is optional for local files, scripting, CI, auth debugging, and the convenience vruum init command.

Install

Claude Code

Plugin (recommended) — bundles the skills + Vruum MCP in one step. Vruum is listed in the Claude Directory, or add this repository as a marketplace:

/plugin marketplace add vruum-gtm/skills
/plugin install vruum@vruum-gtm

Then run /mcp to sign in to Vruum (OAuth).

Manual — add the MCP server to ~/.claude.json:

{
  "mcpServers": {
    "vruum": { "type": "http", "url": "https://api.vruum.ai/mcp" }
  }
}

Then install the skills directly:

npx --yes @vruum/skills@latest install

Restart Claude Code afterward. On Windows, the installer uses directory junctions and does not require Administrator access or Developer Mode.

Codex CLI

Plugin (recommended) — bundles the skills + Vruum MCP in one step:

codex plugin marketplace add vruum-gtm/skills
codex plugin add vruum@vruum-gtm
codex mcp login vruum

Manual / other harnesses — register the MCP, then install the skills into the agent-standard skills dir:

# ~/.codex/config.toml
[mcp_servers.vruum]
url = "https://api.vruum.ai/mcp"

npx --yes @vruum/skills@latest install                                # detects ~/.agents/skills/
npx --yes @vruum/skills@latest install --target /path/to/skills/dir   # any other harness

Cursor / VS Code Copilot / Cline

Register the MCP server via your editor's MCP setup (each one has its own UI / config path). Connect to https://api.vruum.ai/mcp (HTTP, OAuth via standard MCP flow). Saved team skills become readable with fetch type=skill; to also install the skill files locally, use the install --target command under Other local harnesses without plugin support.

Claude Desktop / Claude.ai (Cowork)

Download the Vruum plugin ZIP to bundle the connector and skills in one step:

github.com/vruum-gtm/skills/releases/latest/download/vruum-plugin.zip

Download and upload via Settings → Customize → Plugins → "+".

ChatGPT

Open the official Vruum marketplace app and follow the installation and connection prompts shown there. This is the recommended ChatGPT setup; no local npm install or Vruum CLI is needed.

Once connected, ask What needs my attention in Vruum today? for a read-only first check. The app bundles vruum-guide, deal-triage, and outreach-triage. Use the operations available in that app. The broader slash-command catalog in this README describes the local package. The npm installer below requires a local harness; it does not install skills into ChatGPT.

Other local harnesses without plugin support

npx --yes @vruum/skills@latest install --target /path/to/skills/dir

Coexisting with a Vruum-managed bundle

Some accounts also have a second, Vruum-managed skill bundle in the same harness. For overlapping skill names, a valid managed installation takes precedence. Installing or uninstalling this package preserves the managed bundle's links and update checker. If a managed link becomes stale, the next install restores the public skill instead of leaving a broken link.

Skills

• /objective-builder — Build and launch an outreach objective from criteria in about five prompts: filter contacts by size, industry, persona, region, or list; preview the cohort; create the objective (optionally cloning messaging from an existing one); assign people; review and launch. Use when: create an objective, build a campaign, new objective from criteria, objective or campaign from my list.
• /objective-doctor — Diagnose and fix struggling outreach objectives. Use when: fix an objective, diagnose a campaign, why is my objective not working, objective health, low reply rate, check my objectives or campaigns, which objectives need help.
• /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.
• /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.
• /deal-triage — Triage your active deal pipeline. Flags at-risk deals, surfaces stalled-deal alerts, runs MEDDIC qualification, and recommends next actions. Use when: review deals, triage deals, check pipeline, deal review, morning deals, pipeline review, deal health, at-risk deals.
• /demand-gen-loop — Run the full demand-gen motion end to end from your harness — set a goal, build the audience, co-produce the creative, get explicit approval, boost the published post, then monitor engagement and bridge engagers into outreach. Hands off to the specialist skills behind a HARD approval gate. Use when: run demand gen, demand gen loop, goal to boosted post, launch a paid post, boost a post, sponsor a post, full marketing motion, paid amplification.
• /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.
• /expansion-fill — Source expansion-ready customers for outreach. Finds closed-won customers >60 days old with no open follow-on deal and surfaces them for an expansion play. Use when: expand customer, find upsell opportunities, NRR play, expansion opportunities, customers ripe for expansion, who can we expand to.
• /ingest-meetings — Pull meeting transcripts from your connected Google Drive into Vruum. Attaches each transcript to the right person and deal as a meeting on their timeline, and turns its action items into tasks that surface in your daily briefing. You review every attach before anything is written; safe to re-run. Use when: ingest meetings, import meeting notes, pull transcripts, log my meetings, action items from meetings, Gemini notes, Read.ai transcripts, turn meetings into tasks.
• /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.
• /pipeline-fill — Source-agnostic pipeline orchestrator. Picks a source per objective (Sales Nav / YC / CSV / account list / discovery), runs harness deep research, applies a pre-filter gate, then saves into the objective through Vruum's server-side fit gate. Use when: fill pipeline, import prospects, daily imports, need more prospects, discover prospects from scratch, find buyers at these companies, deep research before import.
• /sales-nav-deep-fill — Sales Nav harness source for /pipeline-fill. Pre-filters Sales Nav profiles via vruum-pipeline-filter, produces a candidate list, hands off to /pipeline-fill for deep research and import. Use when: sales nav with deep research, sales nav harness mode, in-chat sales nav.
• /vruum-guide — Guide to running Vruum from your own AI harness. First run: guided onboarding from empty account to first reviewed outreach draft. After: reads live account state, recommends the single next most valuable action, hands off to the right skill. Use when: get started, onboarding, how do I use vruum, what should I do next, where do I start.
• /vruum-skills-upgrade — Upgrade @vruum/skills to the latest npm version and re-sync ~/.vruum/. Use when the user explicitly asks: upgrade vruum skills, update vruum, or pull latest vruum skills. A passive update notice does not invoke this skill.
• /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.
• /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 an objective with YC founders, sales nav dried up, source YC.

Upgrade

Passive update checks do not interrupt the requested task or install updates. After the task result, a skill may mention an available update once per conversation. Invoke /vruum-skills-upgrade when you want its upgrade flow (including the saved automatic-upgrade preference), or explicitly run:

npx --yes @vruum/skills@latest install

Uninstall

npx --yes @vruum/skills@latest uninstall

Removes all links or Windows junctions this installer created. Does not touch ~/.vruum/auth.json or other co-resident tool state.

Links

• Vruum
• MCP server
• Issues