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".
What this skill does
# 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: | 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 | #### 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: | 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 | #### 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: ```markdown # [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 | 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." | ### 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: ```markdown --- *[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
Related in Productivity
gitea-workflow
IncludedOrchestrate agile development workflows for Gitea repositories using the tea CLI. Use when working with Gitea-hosted repos and asking to 'run the workflow', 'continue working', 'what's next', 'complete the task cycle', 'start my day', 'end the sprint', 'implement the next task', or wanting guided step-by-step development assistance. Keywords: workflow, orchestrate, agile, task cycle, sprint, daily, implement, review, PR, standup, retrospective, gitea, tea.
microsoft-graph-gateway
IncludedRoute Microsoft Graph work in this workspace. Use when users want to read or write Outlook mail, calendar events, contacts, OneDrive or SharePoint files, Teams, Planner, To Do, users, groups, directory data, or arbitrary Microsoft Graph endpoints from VS Code. Prefer WorkIQ for common read scenarios. Use Microsoft Graph for write actions and gap-read scenarios that need exact Graph properties, filters, permissions, or endpoints.
copilotkit
IncludedUse when building with CopilotKit — setup, development, integrations, debugging, upgrading, or contributing. Routes to the appropriate specialized skill based on the task.
wordly-wisdom
IncludedProvides calibrated decision analysis using Charlie Munger-style multiple mental models, inversion, incentive mapping, circle-of-competence checks, misjudgment audits, second-order effects, and forecast updates. Use when the user asks for an oracle take, a hard call, a decision memo, a premortem, an outside view, a red-team, a sanity-check, what am I missing, think this through, or wants a strategy, hire, investment, plan, product, partnership, or major life choice analysed. Avoid for simple factual lookups or time-sensitive legal, medical, or market questions without fresh evidence.
swain-session
IncludedSession management and project status dashboard. Owns the full session lifecycle (start/work/close/resume), focus lane, bookmarks, worktree detection, and tab naming. Also serves as the project status dashboard — shows active epics, progress, actionable next steps, blocked items, tasks, GitHub issues, and recommendations. Worktree creation is deferred to swain-do task dispatch (SPEC-195). Triggers on: 'session', 'status', 'what's next', 'dashboard', 'overview', 'where are we', 'what should I work on', 'show me priorities', 'bookmark', 'focus on', 'session info'.
gandi
IncludedComprehensive Gandi domain registrar integration for domain and DNS management. Register and manage domains, create/update/delete DNS records (A, AAAA, CNAME, MX, TXT, SRV, and more), configure email forwarding and aliases, check SSL certificate status, create DNS snapshots for safe rollback, bulk update zone files, and monitor domain expiration. Supports multi-domain management, zone file import/export, and automated DNS backups. Includes both read-only and destructive operations with safety controls.