Claude Code for RevOps: The Complete Skills and Plugin Playbook

Sources: NEON-Rutger/B2B-revops-skills (MIT licence, 32 stars, 17 forks, built by Rutger Katz / Neon Triforce), plus relevant RevOps-adjacent skills already documented across the GTM Agents, Claude Skills for SaaS Founders, and 80+ Claude Code Sales Skills lead mags in this workspace.

This is the plugin: a genuinely dedicated, open-source RevOps skill layer for Claude, built specifically for B2B SaaS companies scaling from roughly €5M to €150M+ ARR, the exact stage where revenue operations becomes the actual constraint but a full RevOps hire is not yet justified. The repo's own framing: 28 battle-tested Claude skills that give expert-level RevOps, GTM, ICP, positioning, deal velocity, and operating cadence thinking on demand.

28 skills across 4 categories, all installed the same way: clone the repo, copy the folders you need into .claude/skills/.

Why this repo specifically

Most GTM skill collections treat RevOps as a small side category inside a much larger marketing or sales repo. This one is built the opposite way: a diagnostics-first framework that finds the actual constraint in a revenue system before recommending a fix, implementation playbooks for specific tools (HubSpot, Salesforce), and ICP/positioning/sales-methodology skills that chain into a complete GTM workflow rather than sitting as isolated prompts.

The repo's own honest boundary: these are the generic operational frameworks any B2B revenue team can use. The proprietary maturity model and client-specific delivery skills used in the maintainer's live consulting engagements are not included here; this is the self-serve layer.

Quick install

git clone https://github.com/NEON-Rutger/B2B-revops-skills.git

# Copy individual skills
cp -r B2B-revops-skills/revops-diagnostic/ your-project/.claude/skills/

# Or install everything
cp -r B2B-revops-skills/*/ your-project/.claude/skills/

Each skill is a folder containing a SKILL.md file (and optionally a references/ directory). Claude discovers and loads skills automatically once the folder sits inside .claude/skills/, no marketplace step required.

The largest category in the repo: 12 skills covering the foundational RevOps operating layer, from diagnosing what is actually broken through to the two major CRM platforms.

All 12 skills

revops-strategy: revenue operations strategy, pipeline architecture, strategic advisory.

revops-diagnostic: system diagnostics, constraint identification, root cause analysis. This is the entry point skill: run this first to find the real bottleneck before loading a specialist skill to fix it.

revops-metrics: revenue measurement, funnel math, unit economics, benchmarks.

revops-forecasting: forecast methodology, accuracy measurement, pipeline analysis.

revops-data-governance: data governance, quality operations, field management.

revops-tech-stack: tech stack architecture, platform evaluation, capability mapping.

revops-handoffs: revenue handoff design across the full bow-tie model (the marketing-to-sales-to-CS handoff points where deals and accounts most often get dropped).

revops-change-management: change management specifically for revenue operations adoption, distinct from generic organisational change management.

revops-crisis: emergency response when multiple revenue systems break simultaneously.

revops-org-chart: RevOps team design, role structure, and hiring sequencing by company stage.

revops-hubspot: HubSpot implementation patterns specifically for RevOps use cases.

revops-salesforce: Salesforce implementation patterns specifically for RevOps use cases.

6 skills covering the wider GTM motion RevOps sits inside: planning, compensation, marketing ops, CS ops, sales methodology, and partner channels.

All 6 skills

gtm-planning: GTM motion selection, org design, territory and capacity planning.

gtm-compensation: compensation plans, quota setting, OTE structures.

marketing-operations: lead scoring, attribution, campaign tracking, MQL handoff.

cs-operations: customer success operations, health scoring, renewal management.

sales-methodology: multi-framework coverage across SPICED, MEDDIC, Challenger, SPIN, and Gap Selling, rather than being locked into one methodology.

partner-channel-operations: partner programme design, enablement, co-selling, deal registration.

4 skills covering the operational layer that keeps the pipeline visible and the data underneath it usable.

All 4 skills

pipeline-visibility: pipeline reporting, dashboard design, hygiene, forecast reporting.

lead-routing: lead assignment logic, round-robin, territory design, speed-to-lead.

data-enrichment: enrichment strategy, provider evaluation, integration patterns.

revenue-operating-cadence: meeting architecture, the data pyramid (which metrics get reviewed at which cadence and by whom), and board reporting.

How this connects to the enrichment skills already in this workspace

The data-enrichment skill here covers strategy and provider evaluation at the RevOps-architecture level: which enrichment vendor to choose and how to integrate it into the broader data flow. For the actual row-by-row execution of an enrichment waterfall (Apollo to Hunter to Findymail, rate limit handling, failure logging), the personalisation waterfall skills from the Claude Code for B2B Cold Email lead mag elsewhere in this workspace are the execution layer underneath this strategic one.

6 skills covering the strategic layer that determines who you sell to, how you position against them, and where deals actually stall or expand.

All 6 skills

icp-builder: builds and validates ICPs using the GAP method and SPICED framework, a more structured approach than a plain written ICP description.

positioning-messaging-designer: positioning frameworks using the Use Case Canvas and the Opposites method (defining what you deliberately are not, to sharpen what you are).

deal-velocity-engineer: sales cycle diagnostics, stage exit criteria, and pipeline deflation (identifying and removing the stages that inflate cycle time without adding real qualification value).

expansion-revenue-architect: NRR/GRR systems, whitespace analysis (finding unrealised expansion inside existing accounts), and the CS-to-Sales handback motion for expansion deals.

partner-ecosystem-architect: ecosystem-led growth, nearbound methodology (growth driven by partner and ecosystem relationships rather than pure outbound or inbound), and partner strategy.

operating-cadence-designer: operating cadence design covering rituals, dashboards, and escalation rules, the design layer underneath revenue-operating-cadence's execution.

How the skills chain together

From the repo's own documented chains, run in this order:

Diagnose then fix: revops-diagnostic finds the constraint, then load whichever specialist skill actually addresses it.

ICP to pipeline: icp-builder to positioning-messaging-designer to sales-methodology.

Deal flow: deal-velocity-engineer to pipeline-visibility to revops-forecasting.

Partner motion: partner-ecosystem-architect to partner-channel-operations to revops-handoffs.

Operating rhythm: operating-cadence-designer to revenue-operating-cadence to revops-metrics.

# Example: run the ICP to pipeline chain
"Load icp-builder. Build our ICP using the GAP method for [PRODUCT/OFFER].
Then load positioning-messaging-designer and build positioning using the
Use Case Canvas against that ICP.
Then load sales-methodology and recommend which framework (SPICED, MEDDIC,
Challenger, SPIN, or Gap Selling) fits this ICP and deal size best."

The other genuinely relevant RevOps material already documented across this workspace, for teams who want more than the 28-skill core layer.

From Claude for RevOps: The Complete Cheatsheet (existing lead mag)

Covers what Claude can and cannot reliably do for GTM/RevOps work, model and mode selection per task type, how to give Claude proper context about a sales org (the equivalent of the CLAUDE.md context file used throughout this workspace), 8 copy-paste prompt templates for pipeline and GTM work, and integration/output-format guidance including when not to trust the output blind.

From GTM Agents for Claude Code (67-plugin marketplace)

Three plugins from this marketplace sit directly adjacent to RevOps work: revenue-analytics (cohort analysis, LTV/CAC, attribution, forecasting), business-intelligence (BI roadmap, data contracts, dashboards, executive briefs), and pricing-strategy (pricing and packaging design, monetisation models). Install via /plugin marketplace add gtmagents/gtm-agents then /plugin install revenue-analytics (or the equivalent plugin name).

From Claude Skills for SaaS Founders (190+ skill repo)

The finance category (financial analysis and modelling) and the c-level-advisor category's CFO role specifically (built around Chain of Thought reasoning, suited to financial modelling where each number depends on the one before it) both connect directly to RevOps forecasting work, giving an executive-level second opinion on top of the operational forecasting skill covered above.

A note on adjacent repos found during research

Two other real, publicly documented repos are worth knowing about even though they are not the primary source for this lead mag:

t0ddc3by/claude-for-customer-success ships an 81-skill suite where the rev-ops plugin alone carries 34 skills, framed specifically as the portfolio intelligence and revenue operations layer for a CS organisation. Its own stated position: CS teams that want to be treated as a revenue centre need CRM data quality, expansion and renewal pipeline visibility, forecasting, quota and incentive planning, deal desk governance, and revenue leakage scanning, the same infrastructure sales RevOps already has.

A standalone Revenue Operations skill listed on MCP marketplaces provides pipeline health analysis, forecast accuracy tracking using MAPE (Mean Absolute Percentage Error), and core GTM efficiency calculations including the Rule of 40 and LTV:CAC, positioned specifically for weekly pipeline reviews, QBRs, and board-level reporting.

For a CS-specific RevOps need, t0ddc3by's rev-ops plugin is the more directly relevant source. For quick pipeline health and forecast accuracy metrics without installing a full skill repo, the MCP-based skill covers that narrower need on its own.

All 28 skills, the install commands, and the recommended build order for a team adopting this from scratch.

Full 28-skill table

Skill	What it does
revops-strategy	Revenue operations strategy, pipeline architecture, strategic advisory
revops-diagnostic	System diagnostics, constraint identification, root cause analysis
revops-metrics	Revenue measurement, funnel math, unit economics, benchmarks
revops-forecasting	Forecast methodology, accuracy measurement, pipeline analysis
revops-data-governance	Data governance, quality operations, field management
revops-tech-stack	Tech stack architecture, platform evaluation, capability mapping
revops-handoffs	Revenue handoff design across the full bow-tie model
revops-change-management	Change management for revenue operations adoption
revops-crisis	Emergency response when multiple revenue systems break simultaneously
revops-org-chart	RevOps team design, role structure, hiring sequencing by stage
revops-hubspot	HubSpot implementation patterns for RevOps
revops-salesforce	Salesforce implementation patterns for RevOps
gtm-planning	GTM motion selection, org design, territory and capacity planning
gtm-compensation	Compensation plans, quota setting, OTE structures
marketing-operations	Lead scoring, attribution, campaign tracking, MQL handoff
cs-operations	Customer success operations, health scoring, renewal management
sales-methodology	SPICED, MEDDIC, Challenger, SPIN, Gap Selling, multi-framework
partner-channel-operations	Partner programme design, enablement, co-selling, deal registration
pipeline-visibility	Pipeline reporting, dashboard design, hygiene, forecast reporting
lead-routing	Lead assignment logic, round-robin, territory design, speed-to-lead
data-enrichment	Enrichment strategy, provider evaluation, integration patterns
revenue-operating-cadence	Meeting architecture, data pyramid, board reporting
icp-builder	ICP building and validation using the GAP method and SPICED
positioning-messaging-designer	Positioning using Use Case Canvas and Opposites method
deal-velocity-engineer	Sales cycle diagnostics, stage exit criteria, pipeline deflation
expansion-revenue-architect	NRR/GRR systems, whitespace analysis, CS-Sales handback
partner-ecosystem-architect	Ecosystem-led growth, nearbound methodology, partner strategy
operating-cadence-designer	Operating cadence design, rituals, dashboards, escalation rules

Full install

git clone https://github.com/NEON-Rutger/B2B-revops-skills.git
cp -r B2B-revops-skills/*/ your-project/.claude/skills/

Where to start if adopting this fresh

Step 1: run revops-diagnostic first, always. Do not guess at which specialist skill to reach for before knowing what the actual constraint is.

Step 2: whichever specialist the diagnostic points to, load that skill next rather than working through the repo top to bottom.

Step 3: once the immediate constraint is addressed, build the operating rhythm (operating-cadence-designer to revenue-operating-cadence to revops-metrics) so the same constraint gets caught earlier next time rather than resurfacing as a fresh crisis.

Step 4: layer in the adjacent GTM Agents plugins (revenue-analytics, business-intelligence, pricing-strategy) once the core RevOps layer is stable and the team wants deeper analytics or pricing work on top of it.