Blogger Distiller
otter1101/blogger-distiller
A skill your agent uses when the user wants to analyze or distill a blogger/account on Xiaohongshu or Douyin, benchmark a target creator, or diagnose their own content strategy.
Decides what content to make and why — topic territory, format mix, cadence, and how content connects to a business outcome rather than to traffic.
Install Content Strategy
$ npx skills add cbrock84/headcount --skill content-strategy -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install cbrock84/headcount content-strategy --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/content-strategy .claude/skills/content-strategy && 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 "content-strategy" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/marketing/skills/content-strategy into .claude/skills/content-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-strategy", 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/content-strategyType 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 content-strategy -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install cbrock84/headcount content-strategy --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/content-strategy .agents/skills/content-strategy && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "content-strategy" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/marketing/skills/content-strategy into .agents/skills/content-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-strategy", 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 content-strategy -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install cbrock84/headcount content-strategy --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/content-strategy .cursor/skills/content-strategy && 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 "content-strategy" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/marketing/skills/content-strategy into .cursor/skills/content-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-strategy", 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/content-strategy--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 content-strategy -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install cbrock84/headcount content-strategy --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/content-strategy .gemini/skills/content-strategy && 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 "content-strategy" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/marketing/skills/content-strategy into .gemini/skills/content-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-strategy", 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 content-strategyInstalls 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 content-strategy -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/content-strategy .github/skills/content-strategy && 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 "content-strategy" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/marketing/skills/content-strategy into .github/skills/content-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-strategy", 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 content-strategy -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 content-strategy --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/content-strategy .opencode/skills/content-strategy && 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 "content-strategy" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/marketing/skills/content-strategy into .opencode/skills/content-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-strategy", 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.
Facts
- Skill name
content-strategy- GitHub stars
- 2k
- Token cost
- ~752 tokens
- SKILL.md length
- 401 words
- Files
- 2 (incl. references)
- Skills in repo
- 178
- Repo updated
- First seen
- Licence
- MIT
At a glance
Decides what content to make and why — topic territory, format mix, cadence, and how content connects to a business outcome rather than to traffic.
- Tasks that involve Content strategy
- SKILL.md covers Claim a territory, not a topic…, Match format to job, Cadence beats volume and Platform commitment, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Content Strategy is an agent skill from cbrock84/headcount. Decides what content to make and why — topic territory, format mix, cadence, and how content connects to a business outcome rather than to traffic. Use this to plan a content program, choose topics, build an editorial calendar, decide which formats and platforms to commit to, or diagnose why content is producing audience but not results.
Its SKILL.md is about 750 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/sources.md`).
It sits in Writing & Content, covering Content 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
- Tasks that involve Content strategy
Example prompts
- “Use the content-strategy skill to decide what content to make and why — topic territory, format mix, cadence, and how content connects to a business…”
- “/content-strategy”
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
Content Strategy loads about 752 tokens when it runs, and up to ~1.1k if it reads all its reference files. Until then it costs about 89 tokens; SKILL.md has 401 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.
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). 401 words, ~752 tokens.
Download SKILL.mdSave it as
.claude/skills/content-strategy/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- content-strategy
- description
- Decides what content to make and why — topic territory, format mix, cadence, and how content connects to a business outcome rather than to traffic. Use this to plan a content program, choose topics, build an editorial calendar, decide which formats and platforms to commit to, or diagnose why content is producing audience but not results.
Content strategy
Claim a territory, not a topic list
A content program works when a defined audience learns to expect a specific kind of value from you. That requires a territory narrow enough to own: the intersection of what you know unusually well, what your buyer needs help with, and what nobody else is covering properly.
Test it: could a competitor publish your last ten pieces without anyone noticing? If yes, you have a topic list.
Match format to job
Every piece should have one job, and the job dictates the format:
- Reach — a claim someone would repeat. Short, opinionated, self-contained.
- Trust — depth that demonstrates competence. Long, specific, evidenced.
- Conversion — content adjacent to the buying decision: comparisons, implementation guides, objection answers.
- Retention — content that makes existing customers better at the thing.
Programs skew heavily to reach and then wonder why the audience does not convert. Budget across all four deliberately.
Cadence beats volume
Pick a frequency sustainable at your worst week, not your best. Irregular publishing costs more than infrequent publishing, because the audience stops expecting you.
Platform commitment
Two platforms done properly beat five done adequately. Choose by where the audience already is and which format you can actually sustain — not by reach numbers.
Every piece should be planned with its derivatives: the long piece is the source, and the short-form versions are extracted, not written separately.
Show full SKILL.md (173 more words)Show less
Measurement
Measure by job. Reach content is judged on reach; conversion content on conversion. Judging everything on traffic is why content programs drift toward the reach end and stay there.
Set a review point where a topic that is not working gets dropped. Content strategies fail by accumulation.
Sources
references/sources.md in this skill lists the outside authorities that settle the questions
here — what each one is authoritative for, and what you may do with it. Check them before
answering on anything they cover, and cite what you used. Most are free to read and not free
to reproduce; the use note on each is binding.
Never
- Claim a territory you cannot sustain publishing on. Withdrawing from one costs more than never entering it.
- Commit to a platform without deciding who runs it every week.
- Judge a content program on traffic when the objective was demand.
Return contract
Territory, audience, the four-way format budget, cadence, platforms with rationale, first ten pieces with the job of each, and what you are choosing not to cover.
© 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
SKILL.md and 1 other file (references) in plugins/marketing/skills/content-strategy of cbrock84/headcount.
- SKILL.md
- references/sources.md
Open the folder on GitHubat commit 98d1c17
Compare with similar skills
Content Strategy 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 |
|---|---|---|---|---|---|---|
| Content Strategy this skillcbrock84/headcount | 2k | — | ~752 | Automated safety check: Pass | MIT | |
| Blogger Distillerotter1101/blogger-distiller | 697 | — | ~3.8k | Automated safety check: Notes | MIT | |
| Linkedin Content Plannersergebulaev/linkedin-skills | 4.4k | 1 repos | ~2.1k | Automated safety check: Pass | MIT | |
| Blog Post Draftingluongnv89/claude-howto | 42k | — | ~2.1k | Automated safety check: Pass | MIT | |
| WeChat Hot Article AnalysisSpaceZephyr/creator-buddy | 1.6k | — | ~847 | Automated safety check: Pass | None | |
| Brand Voice Content Creatordavila7/claude-code-templates | 32k | 3 repos | ~1.9k | Automated safety check: Pass | MIT |
Similar skills
Linkedin Content Planner
sergebulaev/linkedin-skills
Generate a 7-day LinkedIn content plan from a theme, audience, and pillars.
Blog Post Drafting
luongnv89/claude-howto
Guides drafting a blog post from an idea and optional source material: research, brainstorming, outlining and version-tracked drafts, with user approval at each step.
WeChat Hot Article Analysis
SpaceZephyr/creator-buddy
Fetches hot WeChat Official Account articles by sector or keywords and produces a data file and an HTML report with rankings, style patterns and writing references.
Brand Voice Content Creator
davila7/claude-code-templates
Analyzes a brand's existing writing to lock in a consistent voice, then builds SEO blog posts and platform-specific social content around it.
Ralph Copywriter
muratcankoylan/ralph-wiggum-marketer
A skill your agent uses when the user asks to "analyze my content", "learn my writing style", "research competitors", "find content angles", "improve my blog", "write like me", "embody my brand…
More from cbrock84/headcount
All 178 skills in this repoAgent 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…
Access And Identity
cbrock84/headcount
Designs and audits who can reach what — authentication, authorization models, privileged access, service credentials, and joiner-mover-leaver process.
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…
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.
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.
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.
Related
Categories
Questions about Content Strategy
What does Content Strategy do?
Decides what content to make and why — topic territory, format mix, cadence, and how content connects to a business outcome rather than to traffic. Content Strategy is an agent skill from cbrock84/headcount. Decides what content to make and why — topic territory, format mix, cadence, and how content connects to a business outcome rather than to traffic.
When should I use Content Strategy?
Content Strategy fits situations like: tasks that involve Content strategy.
How do I install Content Strategy in Claude Code?
Run `npx skills add cbrock84/headcount --skill content-strategy -a claude-code`. Or copy the skill folder (plugins/marketing/skills/content-strategy in cbrock84/headcount) into .claude/skills/content-strategy in your project. Claude Code loads it when a task matches its description.
How do I install Content Strategy in Codex?
Run `npx skills add cbrock84/headcount --skill content-strategy -a codex`. Or copy the skill folder (plugins/marketing/skills/content-strategy in cbrock84/headcount) into .agents/skills/content-strategy in your project. Codex loads it when a task matches its description.
Can I use Content Strategy 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 content-strategy -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/content-strategy, .gemini/skills/content-strategy, .github/skills/content-strategy and .opencode/skills/content-strategy in your project.
What does Content Strategy need to run?
SKILL.md names no scripts, command-line tools or credentials: Content Strategy is instructions for the agent only.
Does Content Strategy 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 Content Strategy 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 Content Strategy use?
Content Strategy 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 Content Strategy use?
About 752 tokens (SKILL.md is roughly 3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 310 tokens, read only when the agent opens those files.
What are the alternatives to Content Strategy?
Skills that share tags, products or a category with Content Strategy: Blogger Distiller (otter1101/blogger-distiller, 697 stars), Linkedin Content Planner (sergebulaev/linkedin-skills, 4.4k stars), Blog Post Drafting (luongnv89/claude-howto, 42k stars) and WeChat Hot Article Analysis (SpaceZephyr/creator-buddy, 1.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Content Strategy?
cbrock84 (a GitHub user) maintains it in cbrock84/headcount, which has 2,016 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.