Agent skill

Revenue Operations

by borghei in borghei/Claude-Skills

Analyzes pipeline coverage, tracks forecast accuracy with MAPE, and calculates GTM efficiency metrics for SaaS revenue optimization

MITAuto-check passedMarketing & SEO

Install Revenue Operations

skills CLI
$ npx skills add borghei/Claude-Skills --skill revenue-operations -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install borghei/Claude-Skills revenue-operations --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/business-growth/revenue-operations .claude/skills/revenue-operations && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
revenue-operations
GitHub stars
891
Token cost
~4.1k tokens
SKILL.md length
1,451 words
Files
14 (incl. scripts, references, assets)
Skills in repo
354
Repo updated
First seen
Licence
MIT

At a glance

Analyzes pipeline coverage, tracks forecast accuracy with MAPE, and calculates GTM efficiency metrics for SaaS revenue optimization

  • Works in 6 steps: Pipeline Analyzer → Forecast Accuracy Tracker → GTM Efficiency Calculator → …
  • Tasks that involve Go-to-market strategy
  • SKILL.md covers Table of Contents, Clarify First, Quick Start and Tools Overview, plus 8 more sections
  • Runs Python scripts from its folder; calls python

What it does

Revenue Operations is an agent skill from borghei/Claude-Skills. Analyzes pipeline coverage, tracks forecast accuracy with MAPE, and calculates GTM efficiency metrics for SaaS revenue optimization

Its SKILL.md is about 4.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 16 other files, including scripts, reference files and assets (for example `assets/expected_output.json`, `assets/forecast_report_template.md` and `assets/gtm_dashboard_template.md`).

It sits in Marketing & SEO, covering Go-to-market strategy. The repository describes itself as: 385 AI skills, 77 expert agents, and 900 stdlib Python tools for every team: engineering, PM, marketing, C-level, compliance, business ops, research, and a LinkedIn toolkit… The licence is MIT.

When your agent uses it

  • Tasks that involve Go-to-market strategy

Example prompts

  • “Use the revenue-operations skill to analyz pipeline coverage, tracks forecast accuracy with MAPE, and calculates GTM efficiency metrics for SaaS…”
  • “/revenue-operations”

Requirements

  • Python 3

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Pipeline Analyzer
  2. Forecast Accuracy Tracker
  3. GTM Efficiency Calculator
  4. pipeline_analyzer.py
  5. forecast_accuracy_tracker.py
  6. gtm_efficiency_calculator.py

What it can do on your machine

Read from SKILL.md and the folder at commit 4a698e8. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 3 files in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • python

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Revenue Operations loads about 4.1k tokens when it runs, and up to ~12k if it reads all its reference files. Until then it costs about 38 tokens; SKILL.md has 1,451 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~38
When it runs · the whole SKILL.md, loaded when a task matches
~4.1k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~12k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from borghei/Claude-Skills at commit 4a698e8, republished under its MIT licence (© borghei). 1,451 words, ~4,070 tokens.

Download SKILL.mdSave it as .claude/skills/revenue-operations/SKILL.md (or your agent's skills folder). This skill also uses 13 other files; get the full folder from GitHub.
name
revenue-operations
description
Analyzes pipeline coverage, tracks forecast accuracy with MAPE, and calculates GTM efficiency metrics for SaaS revenue optimization
license
MIT + Commons Clause
metadata.version
1.0.0
metadata.author
borghei
metadata.category
business-growth
metadata.domain
revenue-ops
metadata.updated
2026-03-31
metadata.tags
revops, pipeline, forecast, gtm-efficiency, saas-metrics

Revenue Operations

Pipeline analysis, forecast accuracy tracking, and GTM efficiency measurement for SaaS revenue teams.

Table of Contents


Clarify First

Before running the analysis, confirm these inputs. If any is unknown or vague, ASK — do not assume:

  • Which analysis — pipeline health, forecast accuracy, or GTM efficiency (selects the script and its input schema)
  • Quota / target — the number pipeline coverage and Magic Number are measured against
  • Data export readiness — deals with stage/value/age/close-date, or forecast-vs-actual periods (the tools consume specific JSON; forecast trend needs 3+ periods)
  • Company stage + sales motion — seed vs growth, PLG vs enterprise (benchmarks vary widely by stage and motion)

Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the output.

Quick Start

bash
# Analyze pipeline health and coverage
python scripts/pipeline_analyzer.py --input assets/sample_pipeline_data.json --format text

# Track forecast accuracy over multiple periods
python scripts/forecast_accuracy_tracker.py assets/sample_forecast_data.json --format text

# Calculate GTM efficiency metrics
python scripts/gtm_efficiency_calculator.py assets/sample_gtm_data.json --format text

Tools Overview

1. Pipeline Analyzer

Analyzes sales pipeline health including coverage ratios, stage conversion rates, deal velocity, aging risks, and concentration risks.

Input: JSON file with deals, quota, and stage configuration Output: Coverage ratios, conversion rates, velocity metrics, aging flags, risk assessment

Usage:

bash
# Text report (human-readable)
python scripts/pipeline_analyzer.py --input pipeline.json --format text

# JSON output (for dashboards/integrations)
python scripts/pipeline_analyzer.py --input pipeline.json --format json

Key Metrics Calculated:

  • Pipeline Coverage Ratio -- Total pipeline value / quota target (healthy: 3-4x)
  • Stage Conversion Rates -- Stage-to-stage progression rates
  • Sales Velocity -- (Opportunities x Avg Deal Size x Win Rate) / Avg Sales Cycle
  • Deal Aging -- Flags deals exceeding 2x average cycle time per stage
  • Concentration Risk -- Warns when >40% of pipeline is in a single deal
  • Coverage Gap Analysis -- Identifies quarters with insufficient pipeline

Input Schema:

json
{
  "quota": 500000,
  "stages": ["Discovery", "Qualification", "Proposal", "Negotiation", "Closed Won"],
  "average_cycle_days": 45,
  "deals": [
    {
      "id": "D001",
      "name": "Acme Corp",
      "stage": "Proposal",
      "value": 85000,
      "age_days": 32,
      "close_date": "2025-03-15",
      "owner": "rep_1"
    }
  ]
}
2. Forecast Accuracy Tracker

Tracks forecast accuracy over time using MAPE, detects systematic bias, analyzes trends, and provides category-level breakdowns.

Input: JSON file with forecast periods and optional category breakdowns Output: MAPE score, bias analysis, trends, category breakdown, accuracy rating

Usage:

bash
# Track forecast accuracy
python scripts/forecast_accuracy_tracker.py forecast_data.json --format text

# JSON output for trend analysis
python scripts/forecast_accuracy_tracker.py forecast_data.json --format json

Key Metrics Calculated:

  • MAPE -- Mean Absolute Percentage Error: mean(|actual - forecast| / |actual|) x 100
  • Forecast Bias -- Over-forecasting (positive) vs under-forecasting (negative) tendency
  • Weighted Accuracy -- MAPE weighted by deal value for materiality
  • Period Trends -- Improving, stable, or declining accuracy over time
  • Category Breakdown -- Accuracy by rep, product, segment, or any custom dimension

Accuracy Ratings:

RatingMAPE RangeInterpretation
Excellent<10%Highly predictable, data-driven process
Good10-15%Reliable forecasting with minor variance
Fair15-25%Needs process improvement
Poor>25%Significant forecasting methodology gaps

Input Schema:

json
{
  "forecast_periods": [
    {"period": "2025-Q1", "forecast": 480000, "actual": 520000},
    {"period": "2025-Q2", "forecast": 550000, "actual": 510000}
  ],
  "category_breakdowns": {
    "by_rep": [
      {"category": "Rep A", "forecast": 200000, "actual": 210000},
      {"category": "Rep B", "forecast": 280000, "actual": 310000}
    ]
  }
}
3. GTM Efficiency Calculator

Calculates core SaaS GTM efficiency metrics with industry benchmarking, ratings, and improvement recommendations.

Input: JSON file with revenue, cost, and customer metrics Output: Magic Number, LTV:CAC, CAC Payback, Burn Multiple, Rule of 40, NDR with ratings

Usage:

bash
# Calculate all GTM efficiency metrics
python scripts/gtm_efficiency_calculator.py gtm_data.json --format text

# JSON output for dashboards
python scripts/gtm_efficiency_calculator.py gtm_data.json --format json

Key Metrics Calculated:

MetricFormulaTarget
Magic NumberNet New ARR / Prior Period S&M Spend>0.75
LTV:CAC(ARPA x Gross Margin / Churn Rate) / CAC>3:1
CAC PaybackCAC / (ARPA x Gross Margin) months<18 months
Burn MultipleNet Burn / Net New ARR<2x
Rule of 40Revenue Growth % + FCF Margin %>40%
Net Dollar Retention(Begin ARR + Expansion - Contraction - Churn) / Begin ARR>110%

Input Schema:

json
{
  "revenue": {
    "current_arr": 5000000,
    "prior_arr": 3800000,
    "net_new_arr": 1200000,
    "arpa_monthly": 2500,
    "revenue_growth_pct": 31.6
  },
  "costs": {
    "sales_marketing_spend": 1800000,
    "cac": 18000,
    "gross_margin_pct": 78,
    "total_operating_expense": 6500000,
    "net_burn": 1500000,
    "fcf_margin_pct": 8.4
  },
  "customers": {
    "beginning_arr": 3800000,
    "expansion_arr": 600000,
    "contraction_arr": 100000,
    "churned_arr": 300000,
    "annual_churn_rate_pct": 8
  }
}

Revenue Operations Workflows

Weekly Pipeline Review

Use this workflow for your weekly pipeline inspection cadence.

  1. Generate pipeline report:

    bash
    python scripts/pipeline_analyzer.py --input current_pipeline.json --format text
  2. Review key indicators:

    • Pipeline coverage ratio (is it above 3x quota?)
    • Deals aging beyond threshold (which deals need intervention?)
    • Concentration risk (are we over-reliant on a few large deals?)
    • Stage distribution (is there a healthy funnel shape?)
  3. Document using template: Use assets/pipeline_review_template.md

  4. Action items: Address aging deals, redistribute pipeline concentration, fill coverage gaps

Forecast Accuracy Review

Use monthly or quarterly to evaluate and improve forecasting discipline.

  1. Generate accuracy report:

    bash
    python scripts/forecast_accuracy_tracker.py forecast_history.json --format text
  2. Analyze patterns:

    • Is MAPE trending down (improving)?
    • Which reps or segments have the highest error rates?
    • Is there systematic over- or under-forecasting?
  3. Document using template: Use assets/forecast_report_template.md

  4. Improvement actions: Coach high-bias reps, adjust methodology, improve data hygiene

GTM Efficiency Audit

Use quarterly or during board prep to evaluate go-to-market efficiency.

  1. Calculate efficiency metrics:

    bash
    python scripts/gtm_efficiency_calculator.py quarterly_data.json --format text
  2. Benchmark against targets:

    • Magic Number signals GTM spend efficiency
    • LTV:CAC validates unit economics
    • CAC Payback shows capital efficiency
    • Rule of 40 balances growth and profitability
  3. Document using template: Use assets/gtm_dashboard_template.md

  4. Strategic decisions: Adjust spend allocation, optimize channels, improve retention

Quarterly Business Review

Combine all three tools for a comprehensive QBR analysis.

  1. Run pipeline analyzer for forward-looking coverage
  2. Run forecast tracker for backward-looking accuracy
  3. Run GTM calculator for efficiency benchmarks
  4. Cross-reference pipeline health with forecast accuracy
  5. Align GTM efficiency metrics with growth targets

Reference Documentation

ReferenceDescription
RevOps Metrics GuideComplete metrics hierarchy, definitions, formulas, and interpretation
Pipeline Management FrameworkPipeline best practices, stage definitions, conversion benchmarks
GTM Efficiency BenchmarksSaaS benchmarks by stage, industry standards, improvement strategies

Templates

TemplateUse Case
Pipeline Review TemplateWeekly/monthly pipeline inspection documentation
Forecast Report TemplateForecast accuracy reporting and trend analysis
GTM Dashboard TemplateGTM efficiency dashboard for leadership review
Sample Pipeline DataExample input for pipeline_analyzer.py
Expected OutputReference output from pipeline_analyzer.py

Tool Reference

1. pipeline_analyzer.py

Analyzes sales pipeline health including coverage ratios, stage conversion rates, sales velocity, deal aging risks, and concentration risks.

bash
python scripts/pipeline_analyzer.py --input pipeline.json --format text
python scripts/pipeline_analyzer.py --input pipeline.json --format json
FlagTypeDescription
--inputrequiredPath to JSON file with deals, quota, and stage configuration
--formatoptionalOutput format: text (default) or json
Show full SKILL.md (592 more words)Show less
2. forecast_accuracy_tracker.py

Tracks forecast accuracy over time using MAPE, detects systematic bias, analyzes trends, and provides category-level breakdowns.

bash
python scripts/forecast_accuracy_tracker.py forecast_data.json --format text
python scripts/forecast_accuracy_tracker.py forecast_data.json --format json
FlagTypeDescription
forecast_data.jsonpositionalPath to JSON file with forecast periods and optional category breakdowns
--formatoptionalOutput format: text (default) or json
3. gtm_efficiency_calculator.py

Calculates core SaaS GTM efficiency metrics with industry benchmarking, ratings, and improvement recommendations.

bash
python scripts/gtm_efficiency_calculator.py gtm_data.json --format text
python scripts/gtm_efficiency_calculator.py gtm_data.json --format json
FlagTypeDescription
gtm_data.jsonpositionalPath to JSON file with revenue, cost, and customer metrics
--formatoptionalOutput format: text (default) or json

Troubleshooting

ProblemLikely CauseResolution
Pipeline coverage below 3x quotaInsufficient top-of-funnel activity or poor lead-to-opportunity conversionAudit lead sources and conversion rates by stage; increase outbound activity or marketing spend in underperforming channels
Forecast MAPE above 25%Inconsistent deal stage criteria, sandbagging, or lack of inspection rigorStandardize stage exit criteria; implement weekly pipeline reviews tied to velocity not just activity; coach high-bias reps individually
Magic Number below 0.5GTM spend is inefficient relative to new ARR generatedReview channel ROI; reduce spend in low-performing channels; improve rep productivity before adding headcount
LTV:CAC below 3:1CAC too high or churn eroding lifetime valueAddress churn first (use churn-prevention skill); then optimize CAC by shifting to lower-cost acquisition channels
Deals slipping past forecast close dateLack of deal qualification, missing champion, or no compelling eventImplement MEDDIC/BANT qualification; require compelling event documentation for commit-stage deals
Pipeline heavily concentrated in early stagesPoor stage progression indicating stalled deals or loose qualificationSet maximum stage age limits; implement automated alerts for deals exceeding 2x average cycle per stage
Net Dollar Retention below 100%Contraction and churn outpacing expansion revenuePrioritize expansion playbooks for healthy accounts; conduct exit interviews for churning accounts; review pricing tier structure

Success Criteria

  • Pipeline coverage ratio stabilizes at 3-4x quota with healthy stage distribution
  • Forecast MAPE improves to below 15% (Good) or below 10% (Excellent) within two quarters
  • Magic Number exceeds 0.75 indicating efficient GTM spend
  • LTV:CAC ratio exceeds 3:1 with CAC payback under 18 months
  • Rule of 40 score exceeds 40% (revenue growth % + FCF margin %)
  • Net Dollar Retention exceeds 110% driven by expansion revenue
  • Deal slippage rate drops below 30% (improved from 2024 industry average of 44%)

Scope & Limitations

In scope: Pipeline health analysis (coverage, velocity, aging, concentration), forecast accuracy measurement (MAPE, bias, trends, category breakdowns), GTM efficiency metrics (Magic Number, LTV:CAC, CAC Payback, Burn Multiple, Rule of 40, NDR), weekly/monthly/quarterly review workflows, and QBR preparation combining all three analysis dimensions.

Out of scope: CRM system administration or data extraction (tools consume JSON exports), deal-level sales coaching (tools flag deals but do not prescribe sales tactics), marketing attribution modeling, customer success health scoring (use customer-success-manager skill), and real-time pipeline monitoring. Tools analyze point-in-time snapshots; continuous monitoring requires integration with CRM/BI platforms.

Limitations: Benchmarks are based on aggregate SaaS industry data and vary by company stage (seed, Series A-C, growth, public), vertical, and sales motion (PLG vs enterprise). Pipeline analysis assumes deal data includes accurate stage, value, age, and close date fields. Forecast accuracy requires minimum 3 periods for trend analysis. GTM metrics require accurate financial data that may not be available in early-stage companies.


Integration Points

  • sales-engineer -- Pipeline deals requiring technical validation route through sales-engineer POC and RFP workflows
  • customer-success-manager -- Post-close handoff; NDR metrics depend on customer success health scoring and expansion plays
  • pricing-strategy -- Pricing model impacts pipeline velocity, deal sizes, and conversion rates; pricing changes require pipeline reforecasting
  • churn-prevention -- Churn rate directly impacts LTV:CAC and NDR metrics; reducing churn improves all GTM efficiency measures
  • c-level-advisor -- GTM efficiency metrics feed directly into board-level reporting and strategic resource allocation decisions

© borghei, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 13 other files (scripts, references, assets) in business-growth/revenue-operations of borghei/Claude-Skills.

  • SKILL.md
  • assets/expected_output.json
  • assets/forecast_report_template.md
  • assets/gtm_dashboard_template.md
  • assets/pipeline_review_template.md
  • assets/sample_forecast_data.json
  • assets/sample_gtm_data.json
  • assets/sample_pipeline_data.json
  • references/gtm-efficiency-benchmarks.md
  • references/pipeline-management-framework.md
  • references/revops-metrics-guide.md
  • scripts/forecast_accuracy_tracker.py
  • scripts/gtm_efficiency_calculator.py
  • scripts/pipeline_analyzer.py

Open the folder on GitHubat commit 4a698e8

Compare with similar skills

Revenue Operations next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Revenue Operations compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Revenue Operations this skillborghei/Claude-Skills891—~4.1kAutomated safety check: PassMIT
Marketing PlanNexus-JPF/note-companion8705 repos~5.2kAutomated safety check: PassMIT
Revenue Centric Designheliocosta-dev/revenue-centric-design740—~1.6kAutomated safety check: PassCustom licence
Startup Designferdinandobons/startup-skill1.2k—~8.1kAutomated safety check: PassMIT
Jaredrhod Marketingjaredrhod/ai-marketing-skills282—~584Automated safety check: PassCC-BY-SA-4.0
Traffic Acquisitionvivy-yi/xiaohongshu-skills4811 repos~4kAutomated safety check: PassNone

Similar skills

  • Marketing Plan

    Nexus-JPF/note-companion

    When the user needs a comprehensive marketing plan for a client, a company they advise, or their own product.

    870 GitHub starsUsed in 5 repos~5.2k tokens
    Marketing & SEOAuto-check passed
  • Revenue Centric Design

    heliocosta-dev/revenue-centric-design

    Playbook for designing SaaS and startup products that convert, retain, and monetize — landing pages & CRO, checkout & forms, onboarding/activation, churn reduction, pricing psychology, dashboards…

    740 GitHub stars~1.6k tokensUpdated 1 mo ago
    Marketing & SEOAuto-check passed
  • Startup Design

    ferdinandobons/startup-skill

    Design, validate, and plan a startup from scratch. An agent skill from ferdinandobons/startup-skill.

    1.2k GitHub stars~8.1k tokensUpdated 3 mo ago
    Marketing & SEOAuto-check passed
  • Jaredrhod Marketing

    jaredrhod/ai-marketing-skills

    Run any marketing task the way jaredrhod actually runs it. An agent skill from jaredrhod/ai-marketing-skills.

    282 GitHub stars~584 tokensUpdated 1 mo ago
    Marketing & SEOAuto-check passed
  • Traffic Acquisition

    vivy-yi/xiaohongshu-skills

    A skill your agent uses when driving traffic to Xiaohongshu account from external sources, acquiring new followers beyond organic discovery, implementing multi-platform growth strategy, or scaling…

    481 GitHub starsUsed in 1 repo~4k tokens
    Marketing & SEOAuto-check passed
  • Amazon Product Research

    nexscope-ai/Amazon-Skills

    Comprehensive product research and opportunity analysis for Amazon sellers.

    744 GitHub starsUsed in 1 repo~3.2k tokens
    Marketing & SEOAuto-check passed

More from borghei/Claude-Skills

All 354 skills in this repo
  • Agent Harness

    borghei/Claude-Skills

    Test and evaluation harness for AI agents — scenario suites, deterministic replay, regression diffing, cost and latency budgets.

    891 GitHub stars~3.1k tokensUpdated 3 days ago
    Auto-check passed
  • Agents In The Team

    borghei/Claude-Skills

    Run delivery when AI coding and ops agents take tickets. An agent skill from borghei/Claude-Skills.

    891 GitHub stars~4.2k tokensUpdated 3 days ago
    Auto-check passed
  • AI Content Disclosure

    borghei/Claude-Skills

    Check AI-generated marketing content and reviews for required disclosures under the EU AI Act, FTC rules and platform AI-label policies.

    891 GitHub stars~3.4k tokensUpdated 3 days ago
    Auto-check passed
  • AI Prototyping

    borghei/Claude-Skills

    Idea to AI-generated prototype to customer validation to engineering handoff.

    891 GitHub stars~3.6k tokensUpdated 3 days ago
    Auto-check passed
  • Analytics Engineer

    borghei/Claude-Skills

    Analytics engineering across data modeling, dbt, transformation, and semantic layers.

    891 GitHub stars~3.4k tokensUpdated 3 days ago
    Auto-check passed
  • Ansoff Matrix

    borghei/Claude-Skills

    Ansoff Matrix — 4-quadrant framework for growth options: market penetration, market/product development, and diversification.

    891 GitHub stars~2.2k tokensUpdated 3 days ago
    Auto-check passed

Categories

Questions about Revenue Operations

What does Revenue Operations do?

Analyzes pipeline coverage, tracks forecast accuracy with MAPE, and calculates GTM efficiency metrics for SaaS revenue optimization. Revenue Operations is an agent skill from borghei/Claude-Skills.

When should I use Revenue Operations?

Revenue Operations fits situations like: tasks that involve Go-to-market strategy.

How do I install Revenue Operations in Claude Code?

Run `npx skills add borghei/Claude-Skills --skill revenue-operations -a claude-code`. Or copy the skill folder (business-growth/revenue-operations in borghei/Claude-Skills) into .claude/skills/revenue-operations in your project. Claude Code loads it when a task matches its description.

How do I install Revenue Operations in Codex?

Run `npx skills add borghei/Claude-Skills --skill revenue-operations -a codex`. Or copy the skill folder (business-growth/revenue-operations in borghei/Claude-Skills) into .agents/skills/revenue-operations in your project. Codex loads it when a task matches its description.

Can I use Revenue Operations in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add borghei/Claude-Skills --skill revenue-operations -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/revenue-operations, .gemini/skills/revenue-operations, .github/skills/revenue-operations and .opencode/skills/revenue-operations in your project.

What does Revenue Operations need to run?

Going by SKILL.md and its folder, Revenue Operations needs Python for the scripts in its folder and the command-line tools its instructions call (python). Our summary lists: Python 3.

Does Revenue Operations access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Revenue Operations safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Revenue Operations use?

Revenue Operations is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Revenue Operations use?

About 4.1k tokens (SKILL.md is roughly 16k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 7.7k tokens, read only when the agent opens those files.

What are the alternatives to Revenue Operations?

Skills that share tags, products or a category with Revenue Operations: Marketing Plan (Nexus-JPF/note-companion, 870 stars), Revenue Centric Design (heliocosta-dev/revenue-centric-design, 740 stars), Startup Design (ferdinandobons/startup-skill, 1.2k stars) and Jaredrhod Marketing (jaredrhod/ai-marketing-skills, 282 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Revenue Operations?

borghei (a GitHub user) maintains it in borghei/Claude-Skills, which has 891 GitHub stars. The repository holds 354 skills in this directory. The repository was last updated on October 7, 2026.

Source: borghei/Claude-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.