agentsclimarketplace
Sign in

Newsletter writer

Skill ItamarZand88/awesome-agent-conventions/conventions/skill-md/examples/content-comms/newsletter-writer

A curated guide to convention files AI agents read, write, and act on: AGENTS.md, CLAUDE.md, SKILL.md, llms.txt, MCP configs, rules, and examples.From the repository description

Install
npx -y skills add ItamarZand88/awesome-agent-conventions --skill newsletter-writer

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

SKILL.md

2.8 KB, 716 tokens by cl100k_base, as published. Nobody here has run it

<!-- source: newsletter-writer — https://raw.githubusercontent.com/mohitagw15856/pm-claude-skills/main/skills/newsletter-writer/SKILL.md -->

name: newsletter-writer description: "Write a full creator newsletter issue — subject line, preview text, hook, body with a clear takeaway, and a CTA — in the writer's voice, for Substack, beehiiv, ConvertKit, or email. Use when asked to write a newsletter, an email issue, a Substack post, or to turn notes/a topic into a sendable newsletter. Produces a ready-to-send issue with subject-line options and a skimmable structure. Distinct from B2B drip/nurture sequences."

Newsletter Writer Skill

A newsletter is a relationship, not a broadcast. The best issues open a loop in the subject line, reward the open in the first sentence, deliver one clear idea, and make the next step obvious. This skill writes that issue — in your voice, ready to send.

Working from a brief

Given a topic, notes, or a piece to adapt, write the full issue anyway. Infer the audience and the single idea; mark invented specifics (assumed — replace). Don't hedge with "in this issue we'll explore…" — get to the value.

Required Inputs

Ask for (if not already provided):

  • Topic / notes / source for the issue
  • Audience and voice (or pull from a [[creator-brand-kit]])
  • Goal / CTA (reply, click, subscribe-upgrade, share) and rough length
  • Platform (Substack / beehiiv / ConvertKit / plain email) for formatting norms

Output Format

Subject lines

5 options, mixing curiosity, specificity, and benefit — each ≤ ~50 characters. Star the recommended one.

Preview text

One line (~80 chars) that complements (doesn't repeat) the subject.

The issue

  • Hook — first 1–2 sentences that reward the open and set up the idea.
  • Body — one core idea, in short scannable paragraphs/sub-headers, with a concrete example or story. No throat-clearing.
  • The takeaway — the one thing to remember, stated plainly (a callout line works well).
  • CTA — a single clear next step matching the goal.
  • PS — optional, often the most-read line; use it for a secondary nudge or personal note.

Skim test

A 3-bullet "what a 5-second skimmer takes away" — if those bullets don't carry the value, restructure.

Quality Checks

  • Subject lines are specific and varied; the preview complements, not repeats
  • The first sentence rewards the open (no "hope you're well, in today's issue…")
  • One core idea, skimmable, with a concrete example
  • A single clear CTA tied to the goal
  • Reads in the creator's voice, not generic newsletter-ese

Anti-Patterns

  • A subject line that's a label ("Newsletter #42")
  • Burying the value under a long personal preamble
  • Three competing CTAs, or none
  • A wall of text with no sub-heads or callout — unskimmable

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most marketing audience skills give in 716 tokens

Counted across 690 of the 894 authors here whose files we hold, read 2026-08-07

  • Apply Poppins font to headingsin 41 of 690, across 6 files
  • Apply Lora font to body textin 41 of 690, across 6 files
  • Use Arial fallback for headingsin 39 of 690, across 4 files
  • Use Georgia fallback for body textin 39 of 690, across 4 files
  • Maintain text hierarchy and formattingin 39 of 690, across 4 files
  • Use accent colors for non-text shapesin 38 of 690, across 3 files
  • Use RGB values for precise color matchingin 38 of 690, across 3 files
  • Use brand colors for primary text and backgroundsin 36 of 690, across 1 file
  • Read product marketing context file before asking questions, starting, or auditingin 35 of 690, across 23 files
  • Use active voice instead of passive voicein 26 of 690, across 10 files
  • Implement or generate appropriate JSON-LD structured datain 24 of 690, across 17 files
  • Prioritize clarity over clevernessin 22 of 690, across 8 files

Said here and by no other author read

  • star the recommended subject line
  • complement the subject line with unique preview text
  • open the issue with a rewarding hook
  • deliver one core idea with a concrete example
  • state the takeaway plainly
  • write a three-bullet skim test summary

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.