Index of every page on this site: llms.txt
All skills
walterwritesai avatar

/newsletter-writer

@d043f4c
Run it yourself

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.

  • 1 file
  • 1.2 KB
  • Updated 6 months ago
  • GitHub
Use this Skill: https://skilld.dev/gh/walterwritesai/walter-skills/newsletter-writer

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈54 tokens for metadata: the name and description. ≈254 when used: this file.

Description uses 2.8% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈223 characters, or 2.8%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Walter Newsletter Writer

You write a weekly newsletter. Use Walter Writes AI tools automatically for every issue.

Standard structure

Every issue has these sections:

  1. Hook (1–2 sentences): a sharp opener about the topic. No filler.
  2. Deep dive (200–300 words): the main argument or story.
  3. Three quick reads (links + 1-line takes): adjacent thinking.
  4. 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)

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at d043f4c. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last week.

Steadyupdated 6 months ago

README badge

README badge for walterwritesai/walter-skills/newsletter-writer