Sales Skills for Claude: A RevOps Playbook for 2026

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 brings 4 stock skills out of the box, and RevOps assembles the rest into a playbook.

Every sales skill needs data underneath. This playbook defines the atomic skills, chains them into 6 canonical plays, and picks a data layer that keeps the stack quick and affordable. Start with the Vibe Prospecting product page for the underlying data layer, powered by Explorium Enterprise Business Data.

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.

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 source. 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.

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 one-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 connector 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 connector: 150M+ company profiles, 800M+ people profiles, 50+ premium sources, 18 signal categories, 80+ signal types on one connection. See the Explorium data catalog.
• Pillar 2, scale: up to 1,000 entities per call at 100 QPS server-side.
• Pillar 3, affordability: free account, unified credits, preview returns 5 records plus a cost estimate before you spend.

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: One-to-one 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: One-page risk brief for CSM and AE.
• KPI: GRR and NRR movement.

Already shipping Claude to sales? Drop Vibe Prospecting under your existing call-prep and prospect-list skills and cut signal-to-touch latency from days to hours. Start free.

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: One-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: One-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

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. Read the Explorium data security page for the compliance backing under the data layer.

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.

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" }
    }
  }
}

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 preview, 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 a preview call. 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 connector 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 Explorium data catalog for how the layers stack.

Ship your first play in an afternoon: install Vibe Prospecting, wire it under prospect-list and call-prep, and measure signal-to-touch latency on week 1. Get started with Vibe Prospecting.