Agent skill

Newsletter Voice

by charlie947 in charlie947/social-media-skills

Build newsletter writing instructions inside a Codex or Claude project.

MITAuto-check passedWriting & Content

Install Newsletter Voice

skills CLI
$ npx skills add charlie947/social-media-skills --skill newsletter-voice -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install charlie947/social-media-skills newsletter-voice --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/charlie947/social-media-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/newsletter-voice .claude/skills/newsletter-voice && rm -rf skills-src

Use ~/.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/

Facts

Skill name
newsletter-voice
GitHub stars
3.8k
Token cost
~2.5k tokens
SKILL.md length
970 words
Files
2 (incl. references)
Skills in repo
15
Repo updated
First seen
Licence
MIT

At a glance

Build newsletter writing instructions inside a Codex or Claude project.

  • Works in 3 steps: Check for samples → Write newsletter-voice.md → Confirm and hand off
  • Ever the user says build my newsletter voice
  • SKILL.md covers Codex and Claude runtime, Prerequisites check, Step 1. Check for samples and Step 2a. Sample-based analysis, plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Newsletter Voice is an agent skill from charlie947/social-media-skills. Build newsletter writing instructions inside a Codex or Claude project. Runs after voice-builder. Produces newsletter-voice.md, a single file the assistant references when drafting newsletters in the user's voice. Works with or without existing newsletter samples: if the user has past issues, the skill analyses them; if not, the skill offers 6 archetypes tuned to the user's voice. Trigger whenever the user says "build my newsletter voice", "learn my newsletter style", "set up my newsletter system", "train on my…

Its SKILL.md is about 2.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/archetypes.md`).

It sits in Writing & Content, covering Newsletters. The licence is MIT.

When your agent uses it

  • Ever the user says build my newsletter voice
  • Learn my newsletter style
  • Set up my newsletter system
  • Train on my newsletters

Example prompts

  • “s voice. Trigger whenever the user says”
  • “learn my newsletter style”
  • “set up my newsletter system”
  • “/newsletter-voice”

Workflow steps

3 steps, taken from the step headings in SKILL.md.

  1. Check for samples
  2. Write newsletter-voice.md
  3. Confirm and hand off

What it can do on your machine

Read from SKILL.md and the folder at commit 8cefb5b. 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 (its code samples are json).

    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

Newsletter Voice loads about 2.5k tokens when it runs, and up to ~4.4k if it reads all its reference files. Until then it costs about 185 tokens; SKILL.md has 970 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~185
When it runs · the whole SKILL.md, loaded when a task matches
~2.5k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~4.4k

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 charlie947/social-media-skills at commit 8cefb5b, republished under its MIT licence (© charlie947). 970 words, ~2,464 tokens.

Download SKILL.mdSave it as .claude/skills/newsletter-voice/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
newsletter-voice
description
Build newsletter writing instructions inside a Codex or Claude project. Runs after voice-builder. Produces newsletter-voice.md, a single file the assistant references when drafting newsletters in the user's voice. Works with or without existing newsletter samples: if the user has past issues, the skill analyses them; if not, the skill offers 6 archetypes tuned to the user's voice. Trigger whenever the user says "build my newsletter voice", "learn my newsletter style", "set up my newsletter system", "train on my newsletters", "newsletter onboarding", or drops newsletter samples into chat asking for an analysis. Requires voice-builder to have run first: the skill needs voice.md and about-me.md in the project to work.

Newsletter Voice

Codex and Claude runtime

  • Use this skill in Codex or Claude with the tools actually available in the current task. AskUserQuestion examples describe the questions, not a required API: use an available question tool within its limits, or ask in chat. Reuse answers and source material already supplied.
  • Work in the user-selected project. Read its about-me.md, voice.md and relevant brand files before personalised work. Confirm the intended author if files conflict or contain starter defaults. Ask for missing facts or run voice-builder; never inherit the maintainer's identity, accounts or private files.
  • Resolve bundled references/ relative to this skill folder. For an explicitly requested profile refresh, read and update the canonical about-me.md, voice.md or newsletter-voice.md in place, preserving unrelated user facts and rules. Consumers must reread those canonical files. Use a new filename only for new deliverables that would collide with unrelated existing files. Installation alone never starts an interview or writes files. Do not write persistent learnings unless requested.
  • Use supplied evidence first. Verify external claims through available search/source tools when needed. If a source or integration is unavailable, name the missing capability and offer supplied text/export input. Never invent facts, first-person experience, metrics or a successful tool run.
  • Connect only services needed for the chosen route through the user's existing account. Never print credentials or overwrite connections. Drafting, saving and reviewing do not authorise publishing, sending messages or changing accounts.

Prerequisites check

The moment this skill is triggered, check the project root for voice.md and about-me.md.

If either file is missing, tell the user:

Newsletter voice sits on top of your general voice profile. Run voice-builder first (upload the skill or say "build my voice"), then come back here once about-me.md and voice.md are in the project.

Then stop. Do not continue until both files exist.

If both files exist, read them fully, then go straight to Step 1.

Step 1. Check for samples

Ask the user in chat:

Do you have 2 to 3 past newsletter issues I can learn from?

Yes: paste them here (one per message or all at once) No: type "archetype" and I will build from a template tuned to your voice

Wait for response.

If the user pastes 2 or more newsletters, go to Step 2a. If the user types "archetype", go to Step 2b. If the user pastes 1 newsletter, ask for at least one more. If they only have one, offer: "One sample is not enough for pattern detection. Want me to switch to archetype mode and use your one newsletter as a reference point?"

Step 2a. Sample-based analysis

Read every newsletter fully. Look for patterns across issues, not one-off quirks. Extract:

Opening formula

  • What the first 3 sentences do (specific result, cultural observation, claim, scene, question)
  • Length of the opening section before the first structural break
  • Credibility move (how the author establishes authority early)
  • Value promise (what the reader is told they will get)

Section structure

  • Problem or contrast setup
  • Named framework or free prose
  • Numbered steps, methods, or continuous argument
  • Examples and evidence patterns
  • Bonus or extension section
  • Closing formula and signoff

Data philosophy

  • Specific numbers per issue (count them)
  • Source attribution style (linked, named, uncredited)
  • Example-to-abstraction ratio
  • Limitation or failure acknowledgements

Formatting

  • Header usage (frequency, hierarchy)
  • List usage (numbered, bulleted, arrows)
  • Bold and italic usage
  • Prompt, code block, or blockquote formatting
  • Visual markers (arrows, checkmarks, emojis if any)

Length

  • Word count range across samples
  • Section word counts

Voice markers unique to newsletter format

  • Pro tips or callouts (frequency, format)
  • Forward-looking closings
  • Signoff phrase if consistent across samples
  • Meta-transparency (does the author reflect on the process or ask for feedback)

Absence signals

  • Words, constructions, or structures absent from every sample
  • Closing moves the author never uses
  • Topics the author never touches

Then go to Step 3.

Show full SKILL.md (341 more words)Show less

Step 2b. Archetype selection

Call the AskUserQuestion tool with a single question:

json
[
  {
    "question": "Which newsletter archetype fits what you want to write?",
    "header": "Archetype",
    "multiSelect": false,
    "options": [
      {"label": "Data tutorial", "description": "Numbers, frameworks, step-by-step methods with prompts"},
      {"label": "Contrarian essay", "description": "Take a position, defend it, name the opposition"},
      {"label": "Case study teardown", "description": "One subject per issue, unpacked in depth"},
      {"label": "Curated digest", "description": "5 to 7 links with your commentary each week"},
      {"label": "Personal essay", "description": "Reflection on a theme, story-first"},
      {"label": "Interview or profile", "description": "One person per issue, Q and A or narrative"}
    ]
  }
]

After the user picks an archetype, load the matching defaults from references/archetypes.md inside this skill folder. Tune every field using voice.md and about-me.md before writing newsletter-voice.md. Flag inside the output file that archetype defaults were used and the file should be revisited after 5 published issues.

Step 3. Write newsletter-voice.md

Create newsletter-voice.md in the project root. Single file, 800 to 1,200 words target. Use this structure:

# Newsletter Voice

## Source
[Sample-based: analysed X newsletter issues] OR [Archetype-based: [archetype name] tuned to voice.md. Revisit after 5 published issues.]

## Audience and purpose
[Who reads this newsletter and what they get from it. Written from about-me.md and voice.md. 2 to 3 sentences.]

## Voice principles
[3 to 5 core principles the writing always holds. Each one a short declarative sentence. Tuned to this user's voice.md.]

## Opening formula
[How issues start. Include 2 concrete templates with bracketed placeholders, e.g. "[Specific result with number]. [Credibility marker]. [Value promise for this issue]." Target word count for the opening section.]

## Section flow
[Standard structure of an issue, section by section, 5 to 8 sections max. Brief notes on what each section does and how long it runs.]

## Data and evidence
[How numbers and examples are used. Specific rules, e.g. "every claim needs a number", "sources linked inline", "example-to-abstraction ratio roughly 3:1".]

## Formatting rules
[Headers, lists, bold, italic, code blocks, visual markers. What to use, what to avoid. Drawn from samples or archetype defaults.]

## Closing and signoff
[How issues end. Forward-looking statement versus summary. Signoff phrase if a consistent one exists across samples (do not invent one).]

## What this newsletter never does
[1 short paragraph or 3 to 5 items. Drawn from absence patterns across samples or archetype defaults. Behaviours only, not a banned-words list.]

## Length
[Word count target for standard issues. Separate target for longer comprehensive guides if the user writes both formats.]

Fill every section from the samples (or tuned archetype defaults). No generic filler. If the samples do not cover something, say "no clear pattern across samples" rather than guessing.

Step 4. Confirm and hand off

Tell the user:

Your newsletter voice is built. newsletter-voice.md is in your project root alongside about-me.md and voice.md. When you want to draft an issue, say "write a newsletter" and I will use all three files together.

[If archetype mode: Remember this file was built from archetype defaults. After 5 or so published issues, re-run this skill with your real samples for a sharper profile.]

What this skill produces

One file in the project root:

  • newsletter-voice.md: newsletter-specific writing instructions covering audience, voice principles, opening formula, section flow, data philosophy, formatting, closing, absence patterns, and length targets

Rules

  • Require voice.md and about-me.md in the project root before running. Stop and redirect to voice-builder if either is missing.
  • Minimum 2 newsletter samples if the user chooses sample-based mode. Offer archetype mode if fewer.
  • Keep newsletter-voice.md under 1,200 words. Tight beats exhaustive.
  • Do not invent voice signals. Work only from samples or archetype defaults tuned to voice.md.
  • Do not duplicate content from voice.md. Reference it where relevant. newsletter-voice.md adds newsletter-specific rules only.
  • Do not bake in the user's specific names, URLs, or signoff phrases unless they appear consistently across 2 or more samples.
  • Do not produce a separate voice or banned-words file. Absence patterns live inside newsletter-voice.md as a single section.
  • British English throughout unless samples are clearly American.
  • Never use em dashes in any output file or in any draft.

© charlie947, 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 skills/newsletter-voice of charlie947/social-media-skills.

  • SKILL.md
  • references/archetypes.md

Open the folder on GitHubat commit 8cefb5b

Compare with similar skills

Newsletter Voice 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.

Newsletter Voice compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Newsletter Voice this skillcharlie947/social-media-skills3.8k—~2.5kAutomated safety check: PassMIT
Internal Communications Writeranthropics/skills180k38 repos~378Automated safety check: PassApache-2.0
Clarityaddyosmani/clarity2691 repos~1.9kAutomated safety check: PassMIT
News Aggregator Skillcclank/news-aggregator-skill1.3k—~2.1kAutomated safety check: PassNone
Changelog Social RecapFlorianBruniaux/claude-code-ultimate-guide6.1k—~1.8kAutomated safety check: NotesCC-BY-SA-4.0
News ExtractorNanmiCoder/NewsCrawler624—~1.3kAutomated safety check: PassGPL-3.0

Similar skills

  • Official

    A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill…

    180k GitHub starsUsed in 38 repos~378 tokens
    Writing & ContentAuto-check passed
  • Clarity

    addyosmani/clarity

    Draft, rewrite, or review reader-facing prose so it is specific, useful, and recognizably the author's without inventing facts or performing humanness.

    269 GitHub starsUsed in 1 repo~1.9k tokens
    Writing & ContentAuto-check passed
  • News Aggregator Skill

    cclank/news-aggregator-skill

    Comprehensive news aggregator that fetches, filters, and deeply analyzes real-time content from 44+ sources including Hacker News, Lobsters, Dev.to, GitHub, arXiv, Hugging Face Papers, AIHOT, TLDR…

    1.3k GitHub stars~2.1k tokensUpdated 4 mo ago
    Writing & ContentAuto-check passed
  • 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.

    6.1k GitHub stars~1.8k tokensUpdated today
    Writing & ContentAuto-check: notes
  • News Extractor

    NanmiCoder/NewsCrawler

    新闻站点内容提取。支持 12 个平台:微信公众号、今日头条、网易新闻、搜狐新闻、腾讯新闻、BBC News、CNN News、Twitter/X、Lenny's Newsletter、Naver Blog、Detik News、Quora。当用户需要提取新闻内容、抓取公众号文章、爬取新闻、或获取新闻JSON/Markdown时激活。

    624 GitHub stars~1.3k tokensUpdated 2 mo ago
    Writing & ContentAuto-check passed
  • Bestblogs Discover

    ginobefun/BestBlogs

    A skill your agent uses when the user wants to find today's most worth-reading content from BestBlogs, browse personalized feeds, check trending items, search specific topics, or explore curated…

    4.1k GitHub stars~800 tokensUpdated 3 mo ago
    Writing & ContentAuto-check passed

More from charlie947/social-media-skills

All 15 skills in this repo
  • Voice Builder

    charlie947/social-media-skills

    Build a personalised voice profile inside a Codex or Claude project from a short interview plus 3 to 5 sample pieces of writing.

    3.8k GitHub stars~3.3k tokensUpdated 26 days ago
    Auto-check passed
  • Content Matrix

    charlie947/social-media-skills

    Generate 24 to 40 LinkedIn post ideas in a single table by pairing the user's content pillars with 8 proven content formats.

    3.8k GitHub stars~1.6k tokensUpdated 26 days ago
    Auto-check passed
  • Gemini Carousel

    charlie947/social-media-skills

    Generate a branded slide-by-slide LinkedIn carousel using Gemini.

    3.8k GitHub stars~1.7k tokensUpdated 26 days ago
    Auto-check passed
  • Hook Generator

    charlie947/social-media-skills

    Generate 6 clickbait-style LinkedIn hook variations for any topic.

    3.8k GitHub stars~1.1k tokensUpdated 26 days ago
    Auto-check passed
  • Niche Research

    charlie947/social-media-skills

    Surface the 20 most relevant stories in a niche from the last 7 days using available live research tools.

    3.8k GitHub stars~1.7k tokensUpdated 26 days ago
    Auto-check passed
  • Pinned Comment

    charlie947/social-media-skills

    Write deadpan LinkedIn pinned comments AND matching image generation prompts in the user’s voice.

    3.8k GitHub stars~2.3k tokensUpdated 26 days ago
    Auto-check passed

Questions about Newsletter Voice

What does Newsletter Voice do?

Build newsletter writing instructions inside a Codex or Claude project. Newsletter Voice is an agent skill from charlie947/social-media-skills. Build newsletter writing instructions inside a Codex or Claude project.

When should I use Newsletter Voice?

Newsletter Voice fits situations like: ever the user says build my newsletter voice; learn my newsletter style; set up my newsletter system; train on my newsletters.

How do I install Newsletter Voice in Claude Code?

Run `npx skills add charlie947/social-media-skills --skill newsletter-voice -a claude-code`. Or copy the skill folder (skills/newsletter-voice in charlie947/social-media-skills) into .claude/skills/newsletter-voice in your project. Claude Code loads it when a task matches its description.

How do I install Newsletter Voice in Codex?

Run `npx skills add charlie947/social-media-skills --skill newsletter-voice -a codex`. Or copy the skill folder (skills/newsletter-voice in charlie947/social-media-skills) into .agents/skills/newsletter-voice in your project. Codex loads it when a task matches its description.

Can I use Newsletter Voice 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 charlie947/social-media-skills --skill newsletter-voice -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-voice, .gemini/skills/newsletter-voice, .github/skills/newsletter-voice and .opencode/skills/newsletter-voice in your project.

What does Newsletter Voice need to run?

SKILL.md names no scripts, command-line tools or credentials: Newsletter Voice is instructions for the agent only.

Does Newsletter Voice 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 Newsletter Voice 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 Newsletter Voice use?

Newsletter Voice 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 Newsletter Voice use?

About 2.5k tokens (SKILL.md is roughly 9.9k 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 1.9k tokens, read only when the agent opens those files.

What are the alternatives to Newsletter Voice?

Skills that share tags, products or a category with Newsletter Voice: Internal Communications Writer (anthropics/skills, 180k stars), Clarity (addyosmani/clarity, 269 stars), News Aggregator Skill (cclank/news-aggregator-skill, 1.3k stars) and Changelog Social Recap (FlorianBruniaux/claude-code-ultimate-guide, 6.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Newsletter Voice?

charlie947 (a GitHub user) maintains it in charlie947/social-media-skills, which has 3,844 GitHub stars. The repository holds 15 skills in this directory. The repository was last updated on September 15, 2026.

Source: charlie947/social-media-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.