newsletter
Skill1 starsChanged 7 months agoMITView on GitHub
Write email newsletters with curated content, summaries, formatted sections, compelling subject lines, and preview text. Trigger with "write a newsletter", "draft this week's email", "newsletter about", "email digest for", or when the user needs to produce a recurring or one-off newsletter for subscribers.
23 other projects use a version of this.
Adopted by
Most recently taken up by
- oivanfelipe/claude-skillstheir own version, first seen Nov 8, 2026
- Insightful-Pipe/email-marketing-skillstheir own version, first seen Nov 8, 2026
- MoizIbnYousaf/marketing-clitheir own version, first seen Nov 1, 2026
- Anglesite/anglesite-skillstheir own version, first seen Oct 27, 2026
- guiloureiromkt/ultra-skillstheir own version, first seen Oct 21, 2026
- matteotitta/claude-marketing-contenttheir own version, first seen Oct 20, 2026
Used with
Projects with it also use lead-magnet, linkedin and 5 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
robertbstillwellSkilllead-magnet
Create lead magnets and gated content to capture email subscribers and leads. Use when asked to design checklists, templates, calculators, mini-courses, whitepapers, or other downloadable content offers. Trigger phrases: "lead magnet", "gated content", "email capture", "content offer", "free download", "checklist", "template", "whitepaper", "swipe file", "content upgrade", "opt-in offer".
Also in 4 projects that use this
kkoppenhaverSkilllinkedin
Write LinkedIn posts in Keanan's voice. Use when drafting LinkedIn content, creating professional posts, or sharing builder-focused insights. Triggers include requests to "write a LinkedIn post", "draft something for LinkedIn", "help me post on LinkedIn", or any LinkedIn content creation. Generates upbeat, builder-centric content mixing practical how-tos with candid humor.
Also in 3 projects that use this
Dokkabei97Skillbrand-voice
Defines and enforces brand voice guidelines for startups. Creates tone, style, messaging frameworks and provides consistency checks across all content. Ensures every piece of communication sounds like it comes from the same brand.
Also in 4 projects that use this
silvainfmSkillreferral-program
When the user wants to create, optimize, or analyze a referral program, affiliate program, or word-of-mouth strategy. Also use when the user mentions 'referral,' 'affiliate,' 'ambassador,' 'word of mouth,' 'viral loop,' 'refer a friend,' or 'partner program.' This skill covers program design, incentive structure, and growth optimization.
Also in 3 projects that use this
silvainfmSkilllaunch-strategy
When the user wants to plan a product launch, feature announcement, or release strategy. Also use when the user mentions 'launch,' 'Product Hunt,' 'feature release,' 'announcement,' 'go-to-market,' 'beta launch,' 'early access,' 'waitlist,' or 'product update.' This skill covers phased launches, channel strategy, and ongoing launch momentum.
Also in 3 projects that use this
indranilbanerjeeSkillkeyword-research
Research keywords via the connected data source: intent, gaps. Grouping → keyword-cluster. \"what keywords should we target\"
Also in 3 projects that use this
- +1 more from silvainfm
Other versions23 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 23
- masamasa59/ai-agent-papers★ 1.7ksame name
- OpenClaudia/openclaudia-skills★ 731same name
- getnao/sylph★ 195same name
- AlemTuzlak/skills★ 45same name
- MoizIbnYousaf/marketing-cli★ 33same name
- sanky369/vibe-building-skills★ 30same name
- coopersimson96/ai-content-system★ 17same name
- Anglesite/anglesite-skills★ 15same name
- jsath/claude-skills★ 14same name
- calven-ai/marketing-as-code★ 10same name
13 more not listed
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 repository164 other files it gives its agents.
- instrument-data-to-allotropeSkill
- literature-reviewSkill
- nextflow-developmentSkill
- scientific-problem-selectionSkill
- scvi-toolsSkill
- single-cell-rna-qcSkill
- discover-brandSkill
- enforce-voiceSkill
- generate-guidelinesSkill
- csat-reportSkill
- customer-escalationSkill
- customer-researchSkill
- draft-responseSkill
- kb-articleSkill
- sentiment-analysisSkill
- ticket-triageSkill
- analyzeSkill
- build-dashboardSkill
- create-vizSkill
- data-context-extractorSkill
- data-modelingSkill
- data-pipelineSkill
- etl-designSkill
- explore-dataSkill
- sql-queriesSkill
- statistical-analysisSkill
- validate-dataSkill
- write-querySkill
- accessibility-reviewSkill
- component-librarySkill
- design-critiqueSkill
- design-handoffSkill
- design-systemSkill
- frontend-designSkill
- research-synthesisSkill
- user-researchSkill
- ux-copySkill
- wireframingSkill
- Agent DevelopmentSkill
- CLAUDE.md ManagementSkill
- MCP Server BuilderSkill
- Plugin DevelopmentSkill
- Prompt EngineeringSkill
- Skill CreatorSkill
- curriculum-designSkill
- lesson-planningSkill
- quiz-generatorSkill
- study-guideSkill
- tutoringSkill
- api-designSkill
- architectureSkill
- ci-cd-pipelineSkill
- code-reviewSkill
- database-migrationSkill
- debugSkill
- dependency-auditSkill
- deploy-checklistSkill
- documentationSkill
- error-handlingSkill
- git-workflowSkill
- The first 60 shown.
The file
Show its rules and text
We split this skill into the rules it gives an agent
16 rules. 0 are common, 16 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 22 edited versions we read keep these.
16
Distinctive
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
- Distinctive: line 28
Write email newsletters that subscribers open, read, and act on.
- Distinctive: line 55
Keep subject lines under 50 characters for mobile display.
- Distinctive: line 56
Write preview text (40-90 characters) that complements — not repeats — the subject line.
- Distinctive: line 57
Avoid spam triggers: all caps, excessive punctuation, "free", "act now."
- Distinctive: line 74
Keep total word count between 200-500 words for digests, 500-1000 for narratives.
- Distinctive: line 75
Use short paragraphs (2-3 sentences max) — email is scanned, not read.
- Distinctive: line 76
Ensure the key message is visible without scrolling (above the fold).
- Distinctive: line 77
Use bullet points and bold text for scanability.
- Distinctive: line 80
Test that the content makes sense in plain text (many clients strip HTML).
- Distinctive: line 86
Read the subject line + preview text together — do they create a compelling reason to open?
- Distinctive: line 89
Check all links are correct and descriptive.
- Distinctive: line 90
Verify personalization tokens (if any) have fallback values.
- Distinctive: line 143
Write subject lines last — you need to know the content to summarize it compellingly.
- Distinctive: line 146
Keep curated summaries original.
- Distinctive: line 147
Test subject lines by reading them as the reader would: in a crowded inbox between 20 other emails.
- Distinctive: line 148
If the user has past open-rate data, use it to inform subject line style and content priorities.
“Common” is measured: kept by at least 6 in 10 of the 22 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Newsletter Writing
Write email newsletters that subscribers open, read, and act on. Covers content curation, section writing, subject line optimization, and formatting for email clients.
Workflow
Step 1: Plan the Edition
Define the newsletter structure and content:
- Confirm the edition theme, cadence (weekly, monthly, ad hoc), and audience.
- Identify 3-7 content items to include: articles, updates, tips, announcements, or curated links.
- Determine the newsletter format:
- Digest: Brief summaries of multiple items with links.
- Narrative: Single-topic deep dive with a personal voice.
- Announcement: Product launch, event, or major update.
- Roundup: Curated links and resources around a theme.
- Hybrid: Lead story plus curated items.
- Establish the primary CTA for this edition.
Step 2: Write Subject Line and Preview Text
Craft the first impression — subject line and preview text determine open rates:
- Generate 3-5 subject line options using these proven patterns:
- Curiosity gap: hints at value without revealing everything.
- Benefit-driven: states what the reader will gain.
- Numbered list: "5 tools that..." or "3 lessons from..."
- Timely hook: ties to a current event or deadline.
- Keep subject lines under 50 characters for mobile display.
- Write preview text (40-90 characters) that complements — not repeats — the subject line.
- Avoid spam triggers: all caps, excessive punctuation, "free", "act now."
Step 3: Write the Content
Draft each section following email-specific writing rules:
- Header/banner: Newsletter name, edition number or date, one-line tagline.
- Lead section: The most valuable or compelling item. 2-3 paragraphs max. Hook the reader immediately.
- Body sections: Each item gets a bold headline, 2-4 sentence summary, and a clear link or CTA. Use consistent formatting across items.
- Personal note (optional): A brief, authentic aside from the sender. Builds connection.
- CTA section: One primary action per newsletter. Make the button text specific ("Read the guide" not "Click here").
- Footer: Unsubscribe link, social links, contact info, and the reason they received this email.
Step 4: Optimize for Email
Apply email-specific formatting and deliverability practices:
- Keep total word count between 200-500 words for digests, 500-1000 for narratives.
- Use short paragraphs (2-3 sentences max) — email is scanned, not read.
- Ensure the key message is visible without scrolling (above the fold).
- Use bullet points and bold text for scanability.
- Limit to 2-3 links per section to avoid spam filters.
- Include alt text for any images in case they are blocked.
- Test that the content makes sense in plain text (many clients strip HTML).
Step 5: Review
Final quality check:
- Read the subject line + preview text together — do they create a compelling reason to open?
- Does the newsletter deliver on the subject line's promise within the first section?
- Is there exactly one clear CTA, and is it easy to find?
- Check all links are correct and descriptive.
- Verify personalization tokens (if any) have fallback values.
Output Format
**Subject line options**:
1. [Option A]
2. [Option B]
3. [Option C]
**Preview text**: [40-90 characters]
---
# [Newsletter Name] — [Edition/Date]
[Lead section]
---
## [Section 1 Headline]
[Summary — 2-4 sentences]
[Link/CTA]
## [Section 2 Headline]
[Summary — 2-4 sentences]
[Link/CTA]
## [Section 3 Headline]
[Summary — 2-4 sentences]
[Link/CTA]
---
[Personal note or sign-off]
[Footer: unsubscribe, social links, legal]Examples
User: "Write this week's developer newsletter featuring our new API release" Action: Lead with the API release announcement, add 2-3 curated developer resources, include a tutorial link as the CTA, write subject lines emphasizing the new capability.
User: "Monthly roundup of AI news for our subscribers" Action: Curate 5-7 items, write concise summaries with commentary, organize by theme (research, tools, industry), open with the most significant development.
User: "Announcement newsletter for our product launch" Action: Single-topic format, lead with the value proposition, include key features as scannable bullets, CTA to sign up or try the product, add a brief founder note.
Best Practices
- Front-load value: the best item goes first, not last.
- Write subject lines last — you need to know the content to summarize it compellingly.
- One CTA per newsletter. Secondary actions can exist but should be visually subordinate.
- Maintain a consistent voice across editions — subscribers develop a relationship with the writer.
- Keep curated summaries original; do not copy-paste from source articles.
- Test subject lines by reading them as the reader would: in a crowded inbox between 20 other emails.
- If the user has past open-rate data, use it to inform subject line style and content priorities.
- Include a "reply to this email" prompt occasionally — replies boost deliverability and build engagement.
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
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.

