Individual skill
revenue-operations
Unifies marketing, sales, and customer success around one funnel with org-wide stage definitions, hand-off SLAs, a single source of truth, shared metrics, and a pipeline-weighted forecast. Use when someone asks "set up RevOps", "marketing and sales disagree on what an MQL is", "our forecast is always wrong", "deals fall through the cracks between teams", or "what should our pipeline coverage be". Do NOT use for diagnosing conversion drop-off inside a product or marketing funnel - use funnel-analysis instead - for building the revenue financial model - use revenue-modeling instead - or for outbound activity math per rep - use prospecting-metrics instead.
skills/revenue-operations/SKILL.md
Source commit 97a13607d669157a4a16d5ba79b77f208319f7b9
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 6, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 24
- Repository last updated
- Oct 13, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- claude Repository topic
- claude-skills Repository topic
- skill-me Repository topic
- sales Derived category
- marketing Derived category
- finance Derived category
- operations Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
Read excerpt
# Revenue Operations
Marketing, sales, and customer success each optimize their own metric while the customer experience and the revenue number fall through the seams between them: marketing is measured on leads so it sends volume, sales is measured on closes so it cherry-picks, CS is measured on renewals so it inherits bad-fit customers. Each team is locally optimal and globally broken. RevOps fixes the seams - and the single highest-leverage fix is one funnel with one set of definitions the whole org signs.
## Operating procedure
Definitions come first because every metric, SLA, and forecast downstream inherits them; instrumenting an undefined funnel just automates the disagreement.
### Step 1: Gather inputs
1. The current funnel stages as each team describes them - collect all three versions; the deltas are the diagnosis.
2. The CRM and data stack, and where shadow spreadsheets live.
3. Current targets: revenue, pipeline, renewal.
4. Known seam failures - lead disputes, stalled handoffs, surprise churn. Label anecdotes as anecdotes.