RevOps Skills Library for Claude

Current release: v1.7.0 (2026-09-09), 45 skills, all stable. See the CHANGELOG for what changed in each release.

45 battle-tested Claude skills for B2B revenue teams. Drop them into any Claude project and get expert-level RevOps, GTM, ICP, positioning, deal velocity, and operating cadence thinking on demand.

Built for: B2B SaaS companies in the growth phase where revenue operations is the constraint and hiring a full RevOps team isn’t yet justified.

Not only for scale-ups. Since v1.7.0, 16 skills open with a stage check: they sort the company into start-up before product-market fit, start-up with product-market fit, scale-up or enterprise, and say what to run, what to skip and what changes at enterprise. STAGE-GUIDE.md holds the definition and the map.

What you get:

• A diagnostics-first framework that finds the real constraint before recommending a fix
• Implementation playbooks for HubSpot, Salesforce, pipeline architecture, and compensation design
• ICP, positioning, and sales methodology skills that chain together into a complete GTM workflow
• Every benchmark carries a named source and vintage, so you know which numbers are 2026 reality and which are pre-2024 folklore

---

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). Place the folder in your project’s .claude/skills/ directory. Claude discovers and loads skills automatically when you open the project.

---

Skills

RevOps Core (15 skills)

GTM and Domain (10 skills)

Pipeline and Data (5 skills)

Pricing and Deal Operations (2 skills)

Deal Execution and Post-Sale (5 skills)

ICP, Positioning, and Growth (8 skills)

---

How they work together

Skills chain naturally. Start with a diagnostic, then load the specialist.

• Diagnose then fix: revops-diagnostic finds the constraint → load the relevant specialist skill
• ICP to pipeline: icp-builder → positioning-messaging-designer → sales-methodology
• Deal flow: deal-velocity-engineer → pipeline-visibility → revops-forecasting
• Partner motion: partner-ecosystem-architect → partner-channel-operations → revops-handoffs
• Operating rhythm: operating-cadence-designer → revenue-operating-cadence → revops-metrics
• Data foundation: gtm-data-architecture → revops-data-governance → pipeline-visibility
• Monetization: pricing-monetization-ops → deal-desk-operations → gtm-compensation
• Post-merger: crm-migration-consolidation → revops-data-governance → revops-hubspot or revops-salesforce
• Pipeline hygiene: deal-qualification-gates → deal-velocity-engineer → revops-forecasting
• Renewal defense: renewal-save-motion → expansion-revenue-architect → cs-operations
• Win-back: closed-lost-revival → icp-builder → sales-methodology
• Customer reviews: qbr-ebr-builder → cs-operations → revenue-operating-cadence
• Evaluation to close: deal-qualification-gates → trial-poc-conversion → procurement-navigation
• Land to renew: onboarding-activation → qbr-ebr-builder → renewal-save-motion
• Learn from decisions: win-loss-program → closed-lost-revival → deal-qualification-gates
• Ramp the team: sales-ramp-enablement → sales-methodology → gtm-compensation
• Comp as a system: gtm-compensation → comp-plan-architecture → deal-desk-operations
• Talk to finance: revops-metrics → saas-pnl-reading → revops-forecasting

---

Versioning

The library uses semantic versioning, tracked in CHANGELOG.md:

• MINOR (v1.x.0): new skills, or substantive new capability inside existing skills (new frameworks, new sections, benchmark refreshes that change recommendations).
• PATCH (v1.x.y): corrections, sourcing fixes, typography, small clarifications. No new capability.
• MAJOR (v2.0.0): renames, folder restructures, or removals that break an existing install.

Release discipline: every release updates the CHANGELOG, the version line at the top of this README, the skill count, and the Since column for any new skill. Benchmarks inside skills carry their own source and vintage inline (for example “(Benchmarkit, 2026)”), so a skill’s numbers are auditable independently of the library version.

---

What’s not here

These are the generic operational layer: the frameworks and methodology that any B2B revenue team can use independently.

These skills provide frameworks for self-serve implementation. They won’t run a discovery call, facilitate a workshop, or hold your leadership team accountable to a new operating cadence. If you need implementation support beyond self-service skills, consider engaging a revenue operations consultant.

---

Contributing

See CONTRIBUTING.md. The bar is intentionally high.

Changelog

See CHANGELOG.md.

License

MIT, see LICENSE.

---

Built by Rutger Katz / Neon Triforce