newsletter
Skill0 starsChanged 34 days agoMITView on GitHub
Writes one B2B newsletter issue built on a single idea: picks the idea from your expert point of view and recent
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
- nisarth/claude-skills-storetheir 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
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 repository4 other files it gives its agents.
- content-auditSkill
- content-opsSkill
- content-strategySkill
- thought-leadershipSkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 4 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 22 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 17
Use it for a weekly or fortnightly B2B newsletter, or to turn a recent piece of work into an issue.
- Very specific: line 19
Don't use it for long-form essays (use /thought-leadership), product announcements that need launch planning, or a link digest with no …
- Very specific: line 23
Read these if they exist. Agency users: swap context/ for clients/<client>/context/.
- Distinctive: line 31
Ask the user for: what they've worked on, learned or argued about in the last two weeks, the newsletter's usual length, and what the call …
- Very specific: line 33
If context/expert-pov/ is missing, ask the user three questions: what surprised you lately, what do you disagree with in your field, and …
- Distinctive: line 45
Subject lines: Write five options under 50 characters: one plain statement of the idea, one question, one with a number, one naming the …
- Distinctive: line 47
Check: Run the checklist below and fix anything that fails.
“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
Write one newsletter issue that a busy buyer reads to the end. One idea per issue, made concrete with a real example, ending on one takeaway and one ask. Then give the issue its best chance of being opened (subject lines) and seen (a LinkedIn post).
When to use it
Use it for a weekly or fortnightly B2B newsletter, or to turn a recent piece of work into an issue.
Don't use it for long-form essays (use /thought-leadership), product announcements that need launch planning, or a link digest with no point of view.
Inputs
Read these if they exist. Agency users: swap context/ for clients/<client>/context/.
context/expert-pov/: opinions, stories and lessons worth sharing. The main source of ideas.context/icp/: who reads it and what they're stuck on.context/brand/: voice rules.outputs/content/: recent strategy, articles and audits. Recent work is often the best raw material.outputs/content/*-content-strategy.md: the clusters, so the issue fits the plan.
Ask the user for: what they've worked on, learned or argued about in the last two weeks, the newsletter's usual length, and what the call to action should point to (a reply, a resource, a call, an event).
If context/expert-pov/ is missing, ask the user three questions: what surprised you lately, what do you disagree with in your field, and what did a customer or colleague get wrong that you see often?
Steps
- Pick one idea. List three candidates from
context/expert-pov/, recent work and the user's answers. Pick the one that is specific, useful to the ICP, and grounded in something that actually happened. Produces: the idea in one sentence, plus why this reader should care now. - Find the proof. One concrete example: a project, a before-and-after, a mistake, a number from real work. If it involves a customer, generalise it ("a Series B fintech") unless the user confirms they can be named. Produces: the example with its source.
- Write the issue in this order:
- Hook (2-3 sentences): the tension or surprise, aimed at the reader's problem. No "welcome back" or "this week I want to talk about".
- The idea (one short section): state it plainly, then explain why it's true.
- Proof or example (the longest section): what happened, what was done, what changed.
- One takeaway: what the reader can do or think differently on Monday, in a sentence or two.
- One call to action: a single ask that fits the takeaway.
- Subject lines. Write five options under 50 characters: one plain statement of the idea, one question, one with a number, one naming the reader's problem, one curiosity line that the issue actually pays off. Recommend one. Add a preview text line.
- LinkedIn promo post. 150-300 words that stand on their own: the hook rewritten for the feed, the idea in brief, one line from the example, then an invite to read or subscribe. Plain text, no emojis, no hashtag lists.
- Check. Run the checklist below and fix anything that fails.
Length: 500-1,200 words for the issue unless the user's newsletter runs differently. Match what they already send.
What good looks like
- One idea. A reader can repeat it in a sentence.
- The example is real and specific. Invented numbers or customers are never used; a missing fact is marked
[check]for the user. - The hook is about the reader, not the writer or the newsletter.
- Exactly one takeaway and one call to action.
- Subject lines are honest: the issue delivers what the line promises.
- It reads like a person wrote it: contractions, short sentences, plain words.
Mistakes to avoid
- Three ideas in one issue. Save two for later issues.
- A summary of links with no opinion.
- Burying the idea under a long personal preamble.
- Clickbait subject lines that the issue doesn't pay off.
- A promo post that only says "new issue is out".
- Several calls to action competing with each other.
Output
Write to outputs/content/MMYY-newsletter-<topic-slug>.md:
- Recommended subject line, four alternatives, preview text.
- The issue.
- The LinkedIn promo post.
- Sources and any
[check]flags for the user.
Your email platform (Substack, beehiiv, Kit or another) is where you paste and send; this skill only drafts. Next step: if the idea deserves more room, expand it with /thought-leadership.
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.

