Skip to content
cccskills
FreePublished on GitHub

newsletter-generation

Generate or edit a source-grounded newsletter issue, digest, or briefing from provided or researched sources. Use for weekly/monthly updates, curated links, executive digests, community newsletters, or "turn these sources into a newsletter"; do not use for UI landing pages, marketing campaign design, unsourced news claims, or long-form research reports.

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md2.9 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Newsletter Generation

Purpose

Turn source material into a concise, useful newsletter that has a clear audience, editorial angle, attribution, and fact boundaries.

When to Use

Use for:

  • weekly/monthly newsletters, digest emails, link roundups, or executive briefings
  • summarizing a set of URLs, release notes, issues, papers, meeting notes, or user-provided bullets
  • creating an editorial structure: subject line, intro, sections, summaries, calls to action, and source list

Do not use for:

  • building the visual landing page or email UI; use frontend/design skills as appropriate
  • deep academic/systematic reviews; use systematic-literature-review
  • unsourced breaking-news claims or fake quotes
  • sending email, subscribing users, or managing mailing-list provider configuration

Workflow

  1. Identify audience, purpose, tone, cadence, length, and required sections.
  2. Inventory sources and mark their type: official update, primary document, issue/PR, paper, meeting note, user-provided note, or secondary article.
  3. Verify key facts against primary sources when practical. Do not turn weak evidence into confident news.
  4. Choose an editorial angle that explains why the issue matters to the audience.
  5. Synthesize related items into themes; avoid one bullet per source unless the user asked for a link list.
  6. Draft with concrete headlines, short summaries, clear attribution, and explicit calls to action.
  7. Include an Unverified / Needs follow-up section for claims, links, dates, or numbers not checked.

Quality Rules

  • No fabricated quotes, dates, metrics, product names, event details, sponsorships, or endorsements.
  • Use realistic copy, not filler text.
  • Distinguish editorial interpretation from source facts.
  • Keep source links visible unless the user requests a no-link internal memo.

Output Contract

STATUS: DRAFTED | PARTIAL | BLOCKED

AUDIENCE / GOAL:
- <who this is for and what action/understanding it should create>

ISSUE DRAFT:
- Subject:
- Preview:
- Intro:
- Sections:
- Closing / CTA:

SOURCES USED:
- <source> - <what it supports>

EDITORIAL NOTES:
- <tone, angle, cuts, or assumptions>

UNVERIFIED:
- <unchecked claim/source/date or N/A>

Provenance

Clean-room AILI/OpenCode adaptation inspired by the public DeerFlow newsletter-generation skill pattern. No upstream skill text, runtime paths, tools, generated assets, provider configuration, or mailing-service assumptions are copied. Source family: bytedance/deer-flow, MIT License.

Reviews

No reviews yet. Tell others what you thought.

Comments

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.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Review a single academic paper, preprint, DOI, arXiv link, or user-provided PDF/text with source-grounded critique. Use for paper summaries, methodology review, novelty checks, reproducibility concerns, or "review this paper" requests; do not use for multi-paper surveys, systematic literature reviews, citation management, or implementation from a paper.

The English summary is being prepared. Showing the original description.

Rosetears520/aili-workflows2Updated Sep 27, 2026

AI regression scouting routing. Use when agents, prompts, skills, model/tool routing, harness fixtures, or generated-output expectations change and need regression scenarios; do not use for ordinary product-code regressions.

The English summary is being prepared. Showing the original description.

Rosetears520/aili-workflows2Updated Sep 27, 2026

Run the AILI delivery lifecycle from natural-language IDEATE, DEFINE, BUILD, and SHIP intent or the equivalent slash shortcuts; use for idea shaping, spec/test definition, bounded BUILD package queues, review-repair closeout, or adapter routing without exposing internal stage commands.

The English summary is being prepared. Showing the original description.

Rosetears520/aili-workflows2Updated Sep 27, 2026

Android native Kotlin/Compose app development, Material 3 UI, accessibility, and Gradle builds.

The English summary is being prepared. Showing the original description.

Rosetears520/aili-workflows2Updated Sep 27, 2026

Guides stable API and interface design. Use when designing APIs, module boundaries, or any public interface. Use when creating REST or GraphQL endpoints, defining type contracts between modules, or establishing boundaries between frontend and backend.

The English summary is being prepared. Showing the original description.

Rosetears520/aili-workflows2Updated Sep 27, 2026

Route an explicitly requested independent/delegated browser QA assignment or durable E2E evidence need; do not trigger for direct Playwright/DOM/console/network inspection, ordinary UI implementation, backend-only work, or production-mutating flows.

The English summary is being prepared. Showing the original description.

Rosetears520/aili-workflows2Updated Sep 27, 2026

See all skills by Rosetears520

Report a problem with this skill