
Rss Digest
- 191 installs
- 14 repo stars
- Updated February 14, 2026
- odysseus0/feed
Aggregate RSS feeds into concise digests so you can scan industry news, competitor updates, and blog changes without opening every source manually each day.
About
rss-digest from odysseus0/feed automates collecting and summarizing RSS feeds into readable digests for research, competitive tracking, and content planning without manually visiting each source.
- Parses multiple RSS/Atom feeds into one digest
- Summarizes noisy streams into skimmable updates
- Supports competitive and industry monitoring
- Fits daily research and content curation loops
- Reduces manual feed-checking overhead
Rss Digest by the numbers
- 191 all-time installs (skills.sh)
- +1 installs in the week ending Jul 26, 2026 (Skillselion tracking)
- Ranked #604 of 2,719 Automation & Workflows skills by installs in the Skillselion catalog
- Data as of Aug 3, 2026 (Skillselion catalog sync)
npx skills add https://github.com/odysseus0/feed --skill rss-digestAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 191 |
|---|---|
| repo stars | ★ 14 |
| Last updated | February 14, 2026 |
| Repository | odysseus0/feed ↗ |
What it does
Aggregate RSS feeds into concise digests so you can scan industry news, competitor updates, and blog changes without opening every source manually each day.
Files
RSS Digest
Surface what's worth reading from RSS feeds. Requires feed CLI (brew install odysseus0/tap/feed).
Workflow
1. Scan — feed get entries --limit 50 for recent unread (title, feed, date, URL, summary). Auto-fetches if stale. If 0 results, run feed get stats — if 0 feeds, import starter set: feed import https://github.com/odysseus0/feed/raw/main/hn-popular-blogs-2025.opml and retry. 3. Triage — Pick 5-10 high-signal posts based on the user's prompt. If no specific interest given, prioritize surprising, contrarian, or unusually insightful pieces. 4. Read + Synthesize — For each picked entry, read the full content and summarize in 2-3 sentences. Prefer fetching the URL directly (e.g. WebFetch) if available — keeps full text out of context. Otherwise use feed get entry <id> to read the stored content. Parallelize when possible. 5. Present — Compile the summaries into a digest. Group by theme if natural clusters emerge.
Commands
feed get entries --limit N # list unread entries (table)
feed get entries --feed <id> --limit N # filter by feed
feed get entry <id> # read full post (markdown)
feed fetch # pull latest from all feeds
feed search "<query>" # full-text search
feed update entries --read <id> ... # batch mark read
feed get feeds # list feeds with unread counts
feed get stats # database statsNotes
- The entries table includes full URLs. Prefer fetching URLs directly (keeps full text out of your context window). Fall back to
feed get entry <id>if you don't have a web fetch tool. - Do NOT mark entries as read. The user decides what to mark read.
- Default output is table — most token-efficient for scanning. Avoid
-o json. - Filter by feed if too many entries:
--feed <feed_id>.