Youtube
AgriciDaniel/claude-youtube
The ultimate YouTube creator skill. An agent skill from AgriciDaniel/claude-youtube.
Runs content as an operation — the production pipeline, editorial calendar, repurposing engine, competitive content intelligence, and audits of what already exists.
$ npx skills add cbrock84/headcount --skill chief-content-officer -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install cbrock84/headcount chief-content-officer --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/marketing/skills/chief-content-officer .claude/skills/chief-content-officer && rm -rf skills-srcUse ~/.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/
Install the "chief-content-officer" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/marketing/skills/chief-content-officer into .claude/skills/chief-content-officer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "chief-content-officer", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/cbrock84/headcount/tree/main/plugins/marketing/skills/chief-content-officerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add cbrock84/headcount --skill chief-content-officer -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install cbrock84/headcount chief-content-officer --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/marketing/skills/chief-content-officer .agents/skills/chief-content-officer && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "chief-content-officer" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/marketing/skills/chief-content-officer into .agents/skills/chief-content-officer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "chief-content-officer", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add cbrock84/headcount --skill chief-content-officer -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install cbrock84/headcount chief-content-officer --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/marketing/skills/chief-content-officer .cursor/skills/chief-content-officer && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "chief-content-officer" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/marketing/skills/chief-content-officer into .cursor/skills/chief-content-officer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "chief-content-officer", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/cbrock84/headcount.git --path plugins/marketing/skills/chief-content-officer--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add cbrock84/headcount --skill chief-content-officer -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install cbrock84/headcount chief-content-officer --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/marketing/skills/chief-content-officer .gemini/skills/chief-content-officer && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "chief-content-officer" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/marketing/skills/chief-content-officer into .gemini/skills/chief-content-officer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "chief-content-officer", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install cbrock84/headcount chief-content-officerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add cbrock84/headcount --skill chief-content-officer -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/marketing/skills/chief-content-officer .github/skills/chief-content-officer && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "chief-content-officer" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/marketing/skills/chief-content-officer into .github/skills/chief-content-officer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "chief-content-officer", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add cbrock84/headcount --skill chief-content-officer -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install cbrock84/headcount chief-content-officer --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/marketing/skills/chief-content-officer .opencode/skills/chief-content-officer && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "chief-content-officer" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/marketing/skills/chief-content-officer into .opencode/skills/chief-content-officer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "chief-content-officer", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
chief-content-officerRuns content as an operation — the production pipeline, editorial calendar, repurposing engine, competitive content intelligence, and audits of what already exists.
Chief Content Officer is an agent 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.
Its SKILL.md is about 1.1k 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 Writing & Content, covering Content strategy and Content repurposing. 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.
Read from SKILL.md and the folder at commit 98d1c17. It shows what the files ask for, not the result of running them.
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.
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.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Chief Content Officer loads about 1.1k tokens when it runs. Until then it costs about 120 tokens; SKILL.md has 596 words of instructions outside code blocks.
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.
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.
The full file from cbrock84/headcount at commit 98d1c17, republished under its MIT licence (© cbrock84). 596 words, ~1,087 tokens.
.claude/skills/chief-content-officer/SKILL.md (or your agent's skills folder).content-strategy decides what to make and why. This runs the machine that makes it.
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.
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.
Build against capacity at your worst week, not your best. Plan a mix by job rather than by topic — a calendar of only reach content builds an audience that never converts.
Leave deliberate gaps. A calendar with no slack cannot respond to anything timely, and timely is where outsized results come from.
Plan derivatives at brief time, not after publishing. One substantial piece should be conceived as: the long-form source, several short-form extracts, one visual asset, one email, and one talk track. Segments intended to stand alone get written to stand alone.
Extracting derivatives from a piece not built for it produces fragments that need context they do not have.
Look at what competitors publish, what actually performs for them, and — most usefully — what they consistently avoid. Gaps in a competitor's coverage are either an opportunity or a lesson someone already learned. Work out which before committing.
Track their publishing cadence and format mix. A competitor who abandoned a format probably found it did not work.
Score on reach potential, strategic fit, evidence available, and effort. Force a stack rank rather than tiers. Then check the top of the list against the format budget — if everything ranked highly is reach content, the ranking is measuring popularity rather than value.
Once an idea is picked, expand it before drafting. An idea is a title; a piece needs an argument.
Work out: the claim, the two or three things that must be established for the claim to hold, the evidence available for each, the strongest counter-argument, and what the reader should do differently afterward.
If the counter-argument cannot be answered, that is the more interesting piece — write that one instead.
Only then choose the format. Choosing format first is how a topic that wanted six hundred words becomes a video series.
Inventory everything with its traffic, conversions, and last-updated date, then sort into four piles: update (performing, stale), consolidate (several thin pieces on one topic), promote (good, undistributed — usually the largest and most neglected pile), and retire (no traffic, no links, no strategic value).
Most libraries have more value in the promote pile than in anything unwritten.
© cbrock84, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in plugins/marketing/skills/chief-content-officer of cbrock84/headcount.
Open the folder on GitHubat commit 98d1c17
Chief Content 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Chief Content Officer this skillcbrock84/headcount | 2k | — | ~1.1k | Automated safety check: Pass | MIT | |
| YoutubeAgriciDaniel/claude-youtube | 440 | — | ~3.1k | Automated safety check: Pass | MIT | |
| Content RepurposingScrapeCreators/social-media-research-skills | 3.4k | — | ~564 | Automated safety check: Notes | MIT | |
| Podcast Pipelineericosiu/ai-marketing-skills | 3.6k | 1 repos | ~2.6k | Automated safety check: Pass | MIT | |
| Social Media Managementmanojbajaj95/claude-gtm-plugin | 105 | 1 repos | ~3.9k | Automated safety check: Pass | MIT | |
| Content Productionalirezarezvani/claude-skills | 28k | 1 repos | ~2.8k | Automated safety check: Pass | MIT |
AgriciDaniel/claude-youtube
The ultimate YouTube creator skill. An agent skill from AgriciDaniel/claude-youtube.
ScrapeCreators/social-media-research-skills
A skill your agent uses when the user wants to turn public social videos, transcripts, posts, or creator research into reusable content assets such as LinkedIn posts, X threads, short-form scripts…
ericosiu/ai-marketing-skills
Podcast-to-Everything content pipeline. An agent skill from ericosiu/ai-marketing-skills.
manojbajaj95/claude-gtm-plugin
Comprehensive social media management for all platforms (LinkedIn, Twitter/X, Instagram, TikTok, Facebook, Pinterest, YouTube).
alirezarezvani/claude-skills
Full content production pipeline — takes a topic from blank page to published-ready piece.
AgriciDaniel/claude-blog
Full-lifecycle blog engine with 31 sub-skills, 12 content templates, 5-category 100-point scoring, and 5 specialized agents.
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…
cbrock84/headcount
Designs and audits who can reach what — authentication, authorization models, privileged access, service credentials, and joiner-mover-leaver process.
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…
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.
cbrock84/headcount
Governs models and AI systems in production — intended use, evaluation, monitoring, human oversight, documentation, and the decision to deploy or retire.
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.
Categories
Runs content as an operation — the production pipeline, editorial calendar, repurposing engine, competitive content intelligence, and audits of what already exists. Chief Content Officer is an agent 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.
Chief Content Officer fits situations like: tasks that involve Content strategy; tasks that involve Content repurposing.
Run `npx skills add cbrock84/headcount --skill chief-content-officer -a claude-code`. Or copy the skill folder (plugins/marketing/skills/chief-content-officer in cbrock84/headcount) into .claude/skills/chief-content-officer in your project. Claude Code loads it when a task matches its description.
Run `npx skills add cbrock84/headcount --skill chief-content-officer -a codex`. Or copy the skill folder (plugins/marketing/skills/chief-content-officer in cbrock84/headcount) into .agents/skills/chief-content-officer in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add cbrock84/headcount --skill chief-content-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-content-officer, .gemini/skills/chief-content-officer, .github/skills/chief-content-officer and .opencode/skills/chief-content-officer in your project.
SKILL.md names no scripts, command-line tools or credentials: Chief Content Officer is instructions for the agent only.
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.
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.
Chief Content Officer is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.1k tokens (SKILL.md is roughly 4.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Chief Content Officer: Youtube (AgriciDaniel/claude-youtube, 440 stars), Content Repurposing (ScrapeCreators/social-media-research-skills, 3.4k stars), Podcast Pipeline (ericosiu/ai-marketing-skills, 3.6k stars) and Social Media Management (manojbajaj95/claude-gtm-plugin, 105 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
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.