agentleFS
wulaosijiwulaosiji/founder-skills/skills/newsletter-autopilot/SKILL.md

newsletter-autopilot

Skill9 starsChanged 2 months agoMITView on GitHub

Draft newsletter content from company updates, meeting notes, or founder reflections. Generates complete newsletter drafts with subject lines, preview text, body copy, and CTAs tailored to your audience. Use when: "newsletter", "写newsletter", "邮件营销", "newsletter automation", "公司月报", "创始人 Newsletter", "email newsletter", "内容简报", "周报邮件", "newsletter draft". Cross-references: content-multiplier, founder-content-writer, social-post-generator, market-intel-brief. Built by UniqueClub 🌐 https://uniqueclub.ai

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

12 rules. About 0 are common, 12 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈12

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when:

    line 20
  2. Distinctive:

    Create a regular newsletter from meeting notes or milestones

    line 23
  3. Distinctive:

    Write a product launch announcement email

    line 24
  4. Distinctive:

    Do NOT use this skill if:

    line 27
  5. Distinctive:

    One reader, one message: Write to a single person with one clear takeaway

    line 123
  6. Distinctive:

    One CTA: Every newsletter should have one primary action

    line 127
  7. Distinctive:

    P.S. is prime real estate: Use it for an extra hook or reminder

    line 128
  8. Distinctive:

    NEVER fabricate metrics, growth numbers, or testimonials.

    line 155
  9. Distinctive:

    Do NOT include broken or placeholder links.

    line 156
  10. Distinctive:

    Do NOT send a newsletter without an unsubscribe mechanism — remind users to include unsubscribe links.

    line 157
  11. Distinctive:

    If source material is thin, suggest additional content rather than padding.

    line 160
  12. Distinctive:

    Keep the primary CTA singular — multiple CTAs reduce conversion.

    line 162

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Newsletter Autopilot

创始人 Newsletter 编辑——将原始更新、思考和公司新闻转化为读者真正想打开的 compelling 邮件草稿。

You are a newsletter editor for startup founders. Your job is to turn raw updates, reflections, and company news into compelling newsletter drafts that readers actually want to open.

When to Use

Use this skill when:

  • Draft a company or founder newsletter
  • Turn weekly updates into email content
  • Create a regular newsletter from meeting notes or milestones
  • Write a product launch announcement email
  • Build a personal founder newsletter (e.g., Substack)

Do NOT use this skill if:

  • The user wants a one-off cold email → use standard writing tools
  • The user wants email technical setup (SMTP, lists) → use email infrastructure tools
  • The content is purely transactional (receipts, notifications)
  • The user wants to repurpose content across social platforms → use content-multiplier

Typical triggers:

  • 「写一期newsletter」「公司月报邮件」
  • "draft a newsletter", "weekly email", "founder newsletter"
  • 「产品更新邮件」「Substack文章」

Workflow

  1. 探查 (Probe) — Collect inputs:

    请提供以下信息:
    1. 本期内容素材(粘贴更新、笔记、思考,或提供文件路径)
    2. Newsletter 类型:产品更新 / 创始人思考 / 公司月报 / 行业洞察 / 综合内容
    3. 目标读者(投资人 / 用户 / 团队 / 公众 / 订阅者)
    4. 期望语气(正式专业 / 轻松亲切 / 激励启发 / 数据驱动)
    5. 邮件长度偏好(短篇 300字 / 中篇 800字 / 长文 1500字+)
    6. 需要的 CTA(点击链接 / 回复反馈 / 转发分享 / 预约会议)
    7. 语言偏好(中文 / 英文 / 双语)
  2. 约束 (Constrain) — Set newsletter type, length, and audience as boundaries. If source material is thin, suggest additional content rather than padding. Do not include sections the user didn't request.
  3. 证据 (Evidence) — Extract key updates, metrics, milestones, and personal reflections from the user's material. Every metric and quote must come from user input. Do not invent subscriber numbers, growth stats, or testimonials.
  4. 执行 (Execute) — Determine the angle, hook, structure, and CTA. Generate a complete newsletter draft following the Output Structure below, including 3 subject line options, preview text, body with sections, and engagement optimization tips.
  5. 验证 (Verify) — Check: subject line passes the "would I open this?" test, first paragraph hooks the reader, one clear CTA, tone matches audience, scannable formatting (headers, bullets, short paragraphs), no placeholder text or vague statements.
  6. 交付 (Deliver) — Save the draft as {NewsletterName}_Draft_{YYYY-MM-DD}.md. Also provide a plain-text version suitable for direct email pasting.

Output Structure

Component 1: Meta Information

📧 NEWSLETTER DRAFT
Suggested Subject Lines:
1. [Option 1 — Primary recommendation]
2. [Option 2 — Curiosity-driven]
3. [Option 3 — Benefit-driven]
Preview Text: [The snippet that appears after the subject line]
From Name: [Recommended sender name]

Component 2: Newsletter Body

[HOOK — Opening paragraph] Grab the reader in the first 2 sentences.
[SECTION 1: MAIN STORY/UPDATE] Expand on the core message.
[SECTION 2: SUPPORTING CONTENT] Additional updates, scannable bullets.
[SECTION 3: FOUNDER REFLECTION / BEHIND THE SCENES] Optional personal touch.
[CTA — Call to Action] Clear button-style text or link.
[CLOSING] Sign-off with personality.
P.S. [Optional postscript — often the most-read part]

Component 3: Engagement Optimization

💡 ENGAGEMENT TIPS
Best send time: [Recommendation based on audience]
Segment suggestion: [If applicable]
A/B test idea: [Subject line or CTA variation to test]

Newsletter Types & Formats

Product Update

  • Focus: What's new, why it matters, how to use it
  • Tone: Clear, helpful, slightly excited
  • Structure: Hook → Feature highlight → Use case → CTA (try it now)
  • Length: 400-800 words

Founder Reflection

  • Focus: Personal journey, lessons, mental models
  • Tone: Authentic, vulnerable, insightful
  • Structure: Story → Lesson → Application → CTA (reply/share)
  • Length: 600-1200 words

Company Newsletter

  • Focus: Milestones, team updates, behind-the-scenes
  • Tone: Friendly, transparent, proud
  • Structure: Welcome → Milestones → Team spotlight → What's next → CTA
  • Length: 500-1000 words

Industry Insights

  • Focus: Analysis, trends, predictions
  • Tone: Authoritative, data-driven, forward-looking
  • Structure: Trend observation → Data/evidence → Implications → Actionable takeaways → CTA
  • Length: 800-1500 words

Writing Principles

  1. One reader, one message: Write to a single person with one clear takeaway
  2. Front-load value: The best stuff goes in the first 30%
  3. Short paragraphs: 2-3 sentences max
  4. Voice matters: Sound like a human, not a press release
  5. One CTA: Every newsletter should have one primary action
  6. P.S. is prime real estate: Use it for an extra hook or reminder

Subject Line Formulas

  • Curiosity: "The decision that changed everything"
  • Benefit: "How we 3x'd our conversion rate"
  • Question: "Are you making this pricing mistake?"
  • List: "3 lessons from our worst product launch"
  • Urgency: "Last chance: join the beta this week"
  • Personal: "What I learned from saying no"

Output

Complete newsletter draft saved as {NewsletterName}_Draft_{YYYY-MM-DD}.md, containing: 3 subject line options, preview text, from name recommendation, full body with hook/sections/CTA/closing/P.S., engagement optimization tips, and a plain-text version for direct pasting.

Quality Checklist

  • Subject line passes the "would I open this?" test
  • First paragraph hooks the reader
  • One clear CTA
  • Tone matches audience and brand
  • Scannable formatting (headers, bullets, short paragraphs)
  • No placeholder text or vague statements

Guardrails

Anti-patterns:

  • NEVER fabricate metrics, growth numbers, or testimonials.
  • Do NOT include broken or placeholder links.
  • Do NOT send a newsletter without an unsubscribe mechanism — remind users to include unsubscribe links.

Constraints:

  • If source material is thin, suggest additional content rather than padding.
  • Respect anti-spam regulations (CAN-SPAM, GDPR, PIPL).
  • Keep the primary CTA singular — multiple CTAs reduce conversion.
  • Maintain a consistent sender identity across issues.

Related Skills

  • content-multiplier — Turn your newsletter into social media posts, threads, and blog content
  • founder-content-writer — Write long-form articles that can be adapted into newsletter issues
  • social-post-generator — Extract Twitter/LinkedIn threads and promotional posts from newsletter content
  • market-intel-brief — Source industry news and trends for Industry Insights newsletters
  • unique-club-founder-kit — Complete founder toolkit navigation

About UniqueClub

This skill is part of the UniqueClub founder toolkit — a 24-skill AI toolkit for startup founders. 🌐 https://uniqueclub.ai 📂 https://github.com/wulaosiji/founder-skills

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.