Source profileQuality 92/100

MoizIbnYousaf/marketing-cli/skills/newsletter/SKILL.md

newsletter

Design, write, and grow editorial newsletters with consistent voice and format. Creates newsletter strategy, templates, and growth playbook. Use when someone wants to start a newsletter, improve an existing one, grow subscribers, write a newsletter issue, plan newsletter content, or set up on Substack, Beehiiv, Ghost, or ConvertKit. Triggers on 'newsletter', 'editorial', 'weekly email', 'subscriber growth', 'newsletter template', 'email digest', 'Substack', 'Beehiiv', 'newsletter strategy', 'new

Source repository stars
27
Declared platforms
0
Static risk flags
0
Last source update
2026-07-28
Source checked
2026-07-28

Decision brief

What it does—and where it fits

You design and write editorial newsletters that people actually look forward to receiving. Not corporate updates nobody reads — opinionated, valuable, personality-driven emails that build an audience over time.

Best for

  • Use when someone wants to start a newsletter, improve an existing one, grow subscribers, write a newsletter issue, plan newsletter content, or set up on Substack, Beehiiv, Ghost, or ConvertKit.

Not for

  • Tasks that require unconfirmed production actions or broad system permissions.
  • Environments where the pinned source and install steps cannot be inspected.

Compatibility matrix

Platform support, with evidence labels

PlatformStatusEvidenceWhat to check
CodexNot declaredNo explicit evidencePortability before use
Claude CodeNot declaredNo explicit evidencePortability before use
CursorNot declaredNo explicit evidencePortability before use
Gemini CLINot declaredNo explicit evidencePortability before use
Open the compatibility checker

Installation

Inspect first. Install second.

The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

Source-detected install commandSource
npx skills add https://github.com/MoizIbnYousaf/marketing-cli --skill "skills/newsletter"
Safe inspection promptEditorial

Inspect the Agent Skill "newsletter" from https://github.com/MoizIbnYousaf/marketing-cli/blob/f12fbcbe4929584697b309b9096c9427b0cfce8e/skills/newsletter/SKILL.md at commit f12fbcbe4929584697b309b9096c9427b0cfce8e. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

Workflow

What the source asks the agent to do

  1. 01

    Step 1: Define the Newsletter

    Before writing a single issue, establish:

    Before writing a single issue, establish:
  2. 02

    Step 2: Build the Template

    Every newsletter needs a repeatable structure readers come to expect.

    Every newsletter needs a repeatable structure readers come to expect.
  3. 03

    Step 3: Write an Issue

    1. Choose the theme: One core topic per issue. No scatter. 2. Write the hook: First 2 sentences determine if they read or archive. Make it personal, specific, or surprising. 3. Deliver the value: The thing they subscribed for. Don't bury it. 4. Keep sections scannable: Bold key…

    Choose the theme: One core topic per issue. No scatter.Write the hook: First 2 sentences determine if they read or archive. Make it personal, specific, or surprising.Deliver the value: The thing they subscribed for. Don't bury it.
  4. 04

    The Writing Process

    1. Choose the theme: One core topic per issue. No scatter. 2. Write the hook: First 2 sentences determine if they read or archive. Make it personal, specific, or surprising. 3. Deliver the value: The thing they subscribed for. Don't bury it. 4. Keep sections scannable: Bold key…

    Choose the theme: One core topic per issue. No scatter.Write the hook: First 2 sentences determine if they read or archive. Make it personal, specific, or surprising.Deliver the value: The thing they subscribed for. Don't bury it.
  5. 05

    Step 4: Frequency Recommendations

    Default recommendation: Weekly. It's the sweet spot between staying top-of-mind and maintaining quality.

    Default recommendation: Weekly. It's the sweet spot between staying top-of-mind and maintaining quality.

Permission review

Static risk signals and limitations

No configured static risk pattern was detected

This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.

Evidence record

Why each signal appears

EvidenceSourceComputedTestedEditorial
SignalValueEvidence typeMeaning
Quality score92/100ComputedDocumentation, specificity, maintenance, and trust rules
Repository stars27SourceRepository attention, not individual Skill quality
Compatibility0 platformsSourceDeclared in the catalog source record
Usage guideautomated source guideEditorialGenerated or reviewed according to the visible evidence level

Pinned source

Provenance and original SKILL.md

Repository
MoizIbnYousaf/marketing-cli
Skill path
skills/newsletter/SKILL.md
Commit
f12fbcbe4929584697b309b9096c9427b0cfce8e
License
MIT
Collected
2026-07-28
Default branch
main
View the original SKILL.md

Newsletter System

You design and write editorial newsletters that people actually look forward to receiving. Not corporate updates nobody reads — opinionated, valuable, personality-driven emails that build an audience over time.

On Activation

  1. Read brand/voice-profile.md — newsletters live or die by voice consistency
  2. Read brand/audience.md — understand what they care about, how sophisticated they are
  3. If starting fresh, ask: What's the newsletter about? Who's it for? What format appeals to you?
  4. Check marketing/newsletter/ for existing strategy and past issues

Brand Integration

  • voice-profile.md → Newsletters live or die by voice consistency. If voice is warm/conversational, use 'I' perspective with personal anecdotes. If authoritative/editorial, use curated insights with expert framing. The voice must feel like a person writing, not a company broadcasting.
  • audience.md → Content selection and depth matches audience sophistication. Technical audience gets deep dives. General audience gets accessible summaries with links to learn more.

Step 1: Define the Newsletter

Newsletter Types

TypeDescriptionBest ForExample
CuratedBest links + your commentaryIndustry watchers, busy professionalsThe Hustle, TLDR
EditorialOriginal essays/insightsThought leaders, opinionated foundersStratechery, Lenny's Newsletter
HybridMix of original + curatedMost founders and creatorsMorning Brew, Dense Discovery
Product updateWhat's new in your productSaaS companies with active usersLinear, Notion changelogs
EducationalTeaches one skill per issueCourse creators, consultantsJames Clear, Marketing Examples

Strategy Doc

Before writing a single issue, establish:

---
name: "Newsletter Name"
tagline: "One-line value prop (what they get + how often)"
type: curated | editorial | hybrid | product | educational
frequency: weekly | biweekly | daily
send_day: Tuesday
send_time: "9:00 AM ET"
target_audience: "Who specifically reads this"
core_topic: "The single topic area"
voice: "How it sounds (reference voice-profile.md)"
success_metric: "Open rate > 40%, click rate > 5%"
---

Step 2: Build the Template

Every newsletter needs a repeatable structure readers come to expect.

Template Structure

# [Newsletter Name] — Issue #[N]

## [Catchy issue title or theme]

### Intro (2-3 sentences)
[Personal hook — what happened this week, what's on your mind, why this issue matters]

---

### Section 1: [Main Value Block]
[The core content — original insight, deep dive, or primary curation]

### Section 2: [Secondary Value]
[Supporting content, related links, or complementary angle]

### Section 3: [Quick Hits / Links]
- **[Link title]** — One-line commentary on why it matters
- **[Link title]** — One-line commentary
- **[Link title]** — One-line commentary

---

### [Recurring Section Name]
[Something predictable readers look forward to: tool of the week, quote, stat, hot take]

---

### CTA
[One primary ask: share, reply, check out product, visit link]

---

[Sign-off in your voice]
[Name]

[Footer: unsubscribe, share link, social links]

Format-Specific Templates

Curated Newsletter:

  • 5-7 links with 2-3 sentence commentary each
  • Group by theme or rank by importance
  • Your opinion is the value — don't just summarize

Editorial Newsletter:

  • One main essay (500-1,000 words)
  • Strong opening hook
  • Clear argument or insight
  • End with a question or call to reply

Hybrid Newsletter:

  • One short original piece (300-500 words)
  • 3-5 curated links with commentary
  • One recurring section (tool, quote, tip)

Step 3: Write an Issue

The Writing Process

  1. Choose the theme: One core topic per issue. No scatter.
  2. Write the hook: First 2 sentences determine if they read or archive. Make it personal, specific, or surprising.
  3. Deliver the value: The thing they subscribed for. Don't bury it.
  4. Keep sections scannable: Bold key phrases. Short paragraphs. Clear headers.
  5. Close with energy: A question, a challenge, a forward-looking tease.

Issue Output Format

---
issue_number: 42
title: "Issue title"
subject: "Email subject line"
preview: "Preview text"
theme: "Core topic"
send_date: 2026-03-12
word_count: 850
status: draft
---

Writing Rules

  • Personality first: Readers subscribe for your take, not the news itself
  • One idea per section: Don't cram. Each section has one job.
  • Scannable: Someone skimming should get 60% of the value. Bold key points.
  • Consistent length: Set an expectation and keep it. Plus or minus 20% variance max.
  • Predictable structure: Readers should know where to find what they want.
  • End with a question: The reply is the highest-engagement action. Invite it.

AI Tells to Avoid in Newsletters

Newsletters live or die on voice. Generic AI voice is fatal — readers unsubscribe from "content," they stay for a person.

Words to ban: delve, comprehensive, robust, utilize, landscape, navigate, foster, empower, elevate, streamline, crucial, leverage Phrases to ban: "In today's fast-paced world," "It's worth noting that," "Let's dive in," "Without further ado," "In conclusion" Structural tells: Every section same length. No personal anecdotes. No opinions without hedging. Perfect grammar everywhere (real newsletters have personality quirks). No contractions. The test: Read it aloud. If it sounds like a press release or a textbook, rewrite it. It should sound like a smart friend talking over coffee.


Step 4: Frequency Recommendations

FrequencyProsConsBest For
DailyHabit-forming, high engagementBurnout risk, high content demandNews, curation-heavy
WeeklySustainable, high quality per issueSlower growthMost creators and businesses
BiweeklyLow pressure, high qualityHarder to build habitIn-depth analysis, B2B
MonthlyMaximum qualityEasy to forget aboutReports, roundups

Default recommendation: Weekly. It's the sweet spot between staying top-of-mind and maintaining quality.


Step 5: Growth Assets (Agent-Actionable)

For each newsletter, generate these growth assets:

Signup Page Copy

Write a dedicated newsletter signup page with:

  • Headline: What they get + how often ("Weekly insights for founders building in public")
  • 3 bullet points: Specific value per issue
  • Social proof: Subscriber count, notable readers, or open rate stats
  • Single email field + subscribe button
  • "No spam. Unsubscribe anytime."

Welcome Email

Write the welcome email that triggers on signup:

  • Deliver on the promise (what to expect, when)
  • Ask for a reply ("What are you working on?") — boosts deliverability
  • Set the relationship tone from day one

Referral Copy

Write referral program copy with tiered rewards:

  • 1 referral: Bonus content (exclusive post, template, etc.)
  • 3 referrals: Free resource or community access
  • 10 referrals: Product discount or 1:1 consultation
  • Include the share CTA copy and referral email template

Cross-Promotion Outreach Template

Write a cross-promo pitch email for newsletters of similar size:

  • Introduce your newsletter (subscriber count, niche, open rate)
  • Propose mutual recommendation
  • Keep it short, genuine, no-strings

Social Teaser Copy

For each issue, generate 1-2 social posts that share a highlight and link to the archive/signup:

  • Pull the most surprising or valuable line from the issue
  • End with "Subscribe for more like this: [link]"

Growth Channel Reference

ChannelTacticExpected Conversion
WebsiteHomepage signup bar, exit intent popup, blog post CTAs1-3% of visitors
SocialPin newsletter link in bio, share issue highlights0.5-2% of followers
Cross-promoNewsletter swaps with similar-size newsletters50-200 subs per swap
Lead magnetFree resource into newsletter opt-in20-40% of landing page visitors
ReferralGive subscribers a referral link + incentive10-20% of new subs
ContentSEO articles with newsletter CTACompounding over time

Step 6: Engagement Metrics

MetricGoodGreatAction If Low
Open rate30-40%40-50%+Better subjects, clean list, check deliverability
Click rate2-4%5-8%+Better CTAs, more relevant links, clearer value
Reply rate1-2%3-5%+Ask better questions, be more personal
Unsubscribe<0.5%<0.2%Check frequency, relevance, expectations
Growth rate5-10%/mo10-20%/moAdd acquisition channels, improve lead magnets


Worked Example

Newsletter: "The Build Log" — Weekly hybrid newsletter for indie hackers

Subject Line Variants:

  1. "The feature that almost killed our conversion rate" (recommended)
  2. "Build Log #12: when metrics lie"
  3. "What I learned from a $0 week"

Preview Text: Plus 3 tools I switched to this month

Issue:

# The Build Log — Issue #12

## The feature that almost killed our conversion rate

Last week I shipped a "smart onboarding" flow. Took 3 days to build. Looked beautiful.

Conversion dropped 23%.

Turns out, users don't want smart. They want fast. The old flow was 2 steps. The new one was 5. Each step was better — but 5 steps is 5 chances to leave.

I reverted Thursday morning. Conversion recovered by Friday.

**The lesson:** Complexity is a tax. Every step you add needs to earn 10x what it costs in drop-off.

---

### 3 things worth your time

**[Why most MVPs are too big](link)** — This thread nails it. Your MVP should embarrass you, not impress your friends.

**[Indie Hackers revenue dashboard](link)** — New feature lets you see revenue benchmarks by category. I spent 30 minutes comparing and it was worth every second.

**[PostHog's session replay](link)** — Free tier is generous. Watching real users navigate your app is humbling and instructive.

---

### Tool I switched to

**Plausible Analytics** — Replaced Google Analytics. Lighter, privacy-friendly, and I actually look at the dashboard now because it's not overwhelming.

---

What's the last feature you shipped that backfired? Hit reply — I read everything.

— James

Output Structure

marketing/newsletter/
├── strategy.md                    # Newsletter definition and strategy
├── template.md                    # Repeatable issue template
├── growth-plan.md                 # Acquisition and referral strategy
└── issues/
    ├── 2026-03-12-issue-title.md  # Individual issues
    └── ...

Integration: Issues output in plain text format compatible with gws CLI for sending.

See references/archetype-templates.md for the detailed output presentation format (visual summary with subject line variants, send recommendations, files saved, and what's next sections).


References

  • newsletter-examples.md: Detailed breakdowns of 7 top newsletters (Lenny, Morning Brew, Ben's Bites, Sahil Bloom, Greg Isenberg, The Hustle, Rundown AI) with voice markers and sample structures
  • archetype-templates.md: 6 format templates, platform guidance (Beehiiv, Substack, Kit, Ghost), growth strategies, monetization frameworks, and output presentation format

Related Skills

  • brand-voice: Establish voice before writing
  • content-atomizer: Break newsletter issues into social posts
  • email-sequences: Automated sequences (welcome, etc.) complement the newsletter
  • lead-magnet: Create opt-in resources that feed the newsletter list
  • seo-content: Blog content that drives newsletter signups

Alternatives

Compare before choosing

Computed 1007

event4u-app/agent-config

design-intelligence

Grounded design brief from the adopted corpus — style, WCAG-checked color tokens, typography, layout pattern, anti-patterns. Use on ui-design-brief or any which-style/palette/font/chart decision.

Computed 9827

MoizIbnYousaf/marketing-cli

higgsfield-generate

Use when the user wants to generate an image or video via Higgsfield AI. Covers 30+ models: Soul V2, Seedance 2.0, Kling 3.0, Veo 3.1, GPT Image 2, Nano Banana 2. Also covers Marketing Studio — branded ad video/image with avatars and products. Use whenever: "generate an image", "make a video", "animate this photo", "image-to-video", "img2vid", "edit this image with AI", "produce a clip", "create an ad", "make a UGC video", "marketing video", "brand video", "TV spot", "import product from URL", "

Computed 9727

MoizIbnYousaf/marketing-cli

creative

Generate visual asset briefs, ad copy variants, AI image prompts, video scripts, and storyboards. Full creative production system with 5 specialized modes: product photos, product video, social graphics, talking heads, and ad creative. Make sure to use this skill whenever the user mentions any visual or creative marketing need — ad creative, image prompts, video scripts, thumbnails, banners, social graphics, product photography, storyboards, or marketing visuals of any kind. Even if they just sa

Computed 9542,015

coreyhaines31/marketingskills

site-architecture

When the user wants to plan, map, or restructure their website's page hierarchy, navigation, URL structure, or internal linking. Also use when the user mentions "sitemap," "site map," "visual sitemap," "site structure," "page hierarchy," "information architecture," "IA," "navigation design," "URL structure," "breadcrumbs," "internal linking strategy," "website planning," "what pages do I need," "how should I organize my site," or "site navigation." Use this whenever someone is planning what page