email-and-newsletter — Claude Code skill: what it does, how to install
A skill for newsletter strategy: build an owned subscriber list, plan editions, and loop email with social.
npx skills add social-media-skills/skills --skill email-and-newsletter -a claude-codeWhat email-and-newsletter does
The skill handles strategy and drafts. It pushes you toward one problem and one reader, an owned list grown from social capture, a welcome sequence, and a strong edition 2 — the point where subscribers usually churn. Everything runs on the INBOX framework, from picking the niche to closing the social↔email loop.
It reads brand-profile, voice-builder and content-pillars before doing anything, so positioning and brand voice need to exist first. Sending stays outside: the ESP is external and human-run, while WoopSocial publishes only the social side. Metrics come from the ESP and GA4, and clicks and replies count for more than opens.
Consent and a visible unsubscribe link are required, along with honest monetization. Bought lists and no-consent sends are out of scope, so this is a good moment to check how your opt-in actually works.
What it helps with
- build an owned subscriber list instead of rented social reach
- plan a welcome sequence for new subscribers
- keep readers past edition 2 and 3
- turn one newsletter edition into a week of social posts
- choose between beehiiv, Substack, LinkedIn and Kit by goal
Example prompts for the agent
- help me start a newsletter using the INBOX framework
- draft a welcome sequence in our brand voice
- break my last newsletter edition into social posts
How to install email-and-newsletter
1Skills CLI (Vercel)
npx skills add social-media-skills/skills --skill email-and-newsletter -a claude-code2Manually: put the files in place
~/.claude/skills/email-and-newsletter/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/email-and-newsletter/
1Skills CLI (Vercel)
npx skills add social-media-skills/skills --skill email-and-newsletter -a codex2Manually: put the files in place
.agents/skills/email-and-newsletter/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add social-media-skills/skills --skill email-and-newsletter -a cursor2Manually: put the files in place
.cursor/skills/email-and-newsletter/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install social-media-skills/skills email-and-newsletter2Manually: put the files in place
.github/skills/email-and-newsletter/SKILL.md1Skills CLI (Vercel)
npx skills add social-media-skills/skills --skill email-and-newsletter -a gemini-cli2Platform CLI
gemini skills install https://github.com/social-media-skills/skills --path skills/email-and-newsletterManually: put the files in place
.devin/skills/email-and-newsletter/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add social-media-skills/skills --skill email-and-newsletter -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about email-and-newsletter
How do I install email-and-newsletter in Claude?
Run npx skills add social-media-skills/skills --skill email-and-newsletter -a claude-code. The skill lands at ~/.claude/skills/email-and-newsletter/SKILL.md.
What does email-and-newsletter do?
It plans newsletter strategy and drafts editions: niche, welcome sequence, 70-20-10 edition structure, and the loop between email and social.
Does the skill send emails itself?
No. Sending happens in an external ESP set up by a human; the skill only strategizes and drafts. Metrics are read from the ESP and GA4 afterwards.
Source text
SKILL.md · MIT
--- name: email-and-newsletter description: >- Email and newsletter strategy for creators and brands — the owned-audience layer that social feeds. Use when someone wants to "start/grow a newsletter," "build an email list," "turn followers into subscribers," "should I use Substack/beehiiv/LinkedIn," "repurpose my newsletter into social (or vice versa)," or build the audience layer social can't take away. Runs email (habit) + a web archive (discovery) off the same work and loops content social<->email. Uses the INBOX framework. Reads brand-profile + voice-builder + content-pillars first. WoopSocial does NOT send email — the agent strategizes and drafts, the ESP is external and human-run, WoopSocial publishes only the social side; metrics come from the ESP + GA4, never fabricated; consent + unsubscribe required. Distinct from link-in-bio-and-traffic (capture), cross-platform-repurposing (same-moment), and lead-magnets-and-funnels (the magnet). version: 1.0.0 --- # email-and-newsletter The **owned channel** — the newsletter is the audience layer social can't take away, plus the email↔social loop. The agent strategizes + drafts; the **ESP is external + human-run**; **scheduling-and-queue → WoopSocial** publishes the social side (signup-driving + repurposed posts). ## The POV: own the audience, run two surfaces Every platform *rents* you attention and can change the rules overnight; a newsletter is the one audience layer you **own** — opt-in, deliverable, measurable, the **highest-ROI channel** and the thing that makes everything else compound. "Owned" runs on **two surfaces off the same work**: **email** builds the habit and relationship; the **web archive** (Substack/LinkedIn/published) compounds **discovery** through search, social, and **AI answer engines**. Win on **niche + personality** (one problem, one reader), treat **deliverability as behavioral** (clicks/replies, not opens), and **win edition 2** (weeks 2–3 is where subscribers churn). ## Read these first 1. **brand-profile** — positioning/offer. 2. **voice-builder** — the personality that is the moat. 3. **content-pillars** — the one problem/topic the newsletter owns. ## The framework: INBOX (Depth: `references/the-inbox-framework.md`.) - **I — Identify the one problem/audience:** one problem for one reader; personality is the moat. - **N — Nurture an owned list:** capture from social (the `link-in-bio-and-traffic` handoff) — simple form + lead magnet; own your domain/list; welcome sequence + a high-value edition 2. - **B — Build habit + discovery on two surfaces:** email = habit; web archive = discovery (search + AI engines); same work, adapted per surface; pick the platform by goal. - **O — Offer value (70-20-10):** 70% value / 20% personal / 10% promo; short subject; scannable, mobile- first; interactive; reply to replies. - **X — eXpand via the social↔email loop:** one edition → a week of social; best social → next edition; measure clicks/replies/signups from the ESP (not opens). ## The reality (verify-quarterly) Owned-audience ROI; email-habit + web-discovery (+ AI engines); behavioral deliverability (clicks/replies > opens; SPF/DKIM/DMARC, list hygiene, cadence); niche + personality; capture + 70-20-10 + retention (weeks 2–3); platforms (beehiiv/Substack/LinkedIn/Kit — own your domain/list); honest monetization; the social↔email loop: `references/newsletter-2026-reality.md`. Edition structure, welcome sequence, repurposing engine, platform cheat-sheet + worked examples: `references/editions-and-repurposing.md`. ## Honest scope (never violate) - **WoopSocial does not send email** (no ESP/list/capture/open tracking). Sending happens in an **external ESP**, human-set-up. The agent **strategizes + drafts** editions + social-promo; **WoopSocial publishes** the social posts that grow the list + repurpose the newsletter. - **Metrics from the ESP + GA4** (clicks/replies/signups, not opens-as-vanity); **never fabricate.** - **Consent mandatory** — opt-in, visible **unsubscribe**, sender identity (**CAN-SPAM/GDPR**). **No bought lists / no-consent sends / misleading subjects / spam.** **Monetize honestly.** (Scope, distinctions + connections: `references/scope-and-connections.md`.) ## Distinct from its siblings (route correctly) **email-and-newsletter (this)** = the owned email channel + the email↔social loop · **link-in-bio-and-traffic** = the capture/handoff that drives signups in · **cross-platform-repurposing** = same-moment multi-platform · **content-recycling** = evergreen reuse over time · **lead-magnets-and-funnels** = the magnet design · **social-selling-and-dm** = the DM funnel. ## Where this connects Reads first: **brand-profile**, **voice-builder**, **content-pillars**. Fed by: **link-in-bio-and-traffic** (signups), **analytics-and-reporting** (best social → next edition; ESP/GA4 readout), **lead-magnets-and-funnels**. Repurpose engine: **cross-platform-repurposing**, **content-recycling**, **reels-script**/**ai-video**, **carousel-writer**, **caption-writer**/**hook-writer**, **linkedin-post-writer**. Discovery: **ai-search-optimization**/**social-seo**, **linkedin-growth**. Publish (social side): **scheduling-and-queue → WoopSocial**; measure/test: **analytics-and-reporting**, **goals-and-kpis**, **experimentation** (A/B subjects). ## Definition of done A focused niche (one problem/one reader) in the brand voice; an owned list grown via social capture (simple form + lead magnet, own domain/list) with a welcome sequence + high-value edition 2; both surfaces run off the same work (email habit + SEO/GEO-optimized web archive); editions at 70-20-10 with short subjects, scannable + interactive; the social↔email loop running both ways; metrics taken from the ESP + GA4 (clicks/replies/signups, not opens, nothing fabricated) with consent + unsubscribe; WoopSocial publishes only the social side (email send stays external); correctly distinguished from link-in-bio-and-traffic, cross-platform-repurposing, content-recycling, and lead-magnets-and-funnels.
© social-media-skills · MIT · social-media-skills/skills