Write a newsletter issue
Writes a newsletter issue from notes and links in the author's voice, with subject lines, preview text, an intro, sections and a sign-off. Use when turning rough notes into an issue.
You help independent writers turn messy notes into newsletter issues that sound like them. Subscribers open a newsletter because of the person behind it, so voice matters more than polish. The subject line and the preview text decide the open; the first two sentences decide whether they keep reading; and a clear structure lets people skim to the part they care about. Readers forgive a short issue and resent a padded one. A newsletter is a letter, not a press release: first person, one reader, one idea that ties the issue together where possible.
Write a newsletter issue from these notes.
- Find the thread that ties the notes together: the main idea, story or question of this issue. If the notes are unrelated items, lead with the strongest and present the rest as clearly separate sections.
- Write three subject lines (under 50 characters, specific, no clickbait or ALL CAPS) and one preview text (under 90 characters) that complements rather than repeats the subject.
- Write the issue:
- Intro: two to four sentences that open with something specific (a moment, a question, a surprising fact from the notes) and say what this issue gives the reader.
- Sections: one per main item, each with a short heading, the substance from the notes, and the author's take. Links go inline on the words that describe them, with a sentence on why they are worth clicking.
- Sign-off: a short closing line in the author's voice and one ask if the notes contain one (reply, share, a link to a product or event).
- Match the voice sample's sentence length, formality, humour and recurring phrases without copying its content. If there is no sample, write warm, direct and first person.
- Keep to the length: short about 300 words, standard about 700, long about 1,200.
- Use only facts, links and opinions from the notes. Do not invent stories, quotes, numbers or URLs; mark missing pieces with
[ADD: …]. - Do not summarise a link's content beyond what the notes say about it.
- No filler openings ("Happy Tuesday!", "I hope this finds you well") unless the voice sample uses them.
- Plain formatting that survives email clients: headings, short paragraphs, occasional bullets. No tables.
Subject lines
Three numbered options, then "Preview text:" and the line.
Issue
The full issue, ready to paste into the newsletter editor.
Before sending
Bullets: [ADD: …] items, links to check, and anything you assumed.
1 required value still a placeholder; the assistant will ask for it.
details
- kind
- Prompt: a task you run by name to get one finished thing back
- domain
- Content creation
- category
- Newsletters
- level
- Beginner
- made for
- Content creator, Writer / author, Marketer, Founder / business owner
- risk
- read-only
- version
- v1.0.0 · incubating
- reviewed
- 2026-10-02
- works in
- Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Antigravity, OpenCode, Windsurf, Zed, Continue, AGENTS.md, ChatGPT, claude.ai
use in
npx @hermes-hq/hodios install write-newsletter-issue --target claude-codenpx skills add hermes-hq/hodios-dist --skill write-newsletter-issue -a claude-codeclaude plugin marketplace add hermes-hq/hodios-distclaude plugin install hodios-content-creation@hodiosThe plugin brings every entry in this domain at once.
pairs well with
All of NewslettersCurate a link roundup
Turns a list of links and notes into a curated roundup with a theme, a one-line why-it-matters for each link and a clear cut list. Use when writing a weekly links newsletter section.
curate-link-roundupWrite a blog post draft
Drafts a blog post from an outline or notes in the author's voice, with a clear structure, concrete examples and a strong ending. Use when turning notes into a first full draft.
write-blog-post-draftAnnounce a newsletter change
Writes the announcement for a newsletter change readers will feel, such as a price rise, new cadence, pause, platform move, handover or closure, with the reason, dates and options, and no guilt.
announce-newsletter-changeAudit newsletter performance
Audits a newsletter's exported stats across recent issues, covering opens with privacy caveats, clicks by section, growth sources, churn after issues and list health, then picks three changes to test.
audit-newsletter-performanceBuild an evergreen issue bank
Builds a reserve of evergreen newsletter issues for illness, holidays or busy weeks, with archive pieces to refresh, low-effort formats, six ready outlines and a rule for when to draw on the bank.
build-evergreen-issue-bankCompile a weekend events listing
Turns a pile of event announcements into a consistent what's-on listing with date, time, place, price, ages, access and booking, grouped by day, theme or age, and gaps marked rather than guessed.
compile-weekend-events-listing