Token导航 LogoToken导航TokenDH.com
研究检索需要联网github未标认证来源可访问许可证需确认审计提醒

newsletter-generation时事通讯的产生

Agent Skill

newsletter-generation 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

4,260

周安装

183

GitHub Stars

64,338

下载量

1,493
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:newsletter-generation(时事通讯的产生)
来源仓库:https://github.com/bytedance/deer-flow
仓库路径:skills/newsletter-generation
安装命令:
npx skills add https://github.com/bytedance/deer-flow --skill newsletter-generation
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/bytedance/deer-flow --skill newsletter-generation

简介

newsletter-generation 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。

  • 适用于新闻聚合、信息检索、内容筛选等研究检索类任务场景。
  • 通过 npx skills add 命令从指定 GitHub 仓库安装,需确认权限范围和联网需求。
  • 安装前建议核实维护状态、是否会触发命令执行或文件读写操作。
  • 可结合原始 README 文档进一步核验具体功能和使用方法。

SKILL.md

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

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

36.72%
按下载量换算548

Claude

27.89%
按下载量换算416

Cursor

20.21%
按下载量换算302

Gemini CLI

9.82%
按下载量换算147

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills