agentleFS
SkinnnyJaySkinnnyJay/wiki-llm/skills/wiki-research-feeds/SKILL.md

wiki-research-feeds

Skill0 starsChanged 4 months agoMITView on GitHub

Monitor RSS/Atom feeds or OPML lists and ingest recent items into raw/feeds/. Invoked by wiki-research for feed/newsletter research.

  • Installs packages

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 5 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Only process items published within the recency window.

    line 59
  2. Distinctive:

    Before fetching each item's full content:

    line 77
  3. Distinctive:

    If Firecrawl is unavailable, use stdlib:

    line 97
  4. Distinctive:

    If input is an OPML file:

    line 109
  5. Very specific:

    Run each file through skills/wiki-research/references/source-eval.md.

    line 140
  6. Distinctive:

    Write a digest summary if requested:

    line 142
  7. Very specific:

    CLI: Run llm-wiki integrations status and any llm-wiki line from Step 1 of this skill (from the vault root).

    line 177

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Wiki research — feeds

Fetches items from RSS/Atom feeds or OPML lists into raw/feeds/. Use this sub-skill when the input is a feed URL, OPML file, or the user wants to monitor a set of sources for recent content.


Step 1 — Determine input format

InputAction
Single feed URL (.xml, .rss, /feed, /atom)Fetch and parse directly
OPML file pathParse OPML to extract all feed URLs, then process each
Blog URL (not feed URL)Auto-discover feed: try <URL>/feed, <URL>/rss, <URL>/atom.xml
Comma-separated list of URLsProcess each as individual feeds

Step 2 — Check adapter availability

Preferred: feed CLI

which feed && feed --version

If available:

feed fetch <FEED_URL> --since 24h --format json > /tmp/feed-items.json

Fallback: stdlib XML parsing

llm-wiki ingest url <FEED_URL> --out feeds/raw/<source-slug>.xml
# Then parse with Python:
python3 << 'EOF'
import xml.etree.ElementTree as ET, json, sys
tree = ET.parse('feeds/raw/<source-slug>.xml')
root = tree.getroot()
ns = {'atom': 'http://www.w3.org/2005/Atom'}
# Handle both RSS 2.0 and Atom
items = root.findall('.//item') or root.findall('.//atom:entry', ns)
for item in items:
    title = item.findtext('title') or item.findtext('atom:title', namespaces=ns)
    link = item.findtext('link') or item.findtext('atom:link', namespaces=ns)
    pubdate = item.findtext('pubDate') or item.findtext('atom:updated', namespaces=ns)
    print(json.dumps({'title': title, 'link': link, 'date': pubdate}))
EOF

Step 3 — Apply recency filter

Only process items published within the recency window. Default: last 7 days.

For monitoring / daily digests: use last 24 hours.

# With feed CLI
feed fetch <URL> --since 24h

# Manual date check (Python)
from datetime import datetime, timedelta, timezone
cutoff = datetime.now(timezone.utc) - timedelta(days=7)
# Skip items where parsed_date < cutoff

Step 4 — Deduplicate against existing raw/

Before fetching each item's full content:

llm-wiki raw rebuild-index
# Then check:
grep -r "source_url: <ITEM_URL>" raw/feeds/

Skip items already present in raw/ (same URL).


Step 5 — Fetch full content for each item

For each new item that passes the recency and dedup filters:

llm-wiki ingest firecrawl "<ITEM_URL>" \
  --out feeds/<source-slug>/<YYYY-MM-DD>/<item-slug>.md

If Firecrawl is unavailable, use stdlib:

llm-wiki ingest url "<ITEM_URL>" \
  --out feeds/<source-slug>/<YYYY-MM-DD>/<item-slug>.md

Limit: Cap at 20 items per feed per run to avoid context overflow.


Step 6 — OPML processing

If input is an OPML file:

import xml.etree.ElementTree as ET
tree = ET.parse('<OPML_PATH>')
feeds = [el.get('xmlUrl') for el in tree.findall('.//outline[@xmlUrl]')]
# feeds is now a list of RSS/Atom URLs — process each with Steps 2–5

Process feeds sequentially; do not parallelize (respect rate limits).


Step 7 — Add frontmatter to each file

---
source_type: feed
feed_url: https://...
feed_title: "Example Blog"
source_url: https://...          # item link
item_title: "<article title>"
item_published: YYYY-MM-DD
fetched_date: YYYY-MM-DD
adapter: firecrawl | stdlib_url
---

Step 8 — Evaluate and return to orchestrator

Run each file through skills/wiki-research/references/source-eval.md. Feed items often need recency evaluation — skip low-relevance items rather than ingesting everything.

Write a digest summary if requested:

  • Summarize all ingested items in outputs/feeds-digest-<YYYY-MM-DD>.md
  • List: title, source, 1-sentence summary, path to raw file

Then return to wiki-research Step 3 (post-process).


Done looks like

  • Feed items ingested under raw/feeds/ with frontmatter; recency/dedup rules applied.
  • Optional digest written under outputs/ when requested.
  • Orchestrator handles post-process and wiki-ingest.

Troubleshooting

SymptomFix
Feed URL returns HTML not XMLSite requires JS; try <URL>/feed.xml or check site for feed link in <head>
feed CLI not foundpip install feed-cli or use Python stdlib XML fallback
429 from feed serverWait 60s; some servers throttle XML requests
OPML has outdated/dead feed URLsSkip 404s; note [DEAD] in OPML review
Items have no full content (abstract only)Fetch linked article URL via wiki-research-web

Related skills

  • wiki-research — orchestrator that invoked this skill
  • wiki-research-web — for fetching full article content from feed item links
  • wiki-research-news — for general news queries (not feed-based monitoring)
  • wiki-research-loop — for recurring batch monitoring with research-tasks.json

Smoke check

  • CLI: Run llm-wiki integrations status and any llm-wiki line from Step 1 of this skill (from the vault root).
  • Prompt: Invoke this skill by name in Claude Code; complete Step 1 only and confirm expected CLI or file output.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

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.