跳到主要内容

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".

在 GitHub 打开

安装方式

cp -r skills/public/newsletter-generation ~/.claude/skills/newsletter-generation

把该 skill 目录放进客户端 skills 目录。不同客户端的目录可能不同,Claude Code 默认是 ~/.claude/skills/

整仓一次性获取:git clone --depth 1 https://github.com/bytedance/deer-flow.git

依赖与权限

  • 无需 API Key
  • 无需联网
  • 依赖外部命令:make brew
  • 以上为按正文与 frontmatter 自动推断的信号,仅供参考;安装前建议先阅读原文。
触发场景
createwritedraft a newsletteremail digestweekly

SKILL.md 正文

来源 bytedance/deer-flow@b346b17 · 许可 MIT · 内容未修改

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:

ParameterDescriptionDefault
Topic(s)Primary subject area(s) to coverRequired
FormatDaily digest, weekly roundup, deep-dive, or industry briefingWeekly roundup
Target AudienceTechnical, executive, general, or niche communityGeneral
ToneProfessional, conversational, witty, or analyticalConversational-professional
LengthShort (5-min read), medium (10-min), long (15-min+)Medium
SectionsNumber and type of content sections4-6 sections
Frequency ContextOne-time or part of a recurring seriesOne-time

Step 1.2: Define Newsletter Structure

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

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:

# 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.

Step 2.2: Source Evaluation and Selection

Evaluate each source and curate the best content:

CriterionPriority
RecencyPrefer content from the last 7-30 days
AuthorityPrioritize primary sources, official announcements, established publications
UniquenessSelect stories that offer fresh perspective or are underreported
RelevanceEvery item must clearly connect to the newsletter's stated topic(s)
ActionabilityPrefer content readers can act on (tools, insights, strategies)
DiversityMix 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:

# [Newsletter Name]

*[Tagline or description] — [Date]*

---

[Optional: One-sentence preview of what's inside]

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

PrincipleImplementation
ScannableUse headers, bold text, bullet points, and short paragraphs
EngagingLead with the most interesting angle, not chronological order
ConciseEvery sentence earns its place — cut filler ruthlessly
AccurateEvery fact is sourced, every number is verified
AttributiveAlways credit original sources with inline links
HumanWrite like a knowledgeable friend, not a press release

Tone Calibration by Audience:

AudienceToneExample
TechnicalPrecise, no jargon explanations, assumed expertise"The new API supports gRPC streaming with backpressure handling via flow control windows."
ExecutiveImpact-focused, bottom-line, strategic"This acquisition gives Company X a 40% market share in the enterprise segment, directly threatening Incumbent Y's pricing power."
GeneralAccessible, 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:

---

*[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.*

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

# [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.*

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

质量与来源

所属仓库
bytedance/deer-flow
仓库星标
8.4 万
最近更新
今天
采集时间
今天
commit
b346b17fce89
内容指纹
sha256:cc66adb99053a78
文件路径
skills/public/newsletter-generation/SKILL.md

同仓库其它 Skill

查看全部 32 个
blocking-io-guard
Ensure async-path backend code that could block the asyncio event loop is protected by a teeth-verified runtime anchor in tests/blocking_io/. Use when changing backend Python under app/, packages/harness/deerflow/, or scripts/, when running a blocking-IO triage round over the whole repo, or when a reviewer/CI asks for blocking-IO coverage. Runs a deterministic scan (changed-lines or full-repo), routes each candidate, drafts/extends an anchor, and proves it fails when the blocking IO regresses.
精选 bytedance/deer-flow 8.4 万 原文
Codex CLIMCP 客户端
deerflow-maintainer-orchestrator
Use when a DeerFlow maintainer needs comment-only GitHub issue or PR handling: resolve issue/PR scopes with gh, analyze issues, post or draft issue comments, perform PR review comments, review PR or issue batches, compare competing PRs that target the same issue, give fix strategy, risk classification, and validation guidance. Intended for maintainers and trusted local agents, not general contributors.
精选 bytedance/deer-flow 8.4 万 原文
Codex CLIMCP 客户端
engineer-system-change
Evaluate and carry out non-trivial software-system changes from first principles. Use when assessing RFCs, issues, designs, features, refactors, migrations, dependency changes, or proposed fields, events, APIs, modules, and services whose need, consumers, system fit, validation, or rollback require scrutiny. Read the actual system, identify the concrete problem and named semantic consumers, choose the smallest sufficient solution, reject pseudo-requirements and speculative abstractions, and require evidence proportional to risk. Do not use for mechanical edits, source-code explanation, or a dedicated review of an already-complete diff.
精选 bytedance/deer-flow 8.4 万 原文
Codex CLIMCP 客户端
smoke-test
End-to-end smoke test skill for DeerFlow. Guides through: 1) Pulling latest code, 2) Docker OR Local installation and deployment (user preference, default to Local if Docker network issues), 3) Service availability verification, 4) Health check, 5) Final test report. Use when the user says "run smoke test", "smoke test deployment", "verify installation", "test service availability", "end-to-end test", or similar.
精选 bytedance/deer-flow 8.4 万 原文
Codex CLIMCP 客户端
academic-paper-review
Use this skill when the user requests to review, analyze, critique, or summarize academic papers, research articles, preprints, or scientific publications. Supports comprehensive structured reviews covering methodology assessment, contribution evaluation, literature positioning, and constructive feedback generation. Trigger on queries involving paper URLs, uploaded PDFs, arXiv links, or requests like "review this paper", "analyze this research", "summarize this study", or "write a peer review".
精选 bytedance/deer-flow 8.4 万 原文
Codex CLIMCP 客户端
bootstrap
Generate a personalized SOUL.md through a warm, adaptive onboarding conversation. Trigger when the user wants to create, set up, or initialize their AI partner's identity — e.g., "create my SOUL.md", "bootstrap my agent", "set up my AI partner", "define who you are", "let's do onboarding", "personalize this AI", "make you mine", or when a SOUL.md is missing. Also trigger for updates: "update my SOUL.md", "change my AI's personality", "tweak the soul".
精选 bytedance/deer-flow 8.4 万 原文
Codex CLIMCP 客户端

相似 Skill

更多「研究」
last30days
Research what people actually say about any topic in the last 30 days. Pulls posts and engagement from Reddit, X, YouTube, TikTok, Hacker News, Polymarket, GitHub, and the web. Includes a doctor health check to diagnose broken or missing sources.
精选 mvanhorn/last30days-skill 6.4 万 原文
Claude CodeCodex CLIMCP 客户端
agent-reach
MUST USE when user wants to 调研/research/搜索/search/查/找/look up anything on the internet — e.g. 全网调研 X / 帮我调研一下 X / 查一下 X / 搜搜 X / 看看大家怎么评价 X / X 上有什么讨论 / research this topic。 Also MUST USE when user mentions any platform or shares any URL/链接: 小红书/xiaohongshu/xhs, Twitter/推特/X, B站/bilibili, Reddit, Facebook, Instagram, V2EX, LinkedIn/领英/Boss直聘/招聘/求职/jobs, YouTube, GitHub code search, 小宇宙播客, 雪球/股票行情, RSS feeds, or any web URL. 16 platforms, multi-backend routing (OpenCLI / per-platform CLIs / APIs). Zero config for 6 channels. Run `agent-reach doctor --json` to see which backend serves each platform right now. NOT for: 写报告/数据分析/翻译等内容加工(本 skill 只负责从互联网获取内容); 发帖/评论/点赞等写操作;已有专门 skill 的平台(先用专门 skill)。 【路由方式】SKILL.md 包含路由表和常用命令,复杂场景需按需阅读对应分类的 references/*.md。 分类:search / social (小红书/推特/B站/V2EX/Reddit/Facebook/Instagram) / career(LinkedIn/Boss直聘) / dev(github) / web(网页/文章/RSS) / video(YouTube/B站/播客) / finance(雪球/股票)。
精选 Panniantong/Agent-Reach 9.6 万 原文
Claude CodeCursorMCP 客户端
academic-paper-reviewer
Multi-perspective academic paper review with dynamic reviewer personas. Runs a 5-seat, role-separated review panel (Journal-Fit Reviewer + 3 peer-review roles + Devil's Advocate) with field-specific expertise; role separation is not a claim of independent error processes. Supports full review, re-review (verification), quick assessment, methodology focus, Socratic guided, and calibration modes. Triggers on: review paper, peer review, manuscript review, referee report, review my paper, critique paper, simulate review, editorial review, calibrate reviewer, reviewer calibration, measure reviewer accuracy, 審查論文, 論文審查, 模擬審查, 同儕審查, 幫我審這篇, 以審查人角度評估, 審查者校準, 논문 심사, 동료 심사, 모의 심사, 심사자 관점에서 평가, 심사자 보정, revisar artículo, revisión entre pares, revisión de manuscrito, informe de árbitro, revisa mi artículo, criticar artículo, simular revisión, revisión editorial, calibrar revisor.
精选 Imbad0202/academic-research-skills 5.2 万 原文
Claude Code
academic-paper
12-agent academic paper writing pipeline. 11 modes (full/plan/outline/revision/revision-coach/abstract/lit-review/format-convert/citation-check/disclosure/rebuttal-audit). 6 paper types, 5 citation formats, bilingual abstracts, LaTeX/DOCX-via-Pandoc/PDF output. Style Calibration + Writing Quality Check + Anti-Patterns with IRON RULE markers. Triggers: write paper, academic paper, guide my paper, parse reviews, I got reviewer comments, revision roadmap, should we push back, conference rebuttal, grant panel response, audit my rebuttal, check my response draft, AI disclosure, check citations, citation check, check my references, verify references, look over the refs, 寫論文, 學術論文, 引導我寫論文, 審查意見, 我收到審查意見, 修訂路線圖, 評估回覆, 檢查引用, 引用檢查, 檢查參考文獻, 核對文獻, 논문 작성, 초록 작성, 논문 수정, 논문 계획을 도와줘, 심사 의견을 받았어, 심사 의견 반영, 답변서 점검, AI 사용 고지, 인용 확인, 인용 형식 검사, enmendar mi artículo, redactar artículo, guía mi artículo, analizar reseñas, auditar mi respuesta, verificar borrador de respuesta, verificar citas, divulgación de IA.
精选 Imbad0202/academic-research-skills 5.2 万 原文
Claude Code
academic-pipeline
Orchestrator for the full academic research pipeline: research -> write -> integrity check -> review -> revise -> re-review -> re-revise -> final integrity check -> finalize. Coordinates deep-research, academic-paper, and academic-paper-reviewer into a seamless 10-stage workflow with mandatory, coverage-bounded integrity checks, two-stage peer review, and auditable quality-assurance artifacts. Triggers on: academic pipeline, research to paper, full paper workflow, paper pipeline, end-to-end paper, research-to-publication, complete paper workflow, 연구부터 논문까지, 연구 주제 설정부터 논문 완성까지, 논문 전체 워크플로, flujo de trabajo académico, investigación a artículo, flujo completo de artículo, pipeline de investigación completa, publicación de investigación, flujo de trabajo completo del artículo.
精选 Imbad0202/academic-research-skills 5.2 万 原文
Claude Code
deep-research
Universal deep research agent team. 13-agent pipeline for rigorous academic research on any topic. 8 modes: full research, quick brief, paper review, lit-review, fact-check, three-way literature scan, Socratic guided research dialogue, and systematic review with optional meta-analysis. Covers research question formulation, Socratic mentoring, methodology design, systematic literature search, source verification, cross-source synthesis, risk of bias assessment, meta-analysis, APA 7.0 report compilation, editorial review, devil's advocate challenges, ethics review, and post-research literature monitoring. Triggers on: research, deep research, literature review, systematic review, meta-analysis, PRISMA, evidence synthesis, fact-check, WHY HOW WHAT papers, 3W literature scan, guide my research, help me think through, 研究, 深度研究, 文獻回顧, 文獻探討, 系統性回顧, 後設分析, 事實查核, 三段式文獻掃描, 引導我的研究, 幫我釐清, 幫我想想, 我不確定要研究什麼, 研究方向, 研究主題, 심층 연구, 문헌 조사, 체계적 문헌고찰, 메타분석, 사실 확인, 연구 방향을 잡아줘, 연구 주제 정하는 것을 도와줘, revisión de literatura, metaanálisis
精选 Imbad0202/academic-research-skills 5.2 万 原文
Claude Code