Changelog Social Recap
FlorianBruniaux/claude-code-ultimate-guide
Turns CHANGELOG.md entries for a release or a week into LinkedIn, Twitter/X, newsletter and Slack posts in French and English.
Writes and edits newsletters and marketing emails people actually open — subject lines, opening, structure, voice, and the conversion turn where there is one.
$ npx skills add cbrock84/headcount --skill newsletter-writer -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install cbrock84/headcount newsletter-writer --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/newsletter-writer .claude/skills/newsletter-writer && 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 "newsletter-writer" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/marketing/skills/newsletter-writer into .claude/skills/newsletter-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "newsletter-writer", 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/newsletter-writerType 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 newsletter-writer -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install cbrock84/headcount newsletter-writer --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/newsletter-writer .agents/skills/newsletter-writer && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "newsletter-writer" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/marketing/skills/newsletter-writer into .agents/skills/newsletter-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "newsletter-writer", 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 newsletter-writer -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install cbrock84/headcount newsletter-writer --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/newsletter-writer .cursor/skills/newsletter-writer && 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 "newsletter-writer" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/marketing/skills/newsletter-writer into .cursor/skills/newsletter-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "newsletter-writer", 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/newsletter-writer--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 newsletter-writer -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install cbrock84/headcount newsletter-writer --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/newsletter-writer .gemini/skills/newsletter-writer && 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 "newsletter-writer" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/marketing/skills/newsletter-writer into .gemini/skills/newsletter-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "newsletter-writer", 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 newsletter-writerInstalls 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 newsletter-writer -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/newsletter-writer .github/skills/newsletter-writer && 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 "newsletter-writer" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/marketing/skills/newsletter-writer into .github/skills/newsletter-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "newsletter-writer", 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 newsletter-writer -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 newsletter-writer --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/newsletter-writer .opencode/skills/newsletter-writer && 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 "newsletter-writer" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/marketing/skills/newsletter-writer into .opencode/skills/newsletter-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "newsletter-writer", 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.
newsletter-writerWrites and edits newsletters and marketing emails people actually open — subject lines, opening, structure, voice, and the conversion turn where there is one.
Newsletter Writer is an agent skill from cbrock84/headcount. Writes and edits newsletters and marketing emails people actually open — subject lines, opening, structure, voice, and the conversion turn where there is one. Use this to draft or rewrite a newsletter or email, sharpen weak email copy, plan a newsletter's structure and cadence, write a sequence, or repurpose an issue into other formats. For automated lifecycle and SMS programs, use lifecycle-messaging.
Its SKILL.md is about 1.1k 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 Newsletters 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.
Newsletter Writer loads about 1.1k tokens when it runs, and up to ~1.6k if it reads all its reference files. Until then it costs about 106 tokens; SKILL.md has 654 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). 654 words, ~1,109 tokens.
.claude/skills/newsletter-writer/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.A newsletter is a standing invitation that can be withdrawn at any time. Every issue either renews it or spends it.
One issue, one job: teach something, argue something, or sell something. Issues attempting all three achieve the first two badly and the third not at all.
They are read together and should not repeat each other — the preview extends the subject rather than echoing it. Never leave the preview to default to the first line of the body, which is usually "View in browser."
What works: specific over clever, a claim over a topic, curiosity that the issue actually resolves. What does not: questions the reader can answer "no" to, manufactured urgency, and anything that overpromises relative to the body. Overpromising buys one open and costs the next five.
The first sentence decides whether the rest is read. Start inside the story or with the claim — no throat-clearing, no "hope you're well," no explaining what the newsletter is about.
Cut your first paragraph after drafting. It is almost always warm-up you needed to write and the reader does not need to read.
Short paragraphs. One idea each. Enough white space that the issue looks readable before it is read — people decide whether to read from the shape of the thing.
Signpost where the issue turns, so someone skimming still gets the argument. Most readers skim.
The thing that makes a newsletter worth opening is that it sounds like a person. Specifically:
Avoid the register tells: "In today's fast-paced world," "it's no secret that," "let's dive in," tricolon everywhere, and every paragraph the same length.
Earn the ask. When an issue sells, the value comes first and the pitch is clearly marked — readers forgive a clear pitch and resent a disguised one.
One call to action per issue. Multiple asks split attention and reduce all of them.
Replies are the strongest signal a newsletter is working, and they improve deliverability more than any technical fix.
Ask one specific question, occasionally rather than every issue, and make it easy to answer in a sentence. "What did I get wrong here?" outperforms "let me know your thoughts," which asks the reader to do the work of deciding what to say.
Then reply to the replies. A newsletter where the author answers is a different product from one where they do not, and readers tell each other about the first kind.
Three passes, in order: structure (is the order right, is anything missing), cut (remove what does not advance the argument), read aloud (anything you stumble over gets rewritten). The read-aloud pass catches what silent reading never does.
One issue contains several short-form posts, a talk track, and often a longer piece. Plan which before writing, so the sections that should stand alone are written to.
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.
© cbrock84, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 1 other file (references) in plugins/marketing/skills/newsletter-writer of cbrock84/headcount.
Open the folder on GitHubat commit 98d1c17
Newsletter Writer 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 |
|---|---|---|---|---|---|---|
| Newsletter Writer this skillcbrock84/headcount | 2k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Changelog Social RecapFlorianBruniaux/claude-code-ultimate-guide | 6.1k | — | ~1.8k | Automated safety check: Notes | CC-BY-SA-4.0 | |
| Content RepurposingScrapeCreators/social-media-research-skills | 3.4k | — | ~564 | Automated safety check: Notes | MIT | |
| Content Repurposer Smsblacktwist/social-media-skills | 560 | — | ~3.7k | Automated safety check: Pass | MIT | |
| Idea Extractoraiskilloftheweek/claude-ai-skill-of-the-week | 149 | — | ~1.5k | Automated safety check: Pass | None | |
| Podcast Pipelineericosiu/ai-marketing-skills | 3.6k | 1 repos | ~2.6k | Automated safety check: Pass | MIT |
FlorianBruniaux/claude-code-ultimate-guide
Turns CHANGELOG.md entries for a release or a week into LinkedIn, Twitter/X, newsletter and Slack posts in French and English.
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…
blacktwist/social-media-skills
When the user wants to turn one piece of content into multiple formats or adapt content across text-first and visual-first platforms (LinkedIn, Twitter/X, Threads, Bluesky, Facebook, Instagram…
aiskilloftheweek/claude-ai-skill-of-the-week
Analyzes long-form content (transcripts, articles, interviews, webinars, podcast notes) and extracts the 3 best content ideas for any publishing platform — LinkedIn, Substack, blog, newsletter…
ericosiu/ai-marketing-skills
Podcast-to-Everything content pipeline. An agent skill from ericosiu/ai-marketing-skills.
Jakeschincariol/linkedin-agent-skill
Turn one long asset - a YouTube video, podcast, newsletter, blog post, transcript or client call - into a week of LinkedIn posts.
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
Writes and edits newsletters and marketing emails people actually open — subject lines, opening, structure, voice, and the conversion turn where there is one. Newsletter Writer is an agent skill from cbrock84/headcount. Writes and edits newsletters and marketing emails people actually open — subject lines, opening, structure, voice, and the conversion turn where there is one.
Newsletter Writer fits situations like: tasks that involve Newsletters; tasks that involve Content repurposing.
Run `npx skills add cbrock84/headcount --skill newsletter-writer -a claude-code`. Or copy the skill folder (plugins/marketing/skills/newsletter-writer in cbrock84/headcount) into .claude/skills/newsletter-writer in your project. Claude Code loads it when a task matches its description.
Run `npx skills add cbrock84/headcount --skill newsletter-writer -a codex`. Or copy the skill folder (plugins/marketing/skills/newsletter-writer in cbrock84/headcount) into .agents/skills/newsletter-writer 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 newsletter-writer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/newsletter-writer, .gemini/skills/newsletter-writer, .github/skills/newsletter-writer and .opencode/skills/newsletter-writer in your project.
SKILL.md names no scripts, command-line tools or credentials: Newsletter Writer 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.
Newsletter Writer 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.4k 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 476 tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Newsletter Writer: Changelog Social Recap (FlorianBruniaux/claude-code-ultimate-guide, 6.1k stars), Content Repurposing (ScrapeCreators/social-media-research-skills, 3.4k stars), Content Repurposer Sms (blacktwist/social-media-skills, 560 stars) and Idea Extractor (aiskilloftheweek/claude-ai-skill-of-the-week, 149 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.