OverviewHistoryStatsSecurity
npx skills add ...
Documentation
SKILL.md
npx skills add bytedance/deer-flow --skill 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. Trigger on requests like "create a newsletter about X", "write a weekly digest", "generate a tech roundup", or "curate news about Y".
npx skills add bytedance/deer-flow --skill newsletter-generation
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.
Always load this skill when:
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 |
Based on the format, select the appropriate structure:
Daily Digest Structure:
Weekly Roundup Structure:
Deep-Dive Structure:
Industry Briefing Structure:
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.
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 |
For key stories, use web_fetch to read full articles and extract:
Every newsletter starts with a consistent header:
Top Stories / Featured Items:
Quick Bites / Brief Items:
Analysis / Commentary Sections:
| 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." |
Combine all sections into the final document following the chosen structure template.
Every newsletter ends with:
Before finalizing, verify:
After generation:
/mnt/user-data/outputs/newsletter-{topic}-{date}.mdpresent_files tooldeep-research skill for comprehensive topic coverage — load both for newsletters requiring deep analysis<current_date> for temporal context in searches and date references in the newsletter