newsletter-generation
Use this skill when the user requests to generate, create, write, or draft a newsletter, email digest, weekly roundup, industry briefing, or curated content summary. Supports topic-based research, content curation from multiple sources, and professional formatting for email or web distribution. Trig
By bytedance · 1,531 installs
npx skills add bytedance/deer-flow --skill newsletter-generation
Source repository · Upstream listing
Newsletter Generation Skill
Overview
This skill generates professional, well researched newsletters that combine curated content from multiple sources with original analysis and commentary. It follows modern newsletter best practices from publications like Morning Brew, The Hustle, TLDR, and Benedict Evans to produce content that is informative, engaging, and actionable.
The output is a complete, ready to publish newsletter in Markdown format, suitable for email distribution platforms, web publishing, or conversion to HTML.
Core Capabilities
Research and curate content from multiple web sources on specified topics
Generate topic focused or multi topic newsletters with consistent voice
Write engaging headlines, summaries, and original commentary
Structure content for optimal readability and scanning
Support multiple newsletter formats (daily digest, weekly roundup, deep dive, industry briefing)
Include relevant links, sources, and attributions
Adapt tone and style to target audience (technical, executive, general)
Generate recurring newsletter series with consistent branding and structure
When to Use This Skill
Always load this skill when:
User asks to generate a newsletter, email digest, or content roundup
User requests a curated summary of news or developments on a topic
User wants to create a recurring newsletter format
User asks to compile recent developments in a field into a briefing
User needs a formatted email ready content piece with multiple curated items
User asks for a "weekly roundup", "monthly digest", or "morning briefing"
Newsletter Workflow
Phase 1: Planning
Step 1.1: Understand Newsletter Requirements
Identify the key parameters:
Parameter Description Default
Topic(s) Primary subject area(s) to cover Required
Format Daily digest, weekly roundup, deep dive, or industry briefing Weekly roundup
Target Audience Technical, executive, general, or niche community General
Tone Professional, conversational, witty, or analytical Conversational professional
Length Short (5 min read), medium (10 min), long (15 min+) Medium
Sections Number and type of content sections 4 6 sections
Frequency Context One time or part of a recurring series One time
Step 1.2: Define Newsletter Structure
Based on the format, select the appropriate structure:
Daily Digest Structure :
Weekly Roundup Structure :
Deep Dive Structure :
Industry Briefing Structure :
Phase 2: Research & Curation
Step 2.1: Multi Source Research
Conduct thorough research using web search. The quality of the newsletter depends directly on the quality and recency of research.
Search Strategy :
IMPORTANT : Always check <current date to ensure search queries use the correct temporal context. Never use hardcoded years.
Step 2.2: Source Evaluation and Selection
Evaluate each source and curate the best content:
Criterion Priority
Recency Prefer content from the last 7 30 days
Authority Prioritize primary sources, official announcements, established publications
Uniqueness Select stories that offer fresh perspective or are underreported
Relevance Every item must clearly connect to the newsletter's stated topic(s)
Actionability Prefer content readers can act on (tools, insights, strategies)
Diversity Mix of news, analysis, data, and practical resources
Step 2.3: Deep Content Extraction
For key stories, use web fetch to read full articles and extract:
1. Core facts — What happened, who is involved, when
2. Context — Why this matters, background information
3. Data points — Specific numbers, metrics, or statistics
4. Quotes — Relevant expert quotes or official statements
5. Implications — What this means for the reader
Phase 3: Writing
Step 3.1: Newsletter Header
Every newsletter starts with a consistent header:
Step 3.2: Section Writing Guidelines
Top Stories / Featured Items :
Headline : Compelling, clear, benefit oriented (not clickbait)
Hook : Opening sentence that makes the reader care (1 2 sentences)
Body : Key facts and context (2 4 paragraphs)
Why it matters : Connect to the reader's world (1 paragraph)
Source link : Always attribute and link to the original source
Quick Bites / Brief Items :
Format : Bold headline + 2 3 sentence summary + source link
Focus : One key takeaway per item
Efficiency : Readers should get the essential insight without clicking through
Analysis / Commentary Sections :
Voice : The newsletter's unique perspective on trends or developments
Structure : Observation → Context → Implication → (Optional) Actionable takeaway
Evidence : Every claim backed by data or sourced information
Step 3.3: Writing Standards
Principle Implementation
Scannable Use headers, bold text, bullet points, and short paragraphs
Engaging Lead with the most interesting angle, not chronological order
Concise Every sentence earns its place — cut filler ruthlessly
Accurate Every fact is sourced, every number is verified
Attributive Always credit original sources with inline links
Human Write like a knowledgeable friend, not a press release
Tone Calibration by Audience :
Audience Tone Example
Technical Precise, no jargon explanations, assumed expertise "The new API supports gRPC streaming with backpressure handling via flow control windows."
Executive Impact focused, bottom line, strategic "This acquisition gives Company X a 40% market share in the enterprise segment, directly threatening Incumbent Y's pricing power."
General Accessible, analogies, explains concepts "Think of it like a universal translator for data — it lets any app talk to any database without learning a new language."
Phase 4: Assembly & Polish
Step 4.1: Assemble the Newsletter
Combine all sections into the final document following the chosen structure template.
Step 4.2: Footer
Every newsletter ends with:
Step 4.3: Quality Checklist
Before finalizing, verify:
[ ] Every factual claim has a source link — No unsourced assertions
[ ] All links are functional — Verified URLs from search results
[ ] Date references use the actual current date — No hardcoded or assumed dates
[ ] Content is current — All major items are from within the expected timeframe
[ ] No duplicate stories — Each item appears only once
[ ] Consistent formatting — Headers, bullets, links use the same style throughout
[ ] Balanced coverage — Not dominated by a single source or perspective
[ ] Appropriate length — Matches the specified length target
[ ] Engaging opening — The first 2 sentences make the reader want to continue
[ ] Clear closing — The newsletter ends with a memorable or actionable note
[ ] Proofread — No typos, broken formatting, or incomplete sentences
Newsletter Output Template
Adaptation Examples
Technology Newsletter
Emoji usage: ✅ Moderate (section headers)
Sections: Top Stories, Deep Dive, Quick Bites, Open Source Spotlight, Dev Tools
Tone: Technical conversational
Business/Finance Newsletter
Emoji usage: ❌ Minimal to none
Sections: Market Overview, Deal Flow, Company News, Data Corner, Outlook
Tone: Professional analytical
Industry Specific Newsletter
Emoji usage: Moderate
Sections: Regulatory Updates, Market Data, Innovation Watch, People Moves, Events
Tone: Expert authoritative
Creative/Marketing Newsletter
Emoji usage: ✅ Liberal
Sections: Campaign Spotlight, Trend Watch, Viral This Week, Tools We Love, Inspiration
Tone: Enthusiastic professional
Output Handling
After generation:
Save the newsletter to /mnt/user data/outputs/newsletter {topic} {date}.md
Present the newsletter to the user using the present files tool
Offer to adjust sections, tone, length, or focus areas
If the user wants HTML output, note that the Markdown can be converted using standard tools
Notes
This skill works best in combination with the deep research skill for comprehensive topic coverage — load both for newsletters requiring deep analysis
Always use <current date for temporal context in searches and date references in the newsletter
For recurring newsletters, suggest maintaining a consistent structure so readers develop expectations
When curating, quality beats quantity — 5 excellent items beat 15 mediocre ones
Attribute all content properly — newsletters build trust through transparent sourcing
Avoid summarizing paywalled content that the reader cannot access
If the user provides specific URLs or articles to include, incorporate them alongside your curated findings
The newsletter should provide enough value in the summaries that readers benefit even without clicking through to every link