RevOps Claude Skill

The RevOps Claude skill helps marketing and sales teams design lead lifecycle stages, scoring, routing, pipeline stages and handoff rules. It is made for marketers, sales ops and founders fixing leaks between teams. It is free and open source under the MIT license, from the Marketing Skills pack by Corey Haines (coreyhaines31/marketingskills).

GTM Intermediate MIT license 58.2k GitHub stars
Install
Claude Code plugin
/plugin marketplace add coreyhaines31/marketingskills
Claude Code plugin
/plugin install marketing-skills@marketingskills
Skills CLI
npx skills add coreyhaines31/marketingskills --skill revops
View on GitHub Checked

What the RevOps skill does

Revenue operations problems usually come from unclear definitions: marketing calls something an MQL, sales will not work it, and leads go cold. This skill starts by writing down stage definitions, entry and exit criteria, owners and SLAs before anything gets automated. Each document is meant to be implemented directly in your CRM.

It covers the full lead path. You get a lifecycle model, a fit plus engagement scoring approach with negative scoring, routing methods with fallback owners and a speed-to-lead focus, pipeline stage rules, deal desk approval tiers and data hygiene checks.

The scoring guidance is careful. It warns against overweighting content downloads, recommends freezing a model and testing it on a later holdout group, and says to recalibrate often. Output comes as standalone documents you can implement in your CRM. Treat it as a working draft you refine with Claude, not a one-shot answer, and keep the sources it cites so you can check them later.

  • Defines lifecycle stages from subscriber to customer with entry criteria, exit criteria and owners.
  • Builds lead scoring from fit, engagement and negative signals, with a threshold and testing plan.
  • Designs routing by round-robin, territory, account or skill, with fallback owners and audit logs.
  • Sets marketing-to-sales handoff SLAs and speed-to-lead rules with escalation.
  • Specifies pipeline stages, required fields and stage hygiene rules.
  • Sets deal desk approval tiers and handling for non-standard terms.
  • Plans dedupe, required fields, enrichment and a quarterly data audit, plus a metrics dashboard spec.

How it works

  1. Gather context

    Claude reads saved product marketing context, then asks about GTM motion, deal size, sales cycle, current stack, how leads are handled and your goals.

  2. Define the lifecycle

    It writes stage definitions with entry and exit criteria, owners and SLAs, including a clear MQL definition based on fit and engagement.

  3. Score and route

    Claude designs the scoring model and routing rules, with fallbacks so no lead sits unassigned.

  4. Configure the pipeline

    Claude sets pipeline stages, required fields and CRM automations, then adds deal desk approval tiers for non-standard terms and discounts.

  5. Spec the reporting

    Claude produces a metrics dashboard spec and a data hygiene plan, with platform-specific steps when it knows your CRM.

Example prompts

Once the RevOps skill is installed, ask Claude in plain language. These prompts trigger it:

  • Our leads are not getting to sales. Help me fix our MQL to SQL handoff
  • Design a lead scoring model for a B2B SaaS with a 30 day sales cycle
  • Write routing rules for inbound demo requests with a round-robin and fallback owner
  • Set up pipeline stages and required fields for HubSpot
  • Build a quarterly data hygiene checklist for our CRM

What you get

  • A lifecycle stage document with entry and exit criteria, owners and SLAs
  • A scoring specification with attributes, points and a threshold
  • A routing rules document with a decision tree and fallbacks
  • A pipeline configuration with stages, required fields and triggers
  • A metrics dashboard spec with metrics and data sources

Who it is for

  • Marketing leads fixing handoff problems with sales
  • Founders setting up their first CRM process
  • RevOps managers documenting scoring and routing
  • Agencies setting up lead management for B2B clients

How to install the RevOps skill

What you need: Nothing beyond Claude. Works with Claude Code and Claude.ai. Knowing your CRM and monthly lead volume helps Claude give platform-specific steps.

  1. Claude Code plugin
    /plugin marketplace add coreyhaines31/marketingskills
  2. Claude Code plugin
    /plugin install marketing-skills@marketingskills
  3. Skills CLI
    npx skills add coreyhaines31/marketingskills --skill revops
  4. Manual
    git clone https://github.com/coreyhaines31/marketingskills.git && cp -r marketingskills/skills/revops ~/.claude/skills/

After installing, restart Claude Code or start a new session. Claude loads the RevOps skill automatically when your request matches it, or you can ask for it by name.

Tips for better results

  • Tell it your CRM and monthly lead volume so the rules fit your platform and scale.
  • Agree on MQL and SQL definitions with sales before building any automation.
  • Hold back a later group of leads to test the scoring model before you roll it out.

Limitations

  • It writes specs and rules. It does not connect to your CRM or build the workflows.
  • Speed-to-lead figures in the skill come from a third party, so treat them as directional.

RevOps Claude skill FAQ

Yes. It is open source under the MIT license, so you can use, copy and edit it at no cost. You only pay for Claude itself.

Run /plugin marketplace add coreyhaines31/marketingskills, then /plugin install marketing-skills@marketingskills. That installs the whole pack. To get only this skill, run npx skills add coreyhaines31/marketingskills --skill revops.

It is a SKILL.md plus reference files, so you can zip the skill folder and upload it in Claude.ai under Settings, Capabilities, Skills on a paid plan. Claude Code gives the smoothest experience, since the skill can read and write project files.

Yes. This skill designs a scoring spec using fit, engagement and negative signals, sets an MQL threshold, and explains how to test it on a later group of leads before you rely on it.

In this skill, an MQL passes both a fit and an engagement threshold and needs sales to accept or reject it within an SLA. An SQL is a lead sales has accepted and qualified in conversation.