Best for
- 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
bytedance/deer-flow/skills/public/newsletter-generation/SKILL.md
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".
Decision brief
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".
Compatibility matrix
| Platform | Status | Evidence | What to check |
|---|---|---|---|
| Codex | Not declared | No explicit evidence | Portability before use |
| Claude Code | Not declared | No explicit evidence | Portability before use |
| Cursor | Not declared | No explicit evidence | Portability before use |
| Gemini CLI | Not declared | No explicit evidence | Portability before use |
Installation
The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.
npx skills add https://github.com/bytedance/deer-flow --skill "skills/public/newsletter-generation"Inspect the Agent Skill "newsletter-generation" from https://github.com/bytedance/deer-flow/blob/bec6277930d6ee73c58156689f1556780724e35d/skills/public/newsletter-generation/SKILL.md at commit bec6277930d6ee73c58156689f1556780724e35d. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.
Workflow
Identify the key parameters:
Identify the key parameters:
Identify the key parameters:
Based on the format, select the appropriate structure:
Conduct thorough research using web search. The quality of the newsletter depends directly on the quality and recency of research.
Permission review
No configured static risk pattern was detected
This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.
Evidence record
| Signal | Value | Evidence type | Meaning |
|---|---|---|---|
| Quality score | 86/100 | Computed | Documentation, specificity, maintenance, and trust rules |
| Repository stars | 79,261 | Source | Repository attention, not individual Skill quality |
| Compatibility | 0 platforms | Source | Declared in the catalog source record |
| Usage guide | automated source guide | Editorial | Generated or reviewed according to the visible evidence level |
Pinned source
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:
1. Top Story (1 item, detailed)
2. Quick Hits (3-5 items, brief)
3. One Stat / Quote of the Day
4. What to Watch
Weekly Roundup Structure:
1. Editor's Note / Intro
2. Top Stories (2-3 items, detailed)
3. Trends & Analysis (1-2 items, original commentary)
4. Quick Bites (4-6 items, brief summaries)
5. Tools & Resources (2-3 items)
6. One More Thing / Closing
Deep-Dive Structure:
1. Introduction & Context
2. Background / Why It Matters
3. Key Developments (detailed analysis)
4. Expert Perspectives
5. What's Next / Implications
6. Further Reading
Industry Briefing Structure:
1. Executive Summary
2. Market Developments
3. Company News & Moves
4. Product & Technology Updates
5. Regulatory & Policy Changes
6. Data & Metrics
7. Outlook
Conduct thorough research using web search. The quality of the newsletter depends directly on the quality and recency of research.
Search Strategy:
# Current news and developments
"[topic] news [current month] [current year]"
"[topic] latest developments"
"[topic] announcement this week"
# Trends and analysis
"[topic] trends [current year]"
"[topic] analysis expert opinion"
"[topic] industry report"
# Data and statistics
"[topic] statistics [current year]"
"[topic] market data latest"
"[topic] growth metrics"
# Tools and resources
"[topic] new tools [current year]"
"[topic] open source release"
"best [topic] resources [current year]"
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:
# [Newsletter Name]
*[Tagline or description] — [Date]*
---
[Optional: One-sentence preview of what's inside]
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:
---
*[Newsletter Name] is [description of what it is].*
*[How to subscribe/share/give feedback]*
*Sources: All links are provided inline. This newsletter curates and summarizes
publicly available information with original commentary.*
Before finalizing, verify:
# [Newsletter Name]
*[Tagline] — [Full date, e.g., April 4, 2026]*
---
[Preview sentence: "This week: [topic 1], [topic 2], and [topic 3]."]
## 🔥 Top Stories
### [Headline 1]
[Hook — why this matters in 1-2 sentences.]
[Body — 2-4 paragraphs covering key facts, context, and implications.]
**Why it matters:** [1 paragraph connecting to reader's interests or industry impact.]
📎 [Source: Publication Name](URL)
### [Headline 2]
[Same structure as above]
## 📊 Trends & Analysis
### [Trend Title]
[Original commentary on an emerging trend, backed by data from research.]
[Key data points presented clearly — consider inline stats or a brief comparison.]
**The bottom line:** [One-sentence takeaway.]
## ⚡ Quick Bites
- **[Headline]** — [2-3 sentence summary with key takeaway.] [Source](URL)
- **[Headline]** — [2-3 sentence summary.] [Source](URL)
- **[Headline]** — [2-3 sentence summary.] [Source](URL)
- **[Headline]** — [2-3 sentence summary.] [Source](URL)
## 🛠️ Tools & Resources
- **[Tool/Resource Name]** — [What it does and why it's useful.] [Link](URL)
- **[Tool/Resource Name]** — [Description.] [Link](URL)
## 💬 One More Thing
[Closing thought, insightful quote, or forward-looking statement.]
---
*[Newsletter Name] curates the most important [topic] news and analysis.*
*Found this useful? Share it with a colleague.*
*All sources are linked inline. Views and commentary are original.*
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 newsletterAlternatives
alirezarezvani/claude-skills
App Store Optimization (ASO) toolkit for researching keywords, analyzing competitor rankings, generating metadata suggestions, and improving app visibility on Apple App Store and Google Play Store. Use when the user asks about ASO, app store rankings, app metadata, app titles and descriptions, app store listings, app visibility, or mobile app marketing on iOS or Android. Supports keyword research and scoring, competitor keyword analysis, metadata optimization, A/B test planning, launch checklist
wanshuiyin/Auto-claude-code-research-in-sleep
Use it for operations and research tasks; the detail page covers purpose, installation, and practical steps.
K-Dense-AI/scientific-agent-skills
Distributed computing for larger-than-RAM pandas/NumPy workflows. Use when you need to scale existing pandas/NumPy code beyond memory or across clusters. Best for parallel file processing, distributed ML, integration with existing pandas code. For out-of-core analytics on single machine use vaex; for in-memory speed use polars.
K-Dense-AI/scientific-agent-skills
Use NeuroKit2 to build or audit reproducible research workflows for physiological time-series preprocessing, event/interval analysis, multimodal alignment, variability, and complexity. Trigger when code imports neurokit2 or needs its current APIs, schemas, and method-aware validation—not for diagnosis or device validation.