Assembles researched topics into structured, publishable newsletter drafts with Substack-compatible formatting. Activates when the user wants to write, draft, or outline a newsletter, format content for Substack, or asks 'turn this research into a newsletter.' Covers the four-part structure (Hook, Main Content, Takeaways, CTA), link attribution, and visual rhythm.
From founder-osnpx claudepluginhub thecloudtips/founder-os --plugin founder-osThis skill uses the workspace's default tool permissions.
references/section-templates.mdDesigns and optimizes AI agent action spaces, tool definitions, observation formats, error recovery, and context for higher task completion rates.
Enables AI agents to execute x402 payments with per-task budgets, spending controls, and non-custodial wallets via MCP tools. Use when agents pay for APIs, services, or other agents.
Compares coding agents like Claude Code and Aider on custom YAML-defined codebase tasks using git worktrees, measuring pass rate, cost, time, and consistency.
Assemble researched topics into structured, publishable newsletter drafts with Substack-compatible formatting. Used by: /founder-os:newsletter:outline (structure planning), /founder-os:newsletter:draft (full draft generation), and /newsletter (end-to-end research-to-draft pipeline).
Transform raw research findings and topic clusters into a newsletter that a founder can review, lightly edit, and publish directly to Substack. The output must follow a consistent four-part structure (Hook, Main Content, Key Takeaways, CTA), use Substack-compatible Markdown, attribute all sources properly, and land within the 800-1500 word target. Use the output template at ${CLAUDE_PLUGIN_ROOT}/templates/newsletter-template.md as the formatting scaffold for every draft.
Produce every newsletter in this four-part structure. Each part serves a distinct reader purpose -- do not merge or reorder them.
Open with an attention-grabbing statement that establishes why this issue matters right now. Anchor the hook to a specific event, statistic, trend shift, or provocative question. Avoid generic greetings ("Welcome to this week's issue") and throat-clearing ("In this edition, we'll cover...").
Effective hook patterns:
Rules:
Each section covers one finding cluster from the research phase. Present sections in descending order of reader impact -- lead with the most actionable or surprising finding.
Per-section structure:
Section length: 150-300 words each. Aim for 3 sections in a shorter newsletter (800-1000 words) and 4-5 sections when the research supports it (1000-1500 words).
Rules:
Distill the newsletter into 3-5 actionable bullet points. Each takeaway must be a complete, standalone instruction -- not a summary of a section heading.
Rules:
Close with a single, clear ask. The CTA drives reader engagement beyond passive consumption.
CTA types:
Rules:
Write Markdown that renders correctly in Substack's editor. Substack supports a subset of Markdown with specific rendering behaviors.
| Element | Syntax | Substack Notes |
|---|---|---|
| Headings | ## H2 through #### H4 | Use H2 for section titles, H3 for subsections. Avoid H1 (Substack uses the post title as H1). |
| Bold | **text** | Renders correctly. |
| Italic | *text* | Renders correctly. |
| Links | [text](url) | Opens in new tab by default. |
| Images |  | Use full URLs. Substack re-hosts images on upload. |
| Blockquotes | > text | Renders as indented quote block. |
| Unordered lists | - item | Use - not * for consistency. |
| Ordered lists | 1. item | Renders correctly. |
| Horizontal rules | --- | Use between major sections as visual dividers. |
| Code blocks | Triple backticks | Renders in monospace. Use sparingly in newsletters. |
| Line breaks | Double newline | Single newlines are ignored. Always use blank lines between paragraphs. |
<div>, <span>, <table>) -- Substack strips most raw HTML.> > text) -- renders inconsistently.[^1]) -- not supported. Use inline links instead.| col |) -- Substack does not render Markdown tables in published posts. Convert tables to bold-label lists or use images for tabular data.- [ ]) -- not supported.--- horizontal rules between the Hook and Main Content, between each main section, before Key Takeaways, and before the CTA.Attribute sources where the claim appears. Use descriptive link text that tells the reader what they will find -- never use "click here" or bare URLs.
According to [Stripe's 2025 developer survey](url), 68% of startups now use usage-based pricing.The approach mirrors what [Basecamp documented in their Shape Up methodology](url).According to this article (url), the trend is growing.Source: [click here](url)Rules:
Append a "Sources" section at the bottom of every newsletter, below the CTA. List every referenced source with its title and URL. This serves readers who want to explore further and establishes credibility.
Format:
---
**Sources:**
- [Source Title](url) -- one-line description of what this source covers
- [Source Title](url) -- one-line description
Rules:
Target 800-1500 words for the full newsletter (Hook through CTA, excluding the Sources section).
| Newsletter Type | Word Target | Sections | Use When |
|---|---|---|---|
| Quick-hit | 800-1000 | 3 | Single theme, time-sensitive topic, or thin research |
| Standard | 1000-1300 | 4 | Most issues -- balanced depth and scannability |
| Deep-dive | 1300-1500 | 5 | Complex topic with rich research, or a tutorial-heavy issue |
Rules:
Connect sections so the newsletter reads as a cohesive narrative, not a list of unrelated findings.
Place a one-sentence bridge at the end of each section (before the --- divider) that links the current topic to the next section.
Patterns:
Rules:
--- divider signal the shift. Forced transitions are worse than no transition.Vary how each main content section opens to avoid rhythmic monotony:
Do not repeat the same opening pattern in consecutive sections.
Different newsletter issues call for different section types. Select the appropriate type for each section based on the research content. See ${CLAUDE_PLUGIN_ROOT}/skills/newsletter/newsletter-writing/references/section-templates.md for detailed templates, examples, and formatting guidance for each type.
Available section types:
Mix section types within a single newsletter for variety. A typical issue might combine one deep-dive, one news roundup, and one tool spotlight.
Before outputting a newsletter draft, confirm:
--- dividers separate all major sections${CLAUDE_PLUGIN_ROOT}/templates/newsletter-template.md