chief-customer-officer SKILL.md skillA
chief-customer-officer from cbrock84/headcount is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add cbrock84/headcount/chief-customer-officer@git:20260903.cc4a2cdPins git:20260903.cc4a2cd in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- cbrock84/headcount
- Path
plugins/customer-experience/skills/chief-customer-officer/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260903.cc4a2cd, committed Sep 3, 2026
- First version recorded
- Aug 29, 2026
- Size
- 4,646 bytes
- Repository stars
- 2,543
- License
- MIT
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.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# 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. …
Read the whole file at its exact version.
How to install
mdr add cbrock84/headcount/chief-customer-officer@sha256:c0f05566a69c407eThe line at the top of this page pins the label git:20260903.cc4a2cd, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_t45seey6unzekwsy)
8 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Aug 29, 2026 and Sep 3, 2026, about one every day.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260903.cc4a2cd latest | 2026-09-03 | cc4a2cd | 4,646 B | A | view · diff |
| git:20260902.c7de476 | 2026-09-02 | c7de476 | 4,651 B | A | view · diff |
| git:20260831.eaba5fa | 2026-08-31 | eaba5fa | 4,651 B | A | view · diff |
| git:20260829.2464776 | 2026-08-29 | 2464776 | 2,975 B | A | view · diff |
| git:20260829.635d8e8 | 2026-08-29 | 635d8e8 | 2,975 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (4646 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
cbrock84/headcount · 2,543 stars · license MIT · pushed 2026-10-18 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_t45seey6unzekwsy GET https://markdownregistry.com/api/v1/resolve?ref=cbrock84/headcount/chief-customer-officer GET https://markdownregistry.com/api/v1/blob/c0f05566a69c407effd805315da8e69b75999be5c9ac16d6f254227682e0581e
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.