Overview
Install Vruum-shipped workflow skills, and publish team skills for reuse.
Skills are reusable workflow instructions your agent can run end to end. There are two different surfaces:
- Vruum-shipped skills are packaged playbooks such as
outreach-triage,pipeline-fill, anddeal-triage. They are delivered by the Vruum plugin,vruum init, or the@vruum/skillsinstaller. - Team skills are playbooks saved in Vruum, shared with team members, and
discovered or invoked through the MCP
skillfacade.
MCP is the live tool connection. Shipped skills are local/plugin instructions the harness loads; team skills are stored in Vruum.
For clients, the default instruction is: ask for the outcome and let the agent invoke the matching skill. The underlying calls are documented so agents can inspect, verify, or recover from a failed step.
For clients, the easiest instruction is:
Read the matching Vruum skill page as Markdown, then invoke that skill. Use the
underlying MCP or CLI calls only when you need to inspect, verify, or recover
from a failed step.Install or load skills
Use the highest path your harness supports:
| Path | Use when | What happens |
|---|---|---|
| Plugin | The harness supports a Vruum plugin. | The plugin bundles Vruum skills plus the MCP server entry where the harness supports both. |
vruum init | You are using a local technical harness. | Claude Code gets skills in ~/.claude/skills; Codex CLI gets skills in ~/.agents/skills; other harnesses get MCP and may need manual skill loading. |
@vruum/skills installer | The harness exposes a skill directory. | The npm package installs or updates the local skill files in the target directory. |
MCP skill tool | The harness can connect remote MCP. | The agent can discover, fetch, invoke, and publish team skills saved in Vruum. It does not install the shipped @vruum/skills package. |
| Quick Start | The harness has no plugin or skill directory. | Paste the install prompt and let the agent connect MCP, load shipped skills if the harness supports them, and verify setup. |
Claude Code:
vruum login
vruum init
# or install just the skill files
npx @vruum/skills install --target ~/.claude/skillsCodex CLI:
vruum login
vruum init
export VRUUM_MCP_TOKEN=<your-vruum-token>
codex
# or install just the skill files
npx @vruum/skills install --target ~/.agents/skillsGeneric skill directory:
npx @vruum/skills install --target /path/to/skills
npx @vruum/skills uninstallMCP team-skill invocation:
{
"tool": "skill",
"arguments": {
"action": "invoke",
"id": "partner-channel-review"
}
}Team skills
Team skills are your team's reusable playbooks. They live in Vruum, can be shared with team members, and are discoverable through the MCP skill surface. That database is for team-created skills, not the Vruum-shipped package skills listed below.
Ask the agent to draft the trigger description and full body, review it, then publish it through MCP:
{
"tool": "skill",
"arguments": {
"action": "publish",
"payload": {
"body": "---\nname: partner-channel-review\ndescription: Review partner-sourced opportunities and recommend next actions.\n---\n\nRead active partner-sourced deals, inspect notes and next steps, then return risk, evidence, next action, and owner.",
"scope": "company"
}
}
}Do not create team skills in a browser editor. Have the harness draft, review, publish, and then invoke them.
The skills
These are Vruum-shipped package skills. Install them through the Vruum plugin,
vruum init, or @vruum/skills.
- Outreach triage — review the pending
outreach queue, approve the good drafts, regenerate or reject the rest.
Skill:
outreach-triage. - Engagement triage — clear the warming
and nurture engagement queue (LinkedIn comments, reactions). Skill:
engagement-triage. - Pipeline fill — source and import new
prospects, then confirm they landed in the pipeline. Skill:
pipeline-fill(with thecsv-pipeline-fill,sales-nav-deep-fill, andyc-pipeline-fillsource variants). - Deal ops — create, qualify, advance, and close
deals through the pipeline. Skill:
deal-triage.