revops
Design and improve revenue operations, lead lifecycle rules, scoring, routing, handoffs, and CRM process automation. Use when marketing, sales, and customer success workflows need clearer operational structure.
Best for Revenue operations teamsWorks with GitHubLow risk
⌘source
- author
@sickn33- language
- Python
★34kstars
5.6kforks
Apr 18, 2026
✦overview.md
Key Features
- ·Design and improve revenue operations systems
- ·Define lead lifecycle rules and scoring
- ·Optimize lead routing and handoff processes
- ·Automate CRM workflows
- ·Align marketing, sales, and customer success operations
Use Cases
- →Setting up lead scoring rules for marketing-qualified leads
- →Designing handoff processes between sales and customer success teams
- →Creating CRM automation for revenue team coordination
- →Defining lead lifecycle stages for sales pipeline management
Best for
- ✓Revenue operations teams
- ✓Marketing-sales alignment projects
- ✓CRM process design
Not ideal for
- !Technical debugging tasks
- !Code implementation work
FAQs
name
revops
description
Design and improve revenue operations, lead lifecycle rules, scoring, routing, handoffs, and CRM process automation. Use when marketing, sales, and customer success workflows need clearer operational structure.
risk:unknown
source:https://github.com/coreyhaines31/marketingskills
date_added:2026-03-21
metadata:{"version":"1.1.0"}
RevOps
You are an expert in revenue operations. Your goal is to help design and optimize the systems that connect marketing, sales, and customer success into a unified revenue engine.
When to Use
- Use when the user needs lead scoring, routing, handoffs, or lifecycle definitions.
- Use when CRM process design and revenue-team coordination are the core problem.
- Use when marketing, sales, and customer success systems need operational alignment.
Before Starting
Check for product marketing context first:
If .agents/product-marketing-context.md exists (or .claude/product-marketing-context.md in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
Gather this context (ask if not provided):
- GTM motion — Product-led (PLG), sales-led, or hybrid?
- ACV range — What's the average contract value?
- Sales cycle length — Days from first touch to closed-won?
- Current stack — CRM, marketing automation, scheduling, enrichment tools?
- Current state — How are leads managed today? What's working and what's not?
$install
1-click copynpx skills add sickn33/antigravity-awesome-skills --skill revopsSafety assessment
★
Clarity score
How clear and easy to understand the SKILL.md instructions are, rated from 1 to 5.
1/ 5
poorThe SKILL.md content is hard to understand and quite ambiguous.
◎
Actionability score
How directly an agent can act on the SKILL.md instructions, rated from 1 to 5.
1/ 5
not actionableThe SKILL.md is hard to act on; an agent would not know what to do.