agentleFS
Sign inStart free
VercelKnown publishervercel-labs/eve-content-agent-template/agent/skills/newsletter-style/SKILL.md

newsletter-style

Skill32 starsChanged 3 days agoMITView on GitHub

Use when drafting or editing an email newsletter issue in the house voice.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 1

    1. vercel/eve★ 5.9k100% same

    Edited · 0

    None found.

    Wrote their own version · 0

    None found.

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository6 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When writing or editing a newsletter:

    line 7
  2. Distinctive:

    Write to one person, not a list.

    line 9
  3. Distinctive:

    Every issue has one clear next step (read, try, reply) — not five competing CTAs.

    line 19

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Newsletter voice & style

When writing or editing a newsletter:

  • Write to one person, not a list. "You", not "everyone".
  • Subject line earns the open: specific and honest, never clickbait. Under ~50 chars, and front-load the point — mobile inboxes cut off around 33–43 characters.
  • Set the preheader on purpose: extend the subject line, don't repeat it. Leave it blank and the client grabs the first stray text it finds.
  • Open in the first sentence — no "Welcome back to another edition of…".
  • One main thing per issue. Curated links can follow, but the issue has a spine.
  • Readers scan, not read: they give a whole issue about 51 seconds (~200 words) before moving on. Lead each chunk with a meaningful subheading and put the load-bearing words first.
  • Conversational but tight. Read it aloud; cut what you'd never say.
  • Every issue has one clear next step (read, try, reply) — not five competing CTAs.
  • No "in this edition we'll cover" preambles; just start.

Structure

  1. Subject line — the promise, specific and true.
  2. Preheader — extends the subject line; the second half of the hook, not a repeat.
  3. Open — the one idea, in the first two sentences.
  4. Body — the idea developed, or 2–4 curated items with a sentence of why each matters. Short paragraphs, one point per chunk, a few keywords bolded so a scan still lands.
  5. Close — the single next step, and a human sign-off.

References

  • references/best-practices.md — sourced checklist of subject lines, preheaders, scannability, single CTA, sender identity, and plain-text-vs-HTML for newsletters.
  • references/email-specs.md — concrete specs: subject line and preheader character limits and mobile truncation points, from-name, ~600px width, CTA count, plain-text alt.
  • references/banned-words.json — the list of words to avoid. Read it once up front for awareness, then run the check_style tool on your draft to check it against this file before proposing the draft to the writer.

Shared references

Shared global references for all skills in the content agent. These apply regardless of the content type.

  • references/ai-phrases-to-avoid.md — AI-tell words, phrases, and punctuation to avoid.
  • references/plain-english-alternatives.md — plain-English swaps for bloated or vague wording.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free