digest
Tech digest for developers. Aggregates top RSS feeds (Hacker News, Lobste.rs, The Changelog, etc.) and produces a daily recap sorted by day. Use /digest for the last 3 days, /digest 7 for 7 days, /digest 14 for 14 days. Keywords: digest, recap, tech news, dev, RSS, hacker news.
- License 许可
- MIT
- 所属仓库
- caezium/skills
- 最近更新
- 2026-08-24
- Stars
- ★ 3
- Forks
- 0
01 前言 Front Matter
- name
- digest
- description
- Tech digest for developers. Aggregates top RSS feeds (Hacker News, Lobste.rs, The Changelog, etc.) and produces a daily recap sorted by day. Use /digest for the last 3 days, /digest 7 for 7 days, /digest 14 for 14 days. Keywords: digest, recap, tech news, dev, RSS, hacker news.
- allowed-tools
- [ "Read", "Bash" ]
- argument-hint
- [number_of_days]
- user-invokable
- true
02 资源文件 2
- 脚本fetch_feeds.py9.0 KB
- 参考文档sources.yml539 B
03 SKILL.md 正文
Tech Digest
You are a tech news assistant. You aggregate top RSS feeds and produce a structured daily digest of recent articles.
Procedure
Follow these steps in order:
Step 1: Parse the argument
- If the user passes a number (e.g.
/digest 7), use it as the number of days. - Otherwise, default to 3 days.
- Store this value as
DAYS.
Step 2: Fetch and parse articles
Run the following Python script via Bash, replacing DAYS with the value from step 1:
python3 ~/.claude/skills/digest/fetch_feeds.py DAYS
This script:
- Reads
sources.ymlfrom the same directory - Fetches all RSS feeds in parallel (threads)
- Parses XML, filters by date, deduplicates by URL
- For sources with a
limitfield: keeps the top N articles by score (vote count) - Outputs results as TSV (tab-separated), sorted by date descending:
DATE\tTITLE\tLINK\tCATEGORY\tDESCRIPTION\tSOURCE
Step 3: Format the output
From the script output, produce the digest in markdown:
- Header:
# Tech Digest -- [start_date] to [end_date]
> X articles from Y sources over the last Z days
Dates in readable English format (e.g. "April 7, 2026").
- Articles grouped by day, most recent first:
## [Day of week], [date in English]
- **[Article title](URL)** -- `category` -- *Source name*
Short description of the article...
- Day of week in English: Monday, Tuesday, Wednesday, Thursday, Friday, Saturday, Sunday
- One category between backticks (the most relevant one)
- Source name in italics
- If the description is empty or "N/A", omit the description line
- Footer: the script outputs a
SOURCES:section at the end. Format it as:
---
### Sources
- [Source name](site URL) -- Short description
*Made with <3 by [Camille Roux](https://www.camilleroux.com) · [X](https://x.com/CamilleRoux) · [LinkedIn](https://www.linkedin.com/in/camilleroux) · [Bluesky](https://bsky.app/profile/camilleroux.com) · [Mastodon](https://mastodon.social/@camilleroux)*
Step 4: Handle errors
- If the script outputs
ERROR: ...lines (on stderr), show a warning at the top of the digest:
> **Note:** The feed "Source name" could not be fetched.
- If no articles match the date criteria, say so clearly.
04 同仓库更多 Skills
writing-for-agents
Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.
wrangler
Cloudflare Workers CLI for deploying, developing, and managing Workers, KV, R2, D1, Vectorize, Hyperdrive, Workers AI, Containers, Queues, Workflows, Pipelines, and Secrets Store. Load before running wrangler commands to ensure correct syntax and best practices. Biases towards retrieval from Cloudflare docs over pre-trained knowledge.
workers-best-practices
Reviews and authors Cloudflare Workers code against production best practices. Load when writing new Workers, reviewing Worker code, configuring wrangler.jsonc, or checking for common Workers anti-patterns (streaming, floating promises, global state, secrets, bindings, observability). Biases towards retrieval from Cloudflare docs over pre-trained knowledge.
wizard
Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.
why
Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available evidence sources, searches each relevant category, and returns a cited read on decisions and tradeoffs. Use how for runtime behavior.
week-prep
Generate a briefing with calendar, tasks, and attention flags. Use for "week prep", "briefing", or "what's on this week".