opml-reader
Skill5 starsChanged 9 months agoMITView on GitHub
Store OPML files and fetch latest posts across RSS/Atom feeds. Use when a user provides an OPML URL or file path, wants it saved under ~/Code/Files, or wants the newest entries aggregated across feeds (with optional JSON/TSV output, dedupe, and concurrency controls).
- Installs packages
In this repository13 other files it gives its agents.
- apple-music-playerSkill
- apple-notesSkill
- applescript-open-appSkill
- confettiSkill
- ffmpeg-video-editor-h265Skill
- githubSkill
- git-searchSkill
- launchd-non-apple-jobsSkill
- mailapp-send-emailSkill
- open-meteo-weatherSkill
- playwright-cliSkill
- saySkill
- screen-recorderSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 2 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 9
Use scripts/opml_reader.py to (1) store OPML from a URL and (2) list the latest posts across all feeds in the OPML.
- Distinctive: line 12
Create a venv and install dependency:
- Very specific: line 36
If the user supplies an OPML URL, store it under ~/Code/Files using store.
- Distinctive: line 37
If the OPML file already exists, reuse it unless the user explicitly asks to overwrite.
- Very specific: line 38
Run latest to aggregate posts and return the newest entries across feeds.
- Very specific: line 42
Default output: text lines formatted as index.
- Very specific: line 43
Use --format json or --format tsv if the user needs machine-readable output.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
OPML Reader
Overview
Use scripts/opml_reader.py to (1) store OPML from a URL and (2) list the latest posts across all feeds in the OPML. Output timestamps are ISO-8601 in UTC.
Quick Start
- Create a venv and install dependency:
python3 -m venv ~/Code/sandbox/.venv-opml-reader
~/Code/sandbox/.venv-opml-reader/bin/pip install feedparser- Store an OPML file:
~/Code/sandbox/.venv-opml-reader/bin/python scripts/opml_reader.py store \
"https://example.com/feeds.opml" \
"~/Code/Files/feeds.opml"- Fetch latest posts:
~/Code/sandbox/.venv-opml-reader/bin/python scripts/opml_reader.py latest \
"~/Code/Files/feeds.opml" \
--limit 5Workflow
- If the user supplies an OPML URL, store it under
~/Code/Filesusingstore. - If the OPML file already exists, reuse it unless the user explicitly asks to overwrite.
- Run
latestto aggregate posts and return the newest entries across feeds. - Report partial results if some feeds fail (network timeouts are expected on large lists).
Output Options
- Default output:
textlines formatted asindex. title | feed | date | link. - Use
--format jsonor--format tsvif the user needs machine-readable output. - Dedupe is on by default. Use
--no-dedupeif the user wants raw results. - Adjust
--workersand--timeoutfor large or slow feed lists.
Resources
scripts/
scripts/opml_reader.py: Store OPML files and list latest posts across RSS/Atom feeds.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

