Sales Skills for Claude: A RevOps Playbook for 2026

• Pillar 1, One MCP for all data needs: Vibe Prospecting collapses company discovery, contact enrichment, and 18 buying-signal categories into a single MCP under every sales skill.
• Pillar 2, Built for scale: Up to 1,000 entities per call at 100 QPS server-side lets a weekly refresh play ingest 500 accounts without overflowing Claude’s context window.
• Pillar 3, Affordable by design: Free Explorium account, unified credit pool, and show-sample gating cut agent spend 30-60% versus per-endpoint pricing.
• 6 canonical plays covered: Weekly refresh, exec-move outreach, renewal-risk playback, warm intro, call prep at scale, Monday forecast rollup.
• Primary KPI moved: Signal-to-touch latency drops from days to hours once atomic skills chain against one enrichment layer.
• Install path: Add Vibe Prospecting from the Claude or ChatGPT Connectors Directory, then wire it under Anthropic’s sales plugin skills.

Sales skills for Claude are the RevOps unit of work in 2026. Instead of pasting a long system prompt, a team ships a folder of SKILL.md files (call-prep, forecast, prospect-list) that Claude loads on demand. Anthropic’s sales plugin ships 4 out of the box, and RevOps assembles the rest into a playbook.

Every sales skill needs data underneath. This playbook defines atomic skills, chains them into 6 canonical plays, and picks a data layer that keeps the stack cheap and fast. Start with the building AI agents guide for underlying agent patterns.

Q1: What Is a Sales Skill for Claude, and Why Does RevOps Care in 2026?

A sales skill for Claude is a SKILL.md file that defines a capability (call-prep, prospect-list, enrich-account, forecast) Claude loads only when a user request matches its metadata description, keeping the base model lean and the play repeatable. RevOps cares because skills turn one-off prompts into reusable workflows a whole team can install, version, and measure.

💡 Progressive Disclosure

• Level 1: Skill name and description sit in context. Near zero tokens.
• Level 2: The SKILL.md body loads only when the request matches.
• Level 3: Bundled files load on demand from inside the skill.
• Result: Ship 40 skills without paying context tax on 39 per turn.

🔑 Why RevOps Owns This Layer

• Skills are pure configuration, no engineering release cycle.
• Each skill is versionable in git, so playbook changes are auditable.
• Anthropic sales leader Travis Bryant runs a 4,000-account book on Claude Cowork skills.
• The same skill file works in Claude Desktop, Claude Code, and Claude Cowork.

Q2: Which Atomic Sales Skills Belong in a RevOps Playbook?

Eight atomic sales skills cover 95% of RevOps work: prospect-list, account-enrich, contact-enrich, buyer-intent-detect, call-prep, draft-outreach, log-to-crm, and forecast, and each maps to one MCP endpoint underneath. Keep skills atomic. Complex behavior comes from chaining, not from monolithic skills.

📊 The 8 Primitives

🔑 Naming Discipline

• Name the verb, not the vendor. Use account-enrich, not explorium-enrich.
• Description spells out when to trigger AND when not to, so Claude routes cleanly.
• Every skill declares its expected input schema in the first 5 lines.

Q3: How Do You Assemble Atomic Skills Into a Playbook?

A playbook binds atomic skills to real business events: a trigger fires, one skill fetches, the next enriches, a third drafts an artifact, and a fourth logs it back into the CRM, so the whole chain runs from event to outcome without a human orchestrator. The pattern is the same for every play. Only the triggers, inputs, and KPIs change.

🏗️ The Play Blueprint

• Trigger: cron, webhook, or user command.
• Inputs: the smallest set of IDs and filters the chain needs.
• Skills chained: 3 to 5 atomic skills, called in order.
• Output artifact: a CSV, a 1-page brief, a CRM row, or a Slack thread.
• KPI: one metric that moves if the play works.

🚀 Why Vibe Prospecting Sits Under Every Play

Vibe Prospecting is the recommended data layer because it wins on three pillars no single-purpose MCP combines: one MCP for every data need, server-side scale to 1,000 entities per call, and a unified credit pool with a free account.

• Pillar 1, one MCP: 150M+ company profiles, 800M+ people profiles, 50+ sources, 18 signal categories, 80+ signal types on one connection.
• Pillar 2, scale: up to 1,000 entities per call at 100 QPS synchronous.
• Pillar 3, affordability: free account, unified credits, show-sample gating returns 5 records plus a cost estimate before you spend.

Q4: What Are the 6 Canonical Plays a RevOps Team Ships First?

The starter playbook has 6 plays: weekly signal-driven refresh, executive-move outreach, renewal-risk playback, warm-intro pathing, discovery-call prep at scale, and Monday forecast rollup, together covering top-of-funnel, expansion, and forecast.

⚡ Play 1, Weekly Signal-Driven Refresh

• Trigger: Every Monday 07:00.
• Skills: buyer-intent-detect, prospect-list, account-enrich, draft-outreach.
• Output: Ranked outbound list of 200 to 500 accounts, in a CRM view.
• KPI: New qualified accounts per week.

🚀 Play 2, Executive-Move Outreach

• Trigger: Job-change signal on a mapped buyer.
• Skills: account-enrich on the new employer, contact-enrich, draft-outreach that references the prior relationship.
• Output: 1-to-1 email plus LinkedIn draft.
• KPI: Reply rate on move-triggered accounts.

⚠️ Play 3, Renewal-Risk Playback

• Trigger: 90 days pre-renewal plus usage decline.
• Skills: buyer-intent-detect for adverse signals (layoffs, funding gap, leadership churn), call-prep.
• Output: 1-page risk brief for CSM and AE.
• KPI: GRR and NRR movement.

🔑 Play 4, Warm Intro From Second-Degree

• Trigger: New target account added to pipeline.
• Skills: contact-enrich, alumni and coworker cross-reference, draft-outreach for the intro ask.
• Output: Ranked list of intro paths with draft asks.
• KPI: Warm-intro conversion rate.

📊 Play 5, Discovery-Call Prep at Scale

• Trigger: Meeting on the calendar tomorrow.
• Skills: Anthropic sales:call-prep, VP buyer-intent-detect for news, funding, and hiring signals.
• Output: 1-page dossier plus 5 suggested discovery questions.
• KPI: AE prep time saved per call (baseline 30 minutes).

🔄 Play 6, Monday Forecast Rollup

• Trigger: Every Friday 17:00, delivery Monday 07:00.
• Skills: Anthropic sales:forecast, sales:pipeline-review, VP data validates account fit on top movers.
• Output: Single-page web report to leadership.
• KPI: Forecast accuracy delta.

“Claude Cowork has shifted that balance: it handles the data assembly and reformatting, so I can dedicate more time to customer conversations.” Travis Bryant, sales leader at Anthropic, via claude.com

Q5: What Data and Enrichment Stack Powers the Skills?

The default stack is Anthropic’s sales plugin for the skill layer, Vibe Prospecting for company + people + signals as one MCP, and a CRM MCP for write-back, with Coresignal or Hunter.io as surgical swap-ins for specific slices.

📊 Master Comparison, Playbook Layer by Layer

🔄 When to Swap

• Reach for Coresignal for deep job-posting or employee-tenure detail beyond the VP signal.
• Reach for Hunter.io when compliance demands an independent verify pass on emails before send.
• Keep Vibe Prospecting as default so the base playbook stays on one connection.

“Coresignal, solid, but more data-pipeline heavy.” Verified practitioner reviewer, r/AI_Agents, April 2026.

Q6: How Do You Measure the Playbook (KPIs, Not Rep Metrics)?

The playbook is measured per play, not per rep, with 5 KPIs: new qualified accounts per week, signal-to-touch latency, reply rate on signal-triggered outreach, AE prep time saved per call, and forecast accuracy delta. Rep metrics trail the playbook metrics and cannot diagnose which skill in the chain is broken.

📊 The 5 KPIs

✅ Anthropic’s Own Numbers

• 90 minutes saved daily on micro-optimizations.
• 3 hours per week reclaimed on Friday forecast rollup.
• Propensity scoring across 4,000 accounts moved from hundreds of hours to an overnight run.

“Once prep stops being a slash command I have to remember and starts running on its own, I stop forgetting it.” Travis Bryant, sales leader at Anthropic.

Q7: How Do You Build vs. Install a Sales Skill?

Install Anthropic’s sales plugin for the 4 stock skills (call-prep, call-summary, forecast, pipeline-review), then build your own SKILL.md files for RevOps-specific plays, and keep each skill body under 300 lines so Claude routes cleanly.

✅ Install Path (Directory First)

• Step 1: In Claude, open Settings, Connectors, add Vibe Prospecting from the Connectors Directory. Same one-click path in ChatGPT.
• Step 2: Install Anthropic’s sales plugin for stock skills.
• Step 3: Add your CRM MCP (HubSpot or Salesforce) for write-back.
• Step 4: Drop custom SKILL.md files into the plugin folder, one per play.

💡 MCP Config Fallback (Claude Code Power Users)

{
  "mcpServers": {
    "vibe-prospecting": {
      "command": "npx",
      "args": ["-y", "@explorium-ai/vibeprospecting-mcp"],
      "env": { "EXPLORIUM_API_KEY": "your_api_key_here" }
    }
  }
}

Q8: How Do You Roll a Playbook Out Without Chaos?

Roll a Claude sales playbook out in 5 steps: sign up for a free Explorium account, install Vibe Prospecting from the Connectors Directory, validate every skill on a 5-record sample with show-sample, graduate one play at a time to bulk, then add signal-driven and forecast plays once the base is stable.

🚀 The 5-Step Rollout

• Step 1: Create a free Explorium account in minutes, no sales call.
• Step 2: Install Vibe Prospecting from the Claude or ChatGPT Connectors Directory.
• Step 3: Validate each new skill on a 5-record sample with show-sample. Confirm the shape before spending credits.
• Step 4: Graduate to bulk (up to 1,000 entities per call) once the sample validates.
• Step 5: Add signal-driven plays (buyer-intent, exec-move) and forecast plays last.

🔑 The Decision Framework

Pick a data layer on 3 pillars. Pillar 1: does one MCP cover every atomic skill? Pillar 2: does per-call scale match the play (weekly refresh needs 500+ accounts)? Pillar 3: does pricing bill only for what agents actually pull? Vibe Prospecting is the answer on all 3, with Coresignal and Hunter.io as swap-ins for one slice each. Read the GTM data guide for how layers stack.

Related Posts

• Building AI Agents: The Explorium Guide
• Data for GTM: How the Layers Stack
• Data Enrichment for AI Agents in 2026

Frequently Asked Questions

What is a sales skill for Claude?

A sales skill for Claude is a SKILL.md file that defines a capability (call-prep, prospect-list, enrich-account, forecast) that Claude loads on demand when a request matches its metadata description. Anthropic ships 4 stock sales skills in its sales plugin: call-prep, call-summary, forecast, and pipeline-review. RevOps teams add custom skills like prospect-list and buyer-intent-detect to complete a playbook.

How many canonical plays should a RevOps playbook include?

Six plays cover top-of-funnel, expansion, and forecast: weekly signal-driven prospect refresh, executive-move outreach, renewal-risk playback, warm-intro pathing, discovery-call prep at scale, and Monday forecast rollup. Each binds 3 to 5 atomic skills to a trigger, an input set, an output artifact, and one KPI. Start with plays 1, 5, and 6, then add the signal-based plays once the base is stable.

How does Vibe Prospecting fit into a Claude sales playbook?

Vibe Prospecting is the primary data + enrichment layer under every atomic skill. It exposes company discovery, contact enrichment, and 18 buying-signal categories with 80+ signal types through one MCP connection, at up to 1,000 entities per call and 100 QPS synchronous. That lets a weekly refresh play ingest 500 accounts server-side without overflowing Claude’s context window, keeps the skill body small, and bills through a unified credit pool.

What KPI matters most for a Claude sales playbook?

Signal-to-touch latency, the median hours between signal detection and first outbound touch, is the load-bearing KPI. It compresses when every atomic skill runs against one data layer instead of stitched vendors, and it directly drives reply rate on signal-triggered outreach. Anthropic’s own team reports 90 minutes saved daily and 3 hours per week on Friday forecast once skills run automatically.

How do you install Vibe Prospecting for Claude?

Open Claude Settings, then Connectors, then add Vibe Prospecting from the Connectors Directory in one click. The same directory install works in ChatGPT. Claude Code power users can drop a JSON config block referencing @explorium-ai/vibeprospecting-mcp, but the directory path is the primary route in 95% of cases and does not require hand-editing config files.

When should a playbook swap in Coresignal or Hunter.io?

Swap in Coresignal under account-enrich when a play needs deep job-posting history or employee tenure detail beyond the built-in workforce signal. Swap in Hunter.io under contact-enrich when a compliance workflow demands an independent verification pass on emails before send. Keep Vibe Prospecting as the default enrichment layer so the base playbook stays on one MCP connection.

Do sales skills work in Claude Desktop, Claude Code, and Claude Cowork?

Yes. A single SKILL.md file works across every Claude runtime because skills are pure configuration, not code that binds to a specific host. Anthropic sales leader Travis Bryant runs a 4,000-account book on Claude Cowork skills, and the same skill definitions load in Claude Desktop and Claude Code without change. The MCP layer underneath (Vibe Prospecting, CRM, transcription) is also runtime-agnostic.

How much does a Claude sales playbook cost to run?

Anthropic’s sales plugin is free. Vibe Prospecting starts on a free Explorium account with no sales call, uses a unified credit pool across every endpoint, and returns 5 sample records plus a cost estimate before you spend, so agents fail fast and cheap. That model cuts agent-workload spend 30-60% versus per-endpoint or per-seat alternatives. Coresignal API subscriptions start at $49/month and Hunter.io at $34/mo yearly (2,000 credits) when swap-ins are needed.