newsletter-growth

Generate story-first editorial newsletter issues with growth plans and automated audit validation.

1|Updated Aug 7, 2026
One-click install
npx skills add https://github.com/Deepak-ai-93/deepak-skill --skill newsletter-growth-deepak-ai-93
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: newsletter-growth
Source: https://github.com/Deepak-ai-93/deepak-skill/tree/main/skills/newsletter-growth
Command: npx skills add https://github.com/Deepak-ai-93/deepak-skill --skill newsletter-growth-deepak-ai-93

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Writing a newsletter issue that subscribers actually open, read to the bottom, and forward is hard — most issues bury the story, stack multiple CTAs, and ship without any growth plan. This Skill turns a weekly idea into a validated, ready-to-send editorial newsletter pack with the growth engine built in. ## Core Features & Use Cases - Story-first issue writer: issue-writer.mjs assembles an issue from a plan JSON — subject line (≤60 chars, one proven formula), open loop → rising stakes → payoff, value receipts, ONE CTA, ONE growth plug — and exits 1 on any validation failure. - Growth plan generation: ships growth-plan.md covering the 5-email welcome sequence, referral loop, cross-promos, and a day-7/14/30 analytics review. - Two-stage audit harness: audit-newsletter.mjs runs automated checks (subject length, story spine, anti-fluff blocklist, word window 350–900, specificity) then a fresh newsletter-auditor subagent scores issue worthiness /50 and signs PASS or FIX NEEDED before send. - Use Case: A SaaS founder needs this week's Beehiiv issue. Provide the topic, audience, voice, and one CTA; receive issue.md, growth-plan.md, and a signed newsletter-audit.md ready to paste into the ESP. ## Quick Start Ask the agent to write this week's story-first newsletter issue about your chosen topic with one CTA, then run the audit harness before sending.

Frequently Asked Questions about newsletter-growth

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a newsletter issue that gets opened and forwarded?

Start with a subject line under 60 characters using one proven formula (curiosity, number, how-to, pain, or story), open the issue with a hook that creates an unresolved question, raise stakes through the middle, pay off the loop, then close with exactly one CTA and one referral ask.

How do I grow a Beehiiv or Substack newsletter?

Combine a 5-email welcome sequence, a one-line referral plug in every issue, monthly cross-promo swaps with same-audience newsletters, and repurposing each issue into social posts. Review open, click, reply, and unsubscribe metrics every 7 days for the first month.

What is the difference between newsletter-growth and email-marketing skills?

newsletter-growth handles editorial content and audience growth — story-first issues, welcome sequences, and referral loops. email-marketing builds transactional ESP campaigns. They complement each other rather than overlap.

Why does issue-writer.mjs exit with code 1?

The script exits 1 when the plan JSON fails validation: missing subject formula, subject over 60 characters, incomplete story spine (hook, conflict, payoff), fewer than 2 value items, missing CTA or growth plug, or fluff words detected. Fix the plan and re-run.

What does the newsletter audit check before sending?

audit-newsletter.mjs verifies subject length and formula, story-spine sections, at least 2 value bullets, one CTA plus one growth plug, a 350–900 word window, an anti-fluff blocklist, and numeric specificity. A fresh auditor subagent then scores worthiness out of 50, with 35 or higher required to pass.