Research a topic across multiple web sources and turn selected stories into a newsletter with summaries, commentary, and source links. Adapt the structure and tone for daily digests, weekly roundups, detailed features, or industry briefings.
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".
Run score Not tested
See how to installResearch a chosen topic across multiple web sources and turn the findings into a newsletter combining summaries with original commentary. The skill organizes major stories, trend analysis, short news items, tools, and reference material into a Markdown draft with source links. It supports daily digests, weekly roundups, focused deep dives, and industry reports. The tone and level of explanation are adjusted to suit the intended readers.
Use it when you regularly share developments in a field or need to organize several articles for an audience. You can choose a structure for an accessible general-interest summary or an executive briefing focused on implications. For recurring newsletters, it keeps the name and heading structure consistent across issues.
Research uses web search and web_fetch to retrieve article text. Output is Markdown; converting it to HTML requires a separate conversion tool. The skill follows a policy of avoiding summaries of material that readers cannot access, such as paywalled articles.
This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.
AI checked the SKILL.md for operations that need care and for setup requirements. The score comes only from actually running the skill (hands-on test).
Not counted in the score. Rated by AI (OpenAI Codex) as of Oct 21, 2026. Treat it as a guide and read the original before installing.
Review the instructions the agent will receive before you install.
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 newsletterNo reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Turn academic papers into structured reviews that explain findings, strengths, weaknesses, and research methods. Assess originality and supporting evidence, compare relevant literature, and provide specific improvement suggestions in a detailed review or brief summary.
Find Python input/output calls that may stall asynchronous backend work, then fix or guard each relevant path with runtime tests. Verify that tests fail when blocking behavior returns and pass after the fix is restored.
Create or update a SOUL.md file that defines an AI partner’s behavior through a guided conversation. Clarify communication style, autonomy, honesty, and expectations, then review a concise English profile before saving it with setup_agent.
Turn data into chart images by selecting a suitable format from 26 options. Visualize trends, comparisons, distributions, flows, or relationships, then receive the image URL and the complete settings used to generate it.
Send research and analysis tasks to a running DeerFlow instance through its HTTP API, an interface for exchanging requests. Retrieve responses, continue conversations, upload documents, and inspect available models, skills, agents, and service health.
Turn source code into project documentation, from a README with installation steps and examples to API references, architecture diagrams, developer guides, and changelogs. Match the scope and comment format to the project's size and programming language.