RSS Digest
The pack's one tool-providing skill. Every other starter skill is a
procedure over tools the agent already has; this one ships its own code in
tools.py and registers it as rss-digest/fetch_rss.
It exists to show the shape: a manifest entry per @tool function, matching the
signature exactly, plus the network:read permission the tool actually uses.
Procedure
- Fetch the feed with
rss-digest/fetch_rss(url, max_entries=10). It
returns {"feed_title": ..., "entries": [{"title", "link", "published", "summary"}], "count": N} in feed order — conventionally newest first, but
the feed decides, so read the published values rather than assuming.
- If the call returns an
error key, report it verbatim. A malformed feed,
a 404, a blocked host, a feed with no recognizable entries, and a feed
carrying a DTD are all real answers; an invented digest is not.
- Digest the entries. One line per entry: what it is and why it might
matter, with its link. Group by theme when more than five entries share one.
- Lead with the exception. If one entry is materially different from the
usual traffic on this feed — a breaking change, a security release, a
shutdown notice — put it first and label it.
- Say the range you covered — feed title, entry count, and the oldest date
included — so the user knows what was and was not read.
Notes
- The tool follows GAIA's
WebClient, which refuses private and loopback
addresses unless the operator has allowed that host. Call the tool for any
feed URL the user gives you and report what it returns; don't refuse on its
behalf.
- Feeds declaring a DTD are refused rather than parsed: entity expansion is a
denial-of-service vector, and no real feed needs one.
- RSS 1.0 / RDF feeds are not supported and report an error rather than an empty
digest — "nothing published" and "I could not read this" must never look alike.
- Entry summaries in feeds are frequently truncated or HTML-laden. Treat them as
a headline, not the article; say so rather than over-reading a stub.
Fork this
Copy the directory and edit tools.py — that is the whole point of a tool
skill. Parse a JSON API instead of XML, or add a since parameter for
date-bounded fetches. Whatever you change in the signature, mirror in
metadata.gaia.tools: the loader compares them and refuses the skill if they
disagree, so a stale manifest can never ship.
1---2name: rss-digest3description: Read an RSS or Atom feed and summarize the newest entries. Use when the user gives a feed URL, asks what a blog or release feed has published lately, or wants a digest of a site that offers a feed.4license: MIT5version: 1.0.06metadata:7 gaia:8 security_tier: community9 permissions:10 - network:read11 requirements:12 python: ">=3.10"13 tools:14 - name: fetch_rss15 description: Fetch an RSS or Atom feed and return its entries as structured data.16 parameters:17 url:18 type: string19 required: true20 max_entries:21 type: integer22 required: false23 default: 1024 returns:25 type: object26 atomic: true27 provenance:28 source: https://skillmd.com/skills/amd/rss-digest29 upstream: starter-pack30---3132# RSS Digest3334The pack's one **tool-providing** skill. Every other starter skill is a35procedure over tools the agent already has; this one ships its own code in36`tools.py` and registers it as `rss-digest/fetch_rss`.3738It exists to show the shape: a manifest entry per `@tool` function, matching the39signature exactly, plus the `network:read` permission the tool actually uses.4041## Procedure42431. **Fetch the feed** with `rss-digest/fetch_rss(url, max_entries=10)`. It44 returns `{"feed_title": ..., "entries": [{"title", "link", "published",45 "summary"}], "count": N}` in feed order — conventionally newest first, but46 the feed decides, so read the `published` values rather than assuming.472. **If the call returns an `error` key, report it verbatim.** A malformed feed,48 a 404, a blocked host, a feed with no recognizable entries, and a feed49 carrying a DTD are all real answers; an invented digest is not.503. **Digest the entries.** One line per entry: what it is and why it might51 matter, with its link. Group by theme when more than five entries share one.524. **Lead with the exception.** If one entry is materially different from the53 usual traffic on this feed — a breaking change, a security release, a54 shutdown notice — put it first and label it.555. **Say the range you covered** — feed title, entry count, and the oldest date56 included — so the user knows what was and was not read.5758## Notes5960- The tool follows GAIA's `WebClient`, which refuses private and loopback61 addresses unless the operator has allowed that host. Call the tool for any62 feed URL the user gives you and report what it returns; don't refuse on its63 behalf.64- Feeds declaring a DTD are refused rather than parsed: entity expansion is a65 denial-of-service vector, and no real feed needs one.66- RSS 1.0 / RDF feeds are not supported and report an error rather than an empty67 digest — "nothing published" and "I could not read this" must never look alike.68- Entry summaries in feeds are frequently truncated or HTML-laden. Treat them as69 a headline, not the article; say so rather than over-reading a stub.7071## Fork this7273Copy the directory and edit `tools.py` — that is the whole point of a tool74skill. Parse a JSON API instead of XML, or add a `since` parameter for75date-bounded fetches. Whatever you change in the signature, mirror in76`metadata.gaia.tools`: the loader compares them and refuses the skill if they77disagree, so a stale manifest can never ship.