Agent skill

Chief Revenue Officer

by cbrock84 in cbrock84/headcount

Owns the revenue engine end to end: sales, monetization, pricing, customer success, retention, and partnerships.

MITAuto-check passedSales & Support

Install Chief Revenue Officer

skills CLI
$ npx skills add cbrock84/headcount --skill chief-revenue-officer -a claude-code

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

GitHub CLI
$ gh skill install cbrock84/headcount chief-revenue-officer --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/cbrock84/headcount.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/revenue/skills/chief-revenue-officer .claude/skills/chief-revenue-officer && 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
chief-revenue-officer
GitHub stars
2k
Token cost
~1.4k tokens
SKILL.md length
837 words
Files
1
Skills in repo
178
Repo updated
First seen
Licence
MIT

At a glance

Owns the revenue engine end to end: sales, monetization, pricing, customer success, retention, and partnerships.

  • Works in 6 steps: Decision or recommendation — one… → Reasoning — the two or three things that… → What this costs — money, time, capacity,… → …
  • Decide which segments to pursue and which to decline
  • SKILL.md covers Why this role exists, Remit, A forecast is a commitment or… and Discounting is a pricing…, plus 7 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Chief Revenue Officer is an agent skill from cbrock84/headcount. Owns the revenue engine end to end: sales, monetization, pricing, customer success, retention, and partnerships. Use this for pricing and packaging decisions, sales strategy and coverage, forecast and pipeline health, churn and expansion, partner and channel strategy, or when marketing-sourced demand is not converting. Also use to decide which segments to pursue and which to decline.

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Sales & Support, covering Go-to-market strategy, Customer success and Pricing strategy. The repository describes itself as: An agent organization structured as a company — 15+ departments, 125+ skills, each independently installable, citing the standards and regulators that settle the question. Runs… The licence is MIT.

When your agent uses it

  • Decide which segments to pursue and which to decline
  • Tasks that involve Go-to-market strategy
  • Tasks that involve Customer success

Example prompts

  • “/chief-revenue-officer”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Decision or recommendation — one sentence, stated plainly.
  2. Reasoning — the two or three things that actually drove it.
  3. What this costs — money, time, capacity, or optionality given up.
  4. Assumptions — what must hold for this to be right.
  5. What would change my mind — the specific evidence that would reverse this.
  6. Handoffs — who does what next, by when.

What it can do on your machine

Read from SKILL.md and the folder at commit 98d1c17. 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

    No scripts in the folder and no shell commands in SKILL.md.

    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

Chief Revenue Officer loads about 1.4k tokens when it runs. Until then it costs about 102 tokens; SKILL.md has 837 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~102
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k

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); files beside SKILL.md are not scanned.

SKILL.md

The full file from cbrock84/headcount at commit 98d1c17, republished under its MIT licence (© cbrock84). 837 words, ~1,427 tokens.

Download SKILL.mdSave it as .claude/skills/chief-revenue-officer/SKILL.md (or your agent's skills folder).
name
chief-revenue-officer
description
Owns the revenue engine end to end: sales, monetization, pricing, customer success, retention, and partnerships. Use this for pricing and packaging decisions, sales strategy and coverage, forecast and pipeline health, churn and expansion, partner and channel strategy, or when marketing-sourced demand is not converting. Also use to decide which segments to pursue and which to decline.

Chief Revenue Officer

Why this role exists

The executive accountable for this function. It exists so that one agent — not the orchestrator, and not whichever specialist happens to be in the conversation — owns the call when the specialists disagree or when a decision crosses their boundaries.

Remit

  • Pipeline, forecast, and conversion
  • Pricing and packaging
  • Retention, expansion, and churn
  • Partnerships and channel

A forecast is a commitment or it is theater

Most forecasting problems are not analytical. They are that nobody agreed what a stage means, so "proposal sent" describes both a deal closing next week and one that went quiet in March.

Define stages by observable buyer behavior, not seller optimism. "Customer has confirmed budget and named a decision date" is checkable; "customer is very interested" is a feeling. Stages defined this way produce conversion rates that mean something, and conversion rates that mean something are what make the forecast a forecast.

Inspect the pipeline for deals that have stopped moving, not just deals that might close. Age in stage is the most reliable early signal of a deal that has already been lost and not yet recorded, and clearing them out costs a painful quarter once rather than a wrong number every quarter.

Call the number you believe rather than the number that is wanted. A CRO who is right about a bad quarter keeps the ability to be believed about the next good one.

Discounting is a pricing decision made by whoever is most desperate

Every unmanaged discount is a permanent change to the price your market believes in, made by the person under the most pressure at the worst possible moment. It shows up later as an expansion conversation that starts from a number nobody intended.

Control the shape rather than the instance: what may be given, by whom, in exchange for what. A discount traded for a longer term, a case study, or annual prepayment is a trade; a discount given to close this month is a transfer.

Track realized price by segment over time. A slowly falling average is the clearest evidence that discretion has become the pricing policy, and it is invisible in any single deal. Pricing structure itself belongs with revenue:pricing-and-packaging and its recognition consequences with finance:chief-financial-officer.

Retention is where revenue is actually made

Acquiring a customer costs multiples of keeping one, so in any business with recurring revenue the retention rate sets the ceiling on everything else. Growth on a leaking base is a treadmill that gets steeper.

The churn that matters is usually decided in the first ninety days, not at renewal. A customer who never reached the outcome they bought will not be rescued by a renewal conversation, and the signals — unused seats, an unfinished implementation, the champion going quiet — are visible long before the date.

Gross and net retention answer different questions and both are needed. Net retention above one hundred percent can conceal real churn masked by expansion in a few large accounts, which is a pleasant number and a fragile business. See revenue:retention and customer-experience:customer-success-management.

Show full SKILL.md (329 more words)Show less

Marketing volume and revenue quality pull against each other

The lead count is easy to move and easy to move in ways that make it worthless. Where demand generation is measured on volume and revenue is measured on conversion, the two functions optimize against each other while both report success.

The fix is a shared definition of a qualified opportunity, agreed by both and applied to both scorecards, plus a regular look at which sources actually produce closed revenue rather than meetings. Sources differ enormously by that measure and barely at all by lead count.

When sales says the leads are bad and marketing says sales is not working them, both are usually partly right and the definition is the thing that is broken.

What this role owns

These are the artifacts of record. Where two of them disagree, this one is right:

  • The price list
  • Segment and territory coverage
  • The forecast of record

Escalation

Escalate to Chief Executive when hitting the number requires discounting that changes the business model; to Finance on any pricing change affecting recognized revenue.

Never

  • Never book revenue the business cannot deliver
  • Never fix a conversion problem by adding pipeline
  • Do not define pipeline stages by seller sentiment
  • Do not let discounting happen deal by deal without a stated trade
  • Do not report a forecast you do not believe

Works with

Pairs with Marketing on demand quality; with Finance on pricing and recognition; with Product on what customers are actually buying.

Return contract

End every engagement with these sections, in this order:

  1. Decision or recommendation — one sentence, stated plainly.
  2. Reasoning — the two or three things that actually drove it.
  3. What this costs — money, time, capacity, or optionality given up.
  4. Assumptions — what must hold for this to be right.
  5. What would change my mind — the specific evidence that would reverse this.
  6. Handoffs — who does what next, by when.

If any section is empty, say so rather than padding it.

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

Files

Just SKILL.md in plugins/revenue/skills/chief-revenue-officer of cbrock84/headcount.

Open the folder on GitHubat commit 98d1c17

Compare with similar skills

Chief Revenue Officer 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.

Chief Revenue Officer compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Chief Revenue Officer this skillcbrock84/headcount2k—~1.4kAutomated safety check: PassMIT
Discount Marketing Strategykostja94/marketing-skills1k—~2kAutomated safety check: PassMIT
Product Adoptionmagnus919/agent-skills115—~1.7kAutomated safety check: PassMIT
Gtm Technical Product Pricinggithub/awesome-copilot40k1 repos~3.2kAutomated safety check: PassMIT
Beachhead Segmentphuryn/pm-skills27k—~1.5kAutomated safety check: PassMIT
Business Growth Skillsalirezarezvani/claude-skills28k—~506Automated safety check: PassMIT

Similar skills

  • Discount Marketing Strategy

    kostja94/marketing-skills

    When the user wants to plan, implement, or optimize discount and promotional pricing strategy.

    1k GitHub stars~2k tokensUpdated 5 days ago
    Sales & SupportAuto-check passed
  • Product Adoption

    magnus919/agent-skills

    Diagnose and design product adoption for onboarding, activation, behavior change, feature discovery, rollout, and sustained use after launch.

    115 GitHub stars~1.7k tokensUpdated yesterday
    Sales & SupportAuto-check passed
  • Gtm Technical Product Pricing

    github/awesome-copilot

    Official

    Pricing strategy for technical products. An agent skill from github/awesome-copilot.

    40k GitHub starsUsed in 1 repo~3.2k tokens
    Marketing & SEOAuto-check passed
  • Beachhead Segment

    phuryn/pm-skills

    Identify the first beachhead market segment for a product launch.

    27k GitHub stars~1.5k tokensUpdated yesterday
    Marketing & SEOAuto-check passed
  • Business Growth Skills

    alirezarezvani/claude-skills

    Router/index for the 4 business & growth skills bundled in this plugin: customer-success-manager (health scoring, churn risk, expansion), sales-engineer (RFP analysis, competitive matrices, PoC…

    28k GitHub stars~506 tokensUpdated 1 mo ago
    Sales & SupportAuto-check passed
  • Gtm Account Health Scorer

    criptogus/agent-evolve-network

    Scores customer accounts on adoption, sentiment, and commercial signals; flags risk and remediation triggers.

    288 GitHub stars~556 tokensUpdated 2 days ago
    Marketing & SEOAuto-check passed

More from cbrock84/headcount

All 178 skills in this repo
  • Agent Hierarchy

    cbrock84/headcount

    Designs orchestrator-and-subagent hierarchies for a repository — splitting agents by exclusive write surface, pairing every producer with an independent auditor, and enforcing the split with a…

    2k GitHub stars~1.2k tokensUpdated 23 days ago
    Auto-check passed
  • Access And Identity

    cbrock84/headcount

    Designs and audits who can reach what — authentication, authorization models, privileged access, service credentials, and joiner-mover-leaver process.

    2k GitHub stars~1.1k tokensUpdated 23 days ago
    Auto-check passed
  • Account Based Marketing

    cbrock84/headcount

    Concentrates marketing and sales effort on a named set of accounts rather than on volume — qualifying whether the model fits your economics at all, building the account list and the buying group…

    2k GitHub stars~1.2k tokensUpdated 23 days ago
    Auto-check passed
  • Activation

    cbrock84/headcount

    Gets new users from signup to first real value — signup flow, onboarding, time-to-value, and the early experience that determines whether someone becomes a user or a lapsed account.

    2k GitHub stars~865 tokensUpdated 23 days ago
    Auto-check passed
  • AI ML Governance

    cbrock84/headcount

    Governs models and AI systems in production — intended use, evaluation, monitoring, human oversight, documentation, and the decision to deploy or retire.

    2k GitHub stars~1k tokensUpdated 23 days ago
    Auto-check passed
  • AI Research Analyst

    cbrock84/headcount

    Produces executive-level research — market sizing, competitor mapping, trend analysis, and strategic intelligence — grounded in cited sources with the confidence in each claim made explicit.

    2k GitHub stars~916 tokensUpdated 23 days ago
    Auto-check passed

Questions about Chief Revenue Officer

What does Chief Revenue Officer do?

Owns the revenue engine end to end: sales, monetization, pricing, customer success, retention, and partnerships. Chief Revenue Officer is an agent skill from cbrock84/headcount. Owns the revenue engine end to end: sales, monetization, pricing, customer success, retention, and partnerships.

When should I use Chief Revenue Officer?

Chief Revenue Officer fits situations like: decide which segments to pursue and which to decline; tasks that involve Go-to-market strategy; tasks that involve Customer success.

How do I install Chief Revenue Officer in Claude Code?

Run `npx skills add cbrock84/headcount --skill chief-revenue-officer -a claude-code`. Or copy the skill folder (plugins/revenue/skills/chief-revenue-officer in cbrock84/headcount) into .claude/skills/chief-revenue-officer in your project. Claude Code loads it when a task matches its description.

How do I install Chief Revenue Officer in Codex?

Run `npx skills add cbrock84/headcount --skill chief-revenue-officer -a codex`. Or copy the skill folder (plugins/revenue/skills/chief-revenue-officer in cbrock84/headcount) into .agents/skills/chief-revenue-officer in your project. Codex loads it when a task matches its description.

Can I use Chief Revenue Officer 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 cbrock84/headcount --skill chief-revenue-officer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/chief-revenue-officer, .gemini/skills/chief-revenue-officer, .github/skills/chief-revenue-officer and .opencode/skills/chief-revenue-officer in your project.

What does Chief Revenue Officer need to run?

SKILL.md names no scripts, command-line tools or credentials: Chief Revenue Officer is instructions for the agent only.

Does Chief Revenue Officer 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 Chief Revenue Officer 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. Review the folder before installing.

What licence does Chief Revenue Officer use?

Chief Revenue Officer is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Chief Revenue Officer use?

About 1.4k tokens (SKILL.md is roughly 5.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Chief Revenue Officer?

Skills that share tags, products or a category with Chief Revenue Officer: Discount Marketing Strategy (kostja94/marketing-skills, 1k stars), Product Adoption (magnus919/agent-skills, 115 stars), Gtm Technical Product Pricing (github/awesome-copilot, 40k stars) and Beachhead Segment (phuryn/pm-skills, 27k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Chief Revenue Officer?

cbrock84 (a GitHub user) maintains it in cbrock84/headcount, which has 2,022 GitHub stars. The repository holds 178 skills in this directory. The repository was last updated on September 17, 2026.

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