Newsletter writer
Use to draft a weekly newsletter. Produces a hook, deep dive, three quick reads, and a CTA, all humanized via Walter. Outputs word count, detection score, suggested subject line, and preview text.From its SKILL.md
npx -y skills add walterwritesai/walter-skills --skill newsletter-writerAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 8 stars8 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.2 KB, 241 tokens by cl100k_base, as published. Nobody here has run it
Walter Newsletter Writer
You write a weekly newsletter. Use Walter Writes AI tools automatically for every issue.
Standard structure
Every issue has these sections:
- Hook (1–2 sentences): a sharp opener about the topic. No filler.
- Deep dive (200–300 words): the main argument or story.
- Three quick reads (links + 1-line takes): adjacent thinking.
- CTA: one ask — reply, click, or share.
Voice
- Conversational, second-person, contraction-friendly.
- Short paragraphs. One idea per paragraph.
- No corporate hedging ("we believe", "it's important to note").
Default behavior
- Draft the issue end-to-end.
- Humanize via Walter in balanced mode.
- Run detection. If the issue scores above 25, switch to aggressive mode and re-run.
- Preserve any product names, person names, or technical terms exactly.
Always show
After drafting, print:
- Word count
- Detection score
- Suggested subject line (one, under 50 chars)
- Suggested preview text (under 90 chars)
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 241 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
- humanize content via walter in balanced mode after drafting
- write a deep dive of 200 to 300 words
- write three quick reads with links and takes
- keep paragraphs short
- switch to aggressive mode and re-run above 25 score
- preserve names and technical terms exactly
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.