P
podanypepa/skim
Personal RSS agent: Claude Code skills score your feeds against your interests and write a short daily digest.
updated 2026-11-18
View on GitHub ↗Direct link · no redirect page
After install: how to tell it works
- What you see after install — The command exits 0 and the terminal shows no "command not found" or "permission denied".
- One-line self-check — Run the smallest usage example from that repository's README. If the output matches what the README describes, it is working.
- If that does not work — This project has no troubleshooting notes. Search its issues for "install".
The install command comes from the repository; these checks describe observable results only and do not replace the project's own docs.
- Star count
- 0 ★ · podanypepa/skim · read from the GitHub search API · (checked 2026-11-19 20:00:48)
- Source
- read directly from its GitHub page · type: open-source project
- Harvest history
- first seen 2026-11-19 · last seen 2026-11-20 · seen 2× · listed by 1 sources
- Score
- score 103 · 1 sources · repo
- Install
- see Install & config above
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: AI Agent. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
podanypepa/skim;first catalogued 2026-11-19;last seen 2026-11-20。There is no official certification or quality rating here — we record sources and dates only.README excerpt (English, untranslated) · Read the full README on GitHub →
# skim
Excerpted from the repository README (abridged)
A personal RSS agent that reads the feeds for you and hands you a short daily digest.
skim is a replacement for scrolling through hundreds of headlines in a
feed reader. You tell it what you care about, it follows a small set of
hand-picked sources, scores every new article against your interests,
groups duplicate coverage into stories and writes a concise daily digest
with correct links back to the originals.
It is built as a set of Claude Code
skills (the judgement: what is relevant, what is one story, how to
summarise it) on top of small, deterministic Go tools (the mechanics:
fetching, parsing, validating, storing, rendering).
> skim
Fetched 151 · triaged 151 · 36 stories · 0 feeds failed
## ai-novinky
1. Claude Fable 5.2 is the top model again — 20 % cheaper per token, but hungrier …
2. Claude Code leaks secrets to GitHub — "don't ask again" stores commands verbatim …
## golang
21. Go turns 17: the year in review and a look at 1.28 …
## python
28. Tim Peters has died …
Feedback? e.g. "22 good, 26 not interesting".
## Why
Feed readers show you everything and leave the filtering to you. skim
flips that around:
You describe interests once (topics.md) — what you want, what you
don't, how deep, how much per day.
The agent does the reading — every article gets a 1–5 score and a
one-sentence reason, so mistakes are visible and easy to correct.
You read one digest a day — stories, not headlines; the same news
from five outlets becomes one entry with five sources.
The split between skills and Go tools is deliberate: language models are
good at judgement and bad at bookkeeping, so every step where a mistake
would be silent (duplicates, broken links, half-written files) is handled
by code with tests, and the model only ever produces content that the
code validates before anything is written.
## How it works
feeds.yaml topics.md topics.md
│ │ │
▼ ▼ ▼
┌────────────┐ ┌──────────────┐ ┌──────────────┐
│ skimfetch │────▶│ skim-triage │───────▶│ skim-digest │◀── your feedback
│ (Go) │ │ + skimtriage │ │ + skimdigest │
└─────┬──────┘ └──────┬───────┘ └──────┬───────┘
▼ ▼ ▼
data/articles/ data/triage/ data/digest/D.md
D.jsonl D.jsonl (+ D.json)
1. Fetch — skimfetch downloads every feed in feeds.yaml
concurrently, uses conditional requests (ETag / Last-Modified), parses
RSS 2.0, RSS 1.0 and Atom, deduplicates by GUID / link, converts HTML
to plain text and appends new articles to a daily JSONL file. A broken
feed never stops the run.
2. Triage — the skim-triage skill reads topics.md and scores each
new article 1–5 with a short reason. skimtriage pending hands out
batches of untriaged articles; skimtriage save validates the batch
(known ids, integer scores, reason length…) and writes it all or
nothing.
3. Full text — many feeds only carry a teaser (or nothing). Before
the digest, skimdigest fulltext fetches the article page for
candidates with short content, extracts the readable text and stores
it, so summaries have real substance. It honours robots.txt (RFC 9309,
including every redirect hop), only connects to public addresses, and
tries each page once — transient failures (network, 429, 5xx) are
retried on the next run. Sites that block bots (e.g. Reddit) keep their
skim is a replacement for scrolling through hundreds of headlines in a
feed reader. You tell it what you care about, it follows a small set of
hand-picked sources, scores every new article against your interests,
groups duplicate coverage into stories and writes a concise daily digest
with correct links back to the originals.
It is built as a set of Claude Code
skills (the judgement: what is relevant, what is one story, how to
summarise it) on top of small, deterministic Go tools (the mechanics:
fetching, parsing, validating, storing, rendering).
> skim
Fetched 151 · triaged 151 · 36 stories · 0 feeds failed
## ai-novinky
1. Claude Fable 5.2 is the top model again — 20 % cheaper per token, but hungrier …
2. Claude Code leaks secrets to GitHub — "don't ask again" stores commands verbatim …
## golang
21. Go turns 17: the year in review and a look at 1.28 …
## python
28. Tim Peters has died …
Feedback? e.g. "22 good, 26 not interesting".
## Why
Feed readers show you everything and leave the filtering to you. skim
flips that around:
You describe interests once (topics.md) — what you want, what you
don't, how deep, how much per day.
The agent does the reading — every article gets a 1–5 score and a
one-sentence reason, so mistakes are visible and easy to correct.
You read one digest a day — stories, not headlines; the same news
from five outlets becomes one entry with five sources.
The split between skills and Go tools is deliberate: language models are
good at judgement and bad at bookkeeping, so every step where a mistake
would be silent (duplicates, broken links, half-written files) is handled
by code with tests, and the model only ever produces content that the
code validates before anything is written.
## How it works
feeds.yaml topics.md topics.md
│ │ │
▼ ▼ ▼
┌────────────┐ ┌──────────────┐ ┌──────────────┐
│ skimfetch │────▶│ skim-triage │───────▶│ skim-digest │◀── your feedback
│ (Go) │ │ + skimtriage │ │ + skimdigest │
└─────┬──────┘ └──────┬───────┘ └──────┬───────┘
▼ ▼ ▼
data/articles/ data/triage/ data/digest/D.md
D.jsonl D.jsonl (+ D.json)
1. Fetch — skimfetch downloads every feed in feeds.yaml
concurrently, uses conditional requests (ETag / Last-Modified), parses
RSS 2.0, RSS 1.0 and Atom, deduplicates by GUID / link, converts HTML
to plain text and appends new articles to a daily JSONL file. A broken
feed never stops the run.
2. Triage — the skim-triage skill reads topics.md and scores each
new article 1–5 with a short reason. skimtriage pending hands out
batches of untriaged articles; skimtriage save validates the batch
(known ids, integer scores, reason length…) and writes it all or
nothing.
3. Full text — many feeds only carry a teaser (or nothing). Before
the digest, skimdigest fulltext fetches the article page for
candidates with short content, extracts the readable text and stores
it, so summaries have real substance. It honours robots.txt (RFC 9309,
including every redirect hop), only connects to public addresses, and
tries each page once — transient failures (network, 429, 5xx) are
retried on the next run. Sites that block bots (e.g. Reddit) keep their
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/podanypepa-skim/)
- Source
- github · https://github.com/podanypepa/skim
- Browse by field
- AI agents
- added
- today
More entries
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.