newsletter
Write a ready-to-send newsletter issue (and, when starting from zero, the recurring format and cadence to commit to): subject line options, preview text, body in one of six proven formats, and a single engagement CTA. Use when the user says 'write my newsletter', 'this week's issue', 'I want to start a newsletter', 'what should I send my list', 'help me email my subscribers regularly', or shares content to turn into an issue. Produces a complete issue draft with subject/preview variants — or a Newsletter Blueprint (format, cadence, section template) plus the first issue when setting one up.
- Installs
- 72
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/sanky369/vibe-building-skills --skill newsletter- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads newsletter automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Newsletter
Write newsletter issues that subscribers open, read, and reply to. A newsletter is a recurring relationship, not a broadcast: it must be consistent (same format and cadence every time), valuable (useful before promotional), and personal (sounds like one human wrote it to one human). Prime directive: the reader must finish the issue glad they opened it — value first, promotion never more than a postscript.
When to use / when not to
- Use for writing a newsletter issue, designing a new newsletter (format + cadence + template), or fixing a stale one (falling opens, no replies).
- If the user wants automated emails triggered by behavior (welcome series, launch, sales sequence), use
skills/marketing/email-sequences— a newsletter is a recurring broadcast, not an automation. - If the user has no list and no way to get subscribers, route to
skills/marketing/lead-magnetfirst. - If the source material is a blog post being adapted for many channels at once, use
skills/marketing/content-atomizer(it can hand the newsletter item back here).
Intake
Ask in one batch, only what's missing:
- Audience and list — who subscribes, roughly how many, and what they signed up expecting.
- This issue's raw material — a story, lesson, link roundup, data point, or recent piece of content. If nothing, ask for one recent professional observation or lesson; there is always one.
- Voice — existing issues or a brand-voice guide to match (use
skills/marketing/brand-voiceoutput if it exists). - Goal — pure relationship-building, or is there something to softly promote?
If the user is starting a newsletter from scratch, also ask what they can sustain: writing capacity and how much source material their work naturally generates. Otherwise infer format and cadence from past issues. If enough is known, state assumptions and draft — don't stall.
Workflow
1. If new: lock the format and cadence (the Blueprint)
Pick one primary format by decision rule — the user can guest-star other formats occasionally, but the flagship format is what subscribers learn to expect:
| If the user… | Format | Skeleton |
|---|---|---|
| Reads widely, low writing capacity | Curated | Personal opening note → 5–10 links, each with 1–2 sentences of your take (the commentary is the product) → sign-off |
| Has rich personal/client experiences | Story-driven | Hook → story → the lesson → how the reader applies it → sign-off |
| Sells expertise (consultant, coach, B2B) | Educational | Why this matters → the concept/framework → 2–3 real examples → how to apply → sign-off |
| Has network access to interesting people | Interview | Who + why them → 5–10 Q&As → your key takeaway → sign-off |
| Works with data or research | Data-driven | Surprising finding → the data → what it means → what to do with it → sign-off |
| Builds in public / personal brand | Personal update | Working on → learning → thinking about → one recommendation → sign-off |
Cadence by decision rule: weekly if their work generates material weekly and they'll actually sustain it; otherwise bi-weekly (the default recommendation — heuristic: a kept bi-weekly schedule beats a broken weekly one); monthly only if the format is heavyweight (interview, data-driven). Fix the send day/time and put it in the Blueprint.
2. Extract the issue's one idea
Every issue carries exactly one central idea (curated format: one theme unifying the links). From the raw material, pull the single most useful/surprising insight for this audience. If the material holds several strong ideas, list them, pick the best for now, and bank the rest as future issue seeds in the delivery notes.
3. Draft the issue
- Subject line: write 3 candidates, ≤45 characters each, specific and curiosity- or benefit-driven. No clickbait the body doesn't cash; no ALL CAPS; at most one punctuation flourish.
- Preview text: ≤90 characters that extends (not repeats) the subject.
- Opening: 1–3 sentences, personal and concrete — an observation, moment, or admission. Never "Welcome to another issue" or weather-report throat-clearing.
- Body: follow the format skeleton from Step 1. Short paragraphs (≤3 sentences), subheads or bold lead-ins if the issue runs past ~300 words, written to one reader ("you", never "you all"/"subscribers").
- CTA: exactly one, engagement-first — "Hit reply and tell me X" beats "click here" for relationship-building. If there's a promotion, it rides in the P.S., not the body, unless the user explicitly wants a promotional issue.
- Sign-off: first name + optional P.S. (the P.S. is prime real estate: a bonus link, question, or the soft promo).
Length target: 300–800 words for original-content formats; curated can run longer but each link blurb stays ≤2 sentences of commentary.
4. Self-review and deliver
Run the quality bar. Then deliver in the required output format, including next-issue seeds so the user never faces a blank page.
Required output format
# Newsletter Issue — [working title]
## Subject line options
1. "…" (n chars)
2. "…" (n chars)
3. "…" (n chars)
Recommended: #_ — [one-line reason]
## Preview text
"…" (n chars)
## Body
[Full issue: opening → format-skeleton body → CTA → sign-off → P.S.]
## Send notes
- Format: [which of the six] · Cadence slot: [day/time]
- CTA: [the one action asked]
- Promo present: [none | P.S. only | promotional issue]
## Next-issue seeds
- [2–3 banked ideas pulled from this material or conversation]
When setting up a new newsletter, precede the issue with:
# Newsletter Blueprint — [name]
- Audience & promise: [who subscribes and what each issue gives them]
- Flagship format: [one of six] — [why, per decision rule]
- Cadence: [weekly/bi-weekly/monthly], sent [day/time]
- Section template: [the recurring skeleton, so every issue is structurally identical]
- Voice notes: [3–5 bullets]
- Metrics to watch: open rate trend, reply count, unsubscribe spikes per issue
Quality bar
Check every item; fix before delivering:
- Every subject line ≤45 characters (count them) and honestly cashed by the body
- Preview text ≤90 characters and not a repeat of the subject
- Opening is personal/concrete — no "welcome to this week's issue" boilerplate
- Exactly one idea; exactly one CTA
- Promotion absent or confined to the P.S. (unless explicitly a promo issue)
- No paragraph over 3 sentences; issue scannable on a phone
- Sounds like the user, not like "a newsletter" — read it aloud; generic sentences get cut
- Every factual claim cited, attributable to the user's own experience, or cut; no invented anecdotes presented as the user's
- Curated format: every link has a stated reason it earned inclusion
Integration
skills/marketing/brand-voice— supplies the voice guide the issue must match; run it first if the user has no defined voice.skills/marketing/lead-magnet— builds the subscriber-acquisition offer; new subscribers flow throughskills/marketing/email-sequences(welcome) before landing on this newsletter.skills/marketing/email-sequences— owns triggered/automated email; the newsletter is the ongoing touchpoint subscribers graduate into.skills/marketing/content-atomizer— turns blog/video content into newsletter items, and turns strong newsletter issues back into social posts.skills/marketing/seo-content— published articles are recurring issue material; pass title, link, and one-sentence hook.
FAQ
What does the newsletter skill do?
Write a ready-to-send newsletter issue (and, when starting from zero, the recurring format and cadence to commit to): subject line options, preview text, body in one of six proven formats, and a single engagement CTA. Use when the user says 'write my newsletter', 'this week's issue', 'I want to start a newsletter', 'what should I send my list', 'help me email my subscribers regularly', or shares content to turn into an issue. Produces a complete issue draft with subject/preview variants — or a Newsletter Blueprint (format, cadence, section template) plus the first issue when setting one up.
How do I install newsletter?
Run npx skills add https://github.com/sanky369/vibe-building-skills --skill newsletter in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/newsletter/ (personal) or .claude/skills/newsletter/ (project).
Which AI agents can use newsletter?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is newsletter safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains newsletter?
It is published by sanky369 in sanky369/vibe-building-skills. It has 72 recorded installs.
More from sanky369/vibe-building-skills
social-graphics
sanky369/vibe-building-skills
Produce platform-correct social media graphics: pick the right dimensions and layout per platform, write the headline/body/CTA copy, build the generation prompt, and generate the image via the repo's FAL.ai pipeline. Use whenever the user wants a social post visual, Instagram post/story/carousel, LinkedIn graphic, Twitter/X image, TikTok thumbnail, Pinterest pin, launch announcement graphic, or 'something to post about X' — even if they never name a platform. Also use to adapt one design across several platforms. Produces a Social Graphic Spec per asset (platform, dimensions, layout, copy, full generation prompt) plus generated images when FALAPIKEY is available.
direct-response-copy
sanky369/vibe-building-skills
Write copy engineered to drive one specific action — landing pages, sales pages, opt-in pages, ads, promotional emails — using an eight-part direct-response architecture (hook, problem, mechanism, solution, proof, objections, CTA, urgency). Use when the user says 'write my landing page / sales page / ad', 'this page isn't converting', 'rewrite my homepage copy', 'write copy for my lead magnet page', or any request for persuasive copy with a measurable action at the end. Produces the full copy draft, section-labeled against the architecture, plus hook alternatives and a conversion checklist.
tweet-writer
sanky369/vibe-building-skills
Write high-engagement tweets and X/Twitter threads, grounded in live research of what's currently working in the user's niche: researches viral examples via web search, then drafts hook variants, a single-tweet version, and a thread version with alternates to test. Use when the user says 'write a tweet about X', 'turn this into a thread', 'help me go viral', 'grow my X/Twitter account', 'my tweets get no engagement', or shares an idea/article to tweet — any X/Twitter content request. Produces a Tweet Package: 3 hook options, final single tweet, full thread, and posting notes.
typography-system
sanky369/vibe-building-skills
Build or repair a typography system: a modular type scale, font choices and loading, hierarchy, line-height/line-length, and fluid sizing — delivered as tokens (Tailwind fontSize config or CSS variables) applied to real components. Use when the user says 'the text looks off', 'fonts are inconsistent', 'headings don't stand out', 'pick fonts for me', 'it's hard to read', 'too many font sizes', or when an audit finds font-size sprawl. Chooses the scale ratio from product density (dense app vs marketing vs editorial), verifies contrast and measure, and produces the type tokens plus a migration map from existing rogue sizes.
remotion-script-writer
sanky369/vibe-building-skills
Write a complete, render-ready Remotion video script as structured JSON: analyze the user's codebase or product, break the video into timed scenes, specify every visual element, animation, transition, and voiceover line, and list required assets and Remotion packages. Use whenever the user wants a Remotion video, a programmatic/code-rendered video, a product demo video of their app, an animated coding tutorial, a data-visualization video, or short-form animated social content — trigger on 'make a video of my app', 'Remotion', 'animated demo', 'code walkthrough video', 'render a video from code'. Produces a Remotion Script JSON (videoMetadata, scenes[], requiredAssets, technicalRequirements) that Remotion agent tooling can implement directly.
product-video
sanky369/vibe-building-skills
Open the skill to read its SKILL.md instructions.
Popular marketing & seo skills
reddit-automation
flowkit-labs/skills
Find Reddit threads where people are genuinely asking for what you offer, then draft short, genuinely helpful replies — disclosing your affiliation honestly and naming your product only when it truly answers the question. Two moves: discovery — scan the right subreddits for real needs (recommendation asks, expressed pain, competitor mentions) and rank the few threads where you can actually help; drafting — write from real experience, respect each community's self-promo rules, and keep a human in the loop to review and post. This markets on Reddit the honest way: contribute value, disclose who you are, never astroturf. Distilled from the playbook behind doany.ai's Reddit agent. Triggers on "find reddit opportunities", "reddit marketing", "reddit automation", "reply on reddit for my product", "reddit community engagement", "reddit lead gen", or any ask to turn Reddit threads into genuine, disclosed marketing replies.
twitter-automation
101-skills/superpowers
Automate Twitter/X with posting, engagement, and user management via inference.sh CLI. Apps: x/post-tweet, x/post-create (with media), x/post-like, x/post-retweet, x/dm-send, x/user-follow. Capabilities: post tweets, schedule content, like posts, retweet, send DMs, follow users, get profiles. Use for: social media automation, content scheduling, engagement bots, audience growth, X API. Triggers: twitter api, x api, tweet automation, post to twitter, twitter bot, social media automation, x automation, tweet scheduler, twitter integration, post tweet, twitter post, x post, send tweet
twitter-automation
magentosh/superpowers
Automate Twitter/X with posting, engagement, and user management via inference.sh CLI. Apps: x/post-tweet, x/post-create (with media), x/post-like, x/post-retweet, x/dm-send, x/user-follow. Capabilities: post tweets, schedule content, like posts, retweet, send DMs, follow users, get profiles. Use for: social media automation, content scheduling, engagement bots, audience growth, X API. Triggers: twitter api, x api, tweet automation, post to twitter, twitter bot, social media automation, x automation, tweet scheduler, twitter integration, post tweet, twitter post, x post, send tweet
twitter-automation
qu-skills/superpowers
Automate Twitter/X with posting, engagement, and user management via inference.sh CLI. Apps: x/post-tweet, x/post-create (with media), x/post-like, x/post-retweet, x/dm-send, x/user-follow. Capabilities: post tweets, schedule content, like posts, retweet, send DMs, follow users, get profiles. Use for: social media automation, content scheduling, engagement bots, audience growth, X API. Triggers: twitter api, x api, tweet automation, post to twitter, twitter bot, social media automation, x automation, tweet scheduler, twitter integration, post tweet, twitter post, x post, send tweet
product-launch-video
heygen-com/hyperframes
Turn a product or marketing URL, pasted script, or brief into a product launch / promo video — SaaS promos, feature reveals, product demos, app and company launches. Use when the user wants to market, launch, promote, or reveal a product; the default for any commercial URL. Site tours / showcases of a website route here too — the brief carries the show-it-as-is intent. Unclear → /hyperframes.
twitter-automation
skills-shell/superpowers
Automate Twitter/X with posting, engagement, and user management via inference.sh CLI. Apps: x/post-tweet, x/post-create (with media), x/post-like, x/post-retweet, x/dm-send, x/user-follow. Capabilities: post tweets, schedule content, like posts, retweet, send DMs, follow users, get profiles. Use for: social media automation, content scheduling, engagement bots, audience growth, X API. Triggers: twitter api, x api, tweet automation, post to twitter, twitter bot, social media automation, x automation, tweet scheduler, twitter integration, post tweet, twitter post, x post, send tweet