chief-content-officer skillA
chief-content-officer is agent-read markdown (skill) from cbrock84/headcount: Runs content as an operation — the production pipeline, editorial calendar, repurposing engine, competitive content intelligence, and audits of what already exists. Use this to build or fix a content production system, plan a calendar, decide how one piece becomes many, rank content ideas by expected impact, or audit an existing library for what to update, consolidate, or retire. For deciding what territory to own and why, use `content-strategy` first..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Chief content officer `content-strategy` decides what to make and why. This runs the machine that makes it. ## The pipeline Content programs fail on throughput, not ideas. Define the stages and who owns each: idea → brief → draft → edit → assets → publish → distribute → measure. The two stages that jam are **brief** and **distribution**. A piece that reaches a writer without a brief gets rewritten twice. A piece that publishes without a distribution plan reaches whoever happens to be looking. Work in progress is the enemy. Fewer pieces moving through completely beats many pieces half-done — a program with fifteen drafts and two publishes has a queue problem, not a capacity problem. ## Briefs Every piece gets one before drafting, stating: the job (reach, trust, conversion, or retention), the audience, the single argument, the evidence available, the format and length, and what success looks like. Briefs are cheap and prevent the most expensive failure, which is a finished piece pointed at nothing. ## Calendar Build against capacity at your worst week, not your best. Plan a mix by job rather than by topic — …
Read the whole file at its exact version.
How to install
mdr add cbrock84/headcount/chief-content-officer@git:20260901.b973f20mdr add cbrock84/headcount/chief-content-officer@sha256:e8beed41a1b85d0bPin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_pxg57rtf475twj72)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260901.b973f20 latest | 2026-09-01 | b973f20 | 4,378 B | A | view · diff |
| git:20260828.f80dcb5 | 2026-08-28 | f80dcb5 | 3,972 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 (4378 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 · 1,664 stars · license MIT · pushed 2026-09-17 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_pxg57rtf475twj72 GET https://markdownregistry.com/api/v1/resolve?ref=cbrock84/headcount/chief-content-officer GET https://markdownregistry.com/api/v1/blob/e8beed41a1b85d0b91405317355c00abfa8ce22a781c295a1b3df65b5bc602b8
Your agent 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.