agentsclimarketplace
Sign in

Newsletter forge

Skill moses607/skillforge/skills/newsletter-forge

Draft an email newsletter issue built around one idea with a strong open and a single call to action. Use whenever the user asks to write a newsletter, an email issue, "this week's edition", a broadcast to subscribers, or wants to turn notes/links into a sendable email. Trigger even when they only give a rough topic or a pile of links to shape into an issue.From its SKILL.md

Install
npx -y skills add moses607/skillforge --skill newsletter-forge

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

One thing to look at

  • 0 stars0 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

2.2 KB, 475 tokens by cl100k_base, as published. Nobody here has run it

Newsletter Forge

A newsletter earns the next open by being worth this one. Structure each issue around a single idea, open with a reason to keep reading, and ask for exactly one action. Sprawl kills open rates.

Issue architecture

  1. Subject line — curiosity or value, ≤50 chars, no clickbait you can't cash. Give 3 options.
  2. Preview text — the ~90 chars after the subject in the inbox. Extend the subject, don't repeat it.
  3. Open — first 1-2 sentences carry the whole email. A specific hook: a story beat, a sharp claim, a question the reader also has. No "Hope you're doing well!".
  4. One big idea — the issue is about one thing. Develop it: setup → insight → why it matters to the reader.
  5. Scannable body — short paragraphs, subheads if long, bold sparingly for the one line that matters. Assume skimming.
  6. One CTA — a single action (reply, click, try, share). Multiple CTAs split attention and lower every click.
  7. Sign-off — human, brief, optionally a P.S. (the P.S. is the second-most-read line — use it for the CTA or a hook to next issue).

Output template

Subject options:
1. <...>
2. <...>
3. <...>

Preview text: <...>

---

<Open — the hook>

<Body — the one idea, developed, scannable>

**<CTA line>** → [link/action]

<Sign-off>
P.S. <optional — CTA reinforcement or teaser>

Rules

  • One idea per issue. If the user dumps five topics, pick the strongest and offer the rest as future issues — don't cram.
  • Write to one person, not "everyone". "You" singular.
  • The open must not be a warm-up; delete any first line that could be cut without loss.
  • One CTA. If the user insists on two, make one clearly primary and one a low-key P.S.
  • Match the sender's voice if samples are given; otherwise default to plain, warm, direct.

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 475 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

  • give three subject options
  • develop one idea
  • delete every warm-up opening line
  • match the sender's voice

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.