Newsletter Digest Brief Skill
Newsletters are individually reasonable and collectively unreadable — twelve arrivals a week, each 70% padding, each interrupting on its own schedule. The digest move: batch them (the inbox-unsubscribe-purge filter routes them to a label), then process the pile into one brief filtered by the reader's actual interests — items extracted with their source and why-it-matters, everything else dropped with a visible count so the reader trusts the filter instead of re-reading behind it.
What This Skill Produces
- The brief — the items that matter to this reader's stated interests: one line of what + one of so-what + the source link
- The dropped ledger — "skipped 31 items: 12 promos, 9 repeats of the X story, 10 off-interest" — the trust mechanism
- The repeat-collapse — one story covered by four newsletters appears once, best-source-first
- The cadence setting — weekly for most; daily only for genuinely fast-moving beats
Required Inputs
Ask for these if not provided:
- The pile — the newsletters' content (pasted/forwarded), or the label they collect under
- The interest profile — the beats that actually matter to this reader ("AI tooling, pricing strategy, my competitors, nothing about funding rounds") — the filter IS the product, and it needs edges
- The action bias — reading-for-awareness vs. hunting-for-actions; the brief leads with actionable items when the latter
Framework: The Digest Rules
- Filter by declared interest, ruthlessly: the brief includes what matches the profile and drops the rest — a digest that summarizes everything is the pile again, shorter. Edge cases get one "borderline" line at most, not inclusion.
- What + so-what + source, one item = two lines: "Vercel shipped edge-side A/B testing (what). Relevant: replaces the tool you're paying $400/mo for (so-what). [source]" — the so-what is written for this reader, which is what separates a digest from a table of contents.
- Collapse the echo: the same announcement in four newsletters is one item, attributed to the best treatment ("deepest take: X's issue"). The echo-count is itself signal ("covered everywhere = the week's consensus story") and gets a line when heavy.
- The dropped ledger builds the trust: the counted skip-list ("12 promos, 9 echoes, 10 off-interest") is what lets the reader not re-read the pile — a filter with invisible drops never earns retirement of the source reading.
- Cadence follows the beat's clock: weekly suits almost everything; daily digest is for beats where a day's lag costs (markets, security advisories). The cadence is chosen once and defended — an "urgent" exception lane exists only for the reader's pre-named topics.
Output Format
Digest: [period] — [N] sources, [M] items kept, [K] dropped
Actionable (if any)
[Items implying a move for this reader, first]
Worth Knowing
[Per item: what — so-what for you. ([best source])]
[Echo notes where heavy: "covered by 4 of your sources"]
Borderline (one-liners)
[…]
Dropped: [K]
[The counted categories — promos / echoes / off-interest]
Quality Checks
Anti-Patterns
1---2name: newsletter-digest-brief-23description: "Turn a pile of newsletters and subscriptions into one skimmable brief — the items that matter to YOUR interests extracted with sources, the noise dropped with a count, on a cadence that replaces daily trickle-reading. Use when asked digest my newsletters, summarize what my subscriptions said this week, what did I miss that I actually care about, or make my reading pile useful. Produces the interest-filtered brief with per-item sources, the dropped-with-reasons ledger, and the cadence that makes trickle-reading obsolete."4homepage: https://mohitagw15856.github.io/pm-claude-skills/skill/newsletter-digest-brief.html5metadata:6 source: https://skillmd.com/skills/mohitagw15856/newsletter-digest-brief-27 openclaw:8 emoji: 🧠9---1011# Newsletter Digest Brief Skill1213Newsletters are individually reasonable and collectively unreadable — twelve arrivals a week, each 70% padding, each interrupting on its own schedule. The digest move: batch them (the [inbox-unsubscribe-purge](../inbox-unsubscribe-purge/SKILL.md) filter routes them to a label), then process the pile into *one brief* filtered by the reader's actual interests — items extracted with their source and why-it-matters, everything else dropped with a visible count so the reader trusts the filter instead of re-reading behind it.1415## What This Skill Produces1617- **The brief** — the items that matter to this reader's stated interests: one line of what + one of so-what + the source link18- **The dropped ledger** — "skipped 31 items: 12 promos, 9 repeats of the X story, 10 off-interest" — the trust mechanism19- **The repeat-collapse** — one story covered by four newsletters appears once, best-source-first20- **The cadence setting** — weekly for most; daily only for genuinely fast-moving beats2122## Required Inputs2324Ask for these if not provided:25- **The pile** — the newsletters' content (pasted/forwarded), or the label they collect under26- **The interest profile** — the beats that actually matter to this reader ("AI tooling, pricing strategy, my competitors, nothing about funding rounds") — the filter IS the product, and it needs edges27- **The action bias** — reading-for-awareness vs. hunting-for-actions; the brief leads with actionable items when the latter2829## Framework: The Digest Rules30311. **Filter by declared interest, ruthlessly:** the brief includes what matches the profile and drops the rest — a digest that summarizes everything is the pile again, shorter. Edge cases get one "borderline" line at most, not inclusion.322. **What + so-what + source, one item = two lines:** "Vercel shipped edge-side A/B testing (what). Relevant: replaces the tool you're paying $400/mo for (so-what). [source]" — the so-what is written for *this reader*, which is what separates a digest from a table of contents.333. **Collapse the echo:** the same announcement in four newsletters is one item, attributed to the best treatment ("deepest take: X's issue"). The echo-count is itself signal ("covered everywhere = the week's consensus story") and gets a line when heavy.344. **The dropped ledger builds the trust:** the counted skip-list ("12 promos, 9 echoes, 10 off-interest") is what lets the reader *not* re-read the pile — a filter with invisible drops never earns retirement of the source reading.355. **Cadence follows the beat's clock:** weekly suits almost everything; daily digest is for beats where a day's lag costs (markets, security advisories). The cadence is chosen once and defended — an "urgent" exception lane exists only for the reader's pre-named topics.3637## Output Format3839# Digest: [period] — [N] sources, [M] items kept, [K] dropped4041## Actionable (if any)42[Items implying a move for this reader, first]4344## Worth Knowing45[Per item: **what** — so-what for you. ([best source])]46[Echo notes where heavy: "covered by 4 of your sources"]4748## Borderline (one-liners)49[…]5051## Dropped: [K]52[The counted categories — promos / echoes / off-interest]5354## Quality Checks5556- [ ] Every kept item has a reader-specific so-what, not a generic summary57- [ ] Repeats are collapsed with the best source named58- [ ] The dropped ledger is counted and categorized59- [ ] Actionable items lead when the reader's bias is action60- [ ] The interest profile's edges were honored — no scope creep toward "interesting generally"6162## Anti-Patterns6364- [ ] Do not summarize everything — an unfiltered digest is the pile with extra steps65- [ ] Do not write so-whats that would fit any reader — the profile is the point66- [ ] Do not hide the drops — invisible filtering keeps the reader re-reading the sources67- [ ] Do not let one loud newsletter dominate — items compete on interest-match, not sender volume68- [ ] Do not run daily by default — cadence inflation recreates the interruption problem the digest exists to solve