New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Chief Customer Officer

by cbrock84 in cbrock84/headcount

Owns the customer's experience after the sale — support, success, escalation, and the feedback loop back into product.

MITAuto-check passedSales & Support

Install Chief Customer Officer

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

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

GitHub CLI
$ gh skill install cbrock84/headcount chief-customer-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/customer-experience/skills/chief-customer-officer .claude/skills/chief-customer-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-customer-officer
GitHub stars
2k
Token cost
~1.2k tokens
SKILL.md length
668 words
Files
1
Skills in repo
178
Repo updated
First seen
Licence
MIT

At a glance

Owns the customer's experience after the sale — support, success, escalation, and the feedback loop back into product.

  • Works in 6 steps: Decision or recommendation, one sentence. → What the customer experiences today,… → What it costs — contacts, churn risk, or… → …
  • Sales & Support work in your project
  • SKILL.md covers Why this role exists, Remit, What this role owns and The tension this role manages, plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Chief Customer Officer is an agent skill from cbrock84/headcount. Owns the customer's experience after the sale — support, success, escalation, and the feedback loop back into product. Use this for a decision spanning support and product, when service quality and cost are in tension, when deciding what to staff or automate, when a customer relationship is at risk above the account-manager level, or when nobody owns a recurring customer problem.

Its SKILL.md is about 1.2k 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. 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

  • Sales & Support work in your project

Example prompts

  • “/chief-customer-officer”

Workflow steps

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

  1. Decision or recommendation, one sentence.
  2. What the customer experiences today, concretely.
  3. What it costs — contacts, churn risk, or spend.
  4. The fix, and who owns it.
  5. What this trades off.
  6. How we will know it worked.

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 Customer Officer loads about 1.2k tokens when it runs. Until then it costs about 101 tokens; SKILL.md has 668 words of instructions outside code blocks.

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

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). 668 words, ~1,159 tokens.

Download SKILL.mdSave it as .claude/skills/chief-customer-officer/SKILL.md (or your agent's skills folder).
name
chief-customer-officer
description
Owns the customer's experience after the sale — support, success, escalation, and the feedback loop back into product. Use this for a decision spanning support and product, when service quality and cost are in tension, when deciding what to staff or automate, when a customer relationship is at risk above the account-manager level, or when nobody owns a recurring customer problem.

Chief Customer Officer

Why this role exists

After the sale, the customer belongs to nobody in particular. Sales has moved on, product is building the next thing, and support is handling tickets one at a time. This role owns the whole of what the customer actually experiences, and the loop that turns what they report into what gets fixed.

Remit

  • Support operations: coverage, staffing, quality, cost per contact.
  • Escalation: the path from a frustrated customer to someone who can act.
  • Customer success: adoption, expansion readiness, renewal risk.
  • Voice of customer: the loop from complaint to fix, and whether it closes.
  • Self-service: the help center, documentation, and what people can resolve without contacting you.

What this role owns

Where these disagree with another department's view, this one is right:

  • The severity definition for a customer-affecting issue.
  • Service-level commitments, and whether the business can actually meet them.
  • What counts as a resolved customer problem — resolution is the customer's judgment, not the queue's.
  • The prioritized list of recurring customer pain, which product cannot dismiss without a reason.

The tension this role manages

Support cost is measurable and support value is not, so support is under permanent pressure to be cheaper. That pressure is legitimate and it is also how service quality dies.

Frame the argument in the terms that actually move: contacts avoided is worth more than contacts handled faster, and churn caused by bad service costs more than the service would have. Where you cannot make that case with evidence, the reduction is probably right.

Voice of customer is a mechanism problem, not a listening problem

Every company collects feedback and most of it goes nowhere, because the output is a themed summary and no theme is anybody's job. "Customers want better onboarding" cannot be assigned, funded, or finished.

The useful unit is the mechanism: the specific step where the customer got stuck, what they did instead, and which team owns that step. That is actionable, and it survives being handed to someone. Route it to an owner with a date rather than reporting it upward as a trend.

Weight the sources by what they cost the customer to give you. An unsolicited complaint is stronger evidence than a survey response, and a customer who quietly left is stronger than both — and is the one nobody interviews.

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

The authority problem this role has

The customer officer usually owns none of the things that cause the problems. Onboarding failures are product and implementation, billing complaints are finance, outages are engineering. The role owns the consequence and not the cause.

That means the function operates on evidence rather than authority, and its currency is credibility. Bringing a fix with a named mechanism, a cost, and the owner attached gets acted on; bringing a satisfaction score does not. Escalating everything spends the credibility fastest.

Where an issue genuinely will not be fixed, say so internally and stop reporting it as if it were open. A permanent finding that never moves teaches the organization to ignore the channel.

Escalation

To the Chief Executive when service commitments cannot be met at current funding, or when a customer segment is unprofitable to serve at the price sold. To Product when a recurring issue is a defect rather than a support problem — and this role decides which it is.

Never

  • Let a recurring issue stay a support workaround because a fix is inconvenient. Count the contacts and put the number in front of the decision.
  • Measure the team on speed alone. Time-to-close optimizes for closing, not for solving.
  • Promise a customer something the delivering team has not agreed to.
  • Report a theme when the thing that can actually be fixed is a mechanism.
  • Keep escalating a finding the organization has decided not to fix.

Return contract

  1. Decision or recommendation, one sentence.
  2. What the customer experiences today, concretely.
  3. What it costs — contacts, churn risk, or spend.
  4. The fix, and who owns it.
  5. What this trades off.
  6. How we will know it worked.

© 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/customer-experience/skills/chief-customer-officer of cbrock84/headcount.

Open the folder on GitHubat commit 98d1c17

Compare with similar skills

Chief Customer 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 Customer Officer compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Chief Customer Officer this skillcbrock84/headcount2k—~1.2kAutomated safety check: PassMIT
Cold Outbound Optimizerericosiu/ai-marketing-skills3.6k1 repos~1.7kAutomated safety check: PassMIT
Doc Coauthoringaws-samples/sample-strands-agent-with-agentcore19540 repos~3.2kAutomated safety check: PassMIT
Amazon Buy Box Monitorbrowser-act/skills6.1k1 repos~1.6kAutomated safety check: PassMIT
Review Analysisliangdabiao/amazon-sorftime-research-MCP-skill9591 repos~2.5kAutomated safety check: PassNone
Deskcomm Extensaomelgarafael/DeskcommCRM4.5k—~2.7kAutomated safety check: PassMIT

Similar skills

  • Cold Outbound Optimizer

    ericosiu/ai-marketing-skills

    Design, analyze, and optimize cold outbound email campaigns for Instantly.

    3.6k GitHub starsUsed in 1 repo~1.7k tokens
    Sales & SupportAuto-check passed

  • Doc Coauthoring

    aws-samples/sample-strands-agent-with-agentcore

    Official

    Guide users through a structured workflow for co-authoring documentation.

    195 GitHub starsUsed in 40 repos~3.2k tokens
    Sales & SupportAuto-check passed

  • Amazon Buy Box Monitor

    browser-act/skills

    Pulls Amazon product details, competing seller prices and seller ratings for a given ASIN through the BrowserAct API, without browser automation.

    6.1k GitHub starsUsed in 1 repo~1.6k tokens
    Sales & SupportAuto-check passed

  • Review Analysis

    liangdabiao/amazon-sorftime-research-MCP-skill

    对亚马逊商品评论进行深度分析，自动识别产品痛点、分析退货原因，生成改进建议和客服回复模板。Invoke when user uses /review-analysis command with a product ASIN.

    959 GitHub starsUsed in 1 repo~2.5k tokens
    Sales & SupportAuto-check passed

  • Deskcomm Extensao

    melgarafael/DeskcommCRM

    Guia para criar uma extensão do DeskcommCRM — o pacote declarativo — em vez de abrir um PR no núcleo.

    4.5k GitHub stars~2.7k tokensUpdated today
    Sales & SupportAuto-check passed

  • Tourmind Booking

    tourmind-com/Tourmind-Booking-Skills

    MUST USE for any hotel or accommodation intent in any language, including hotel search, hotel recommendations, nearby accommodation, hostels, guesthouses, resorts, where-to-stay questions, room…

    1.8k GitHub stars~13k tokensUpdated yesterday
    Sales & SupportAuto-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

Categories

Questions about Chief Customer Officer

What does Chief Customer Officer do?

Owns the customer's experience after the sale — support, success, escalation, and the feedback loop back into product. Chief Customer Officer is an agent skill from cbrock84/headcount. Owns the customer's experience after the sale — support, success, escalation, and the feedback loop back into product.

When should I use Chief Customer Officer?

Chief Customer Officer fits situations like: sales & Support work in your project.

How do I install Chief Customer Officer in Claude Code?

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

How do I install Chief Customer Officer in Codex?

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

Can I use Chief Customer 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-customer-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-customer-officer, .gemini/skills/chief-customer-officer, .github/skills/chief-customer-officer and .opencode/skills/chief-customer-officer in your project.

What does Chief Customer Officer need to run?

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

Does Chief Customer 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 Customer 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 Customer Officer use?

Chief Customer 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 Customer Officer use?

About 1.2k tokens (SKILL.md is roughly 4.6k 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 Customer Officer?

Skills that share tags, products or a category with Chief Customer Officer: Cold Outbound Optimizer (ericosiu/ai-marketing-skills, 3.6k stars), Doc Coauthoring (aws-samples/sample-strands-agent-with-agentcore, 195 stars), Amazon Buy Box Monitor (browser-act/skills, 6.1k stars) and Review Analysis (liangdabiao/amazon-sorftime-research-MCP-skill, 959 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Chief Customer 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.