← FeederCONTENT HISTORY
WHAT CHANGED
Update to Feeder
Snapshot Nov 10, 2026 · 00:09 UTC · version 1.0.0
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save Feeder and check future changes in Following.
Up to 3 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Set up or run ongoing monitoring of a topic in Feeder; use when the user wants to follow a subject, company, or keyword over time, or asks what happened lately on a monitored topic.",
"included_files": [],
"name": "feeder-topic-monitor",
"skill_md_contents": "---\nname: feeder-topic-monitor\ndescription: Set up or run ongoing monitoring of a topic in Feeder; use when the user wants to follow a subject, company, or keyword over time, or asks what happened lately on a monitored topic.\nmetadata:\n short-description: Follow a topic across sources over time\n---\n\n# Topic Monitor\n\nBuild a durable monitoring setup for a topic in the user's Feeder account, or run a check against one that already exists.\n\n## Tool-call guardrails\n\n- Feeder tools require a connected Feeder account on a Plus plan or higher. If a tool call returns an upgrade message, relay it briefly and stop; do not retry.\n- Adding feeds changes the user's account. Confirm the list of sources with the user before calling `Feeder:add_feed`.\n- Prefer existing subscriptions: search the user's own feeds before proposing new sources.\n\n## Workflow\n\n### 1) Understand the topic\nClarify the topic if vague (\"AI\" is too broad; \"EU AI regulation\" is workable). Identify 2 to 5 search phrasings including synonyms and key entities.\n\n### 2) Check what already exists\n1. Call `Feeder:search_posts` with each phrasing to see how well the user's current subscriptions already cover the topic.\n2. Call `Feeder:list_folders` to see whether a folder for this topic already exists.\n3. If coverage and structure exist, skip to step 4.\n\n### 3) Build the setup (with consent)\n1. Find candidate sources with `Feeder:search_feeds` (site names, RSS URLs, topic keywords).\n2. Show the user the candidates and let them pick.\n3. Create a folder for the topic with `Feeder:create_folder` (a plain name like \"EU AI Act\").\n4. Subscribe with `Feeder:add_feed`, then file each feed with `Feeder:add_feed_to_folder`.\n\n### 4) Run a check\n1. Pull recent posts for the topic: `Feeder:get_posts` scoped to the topic folder, plus `Feeder:search_posts` with the phrasings from step 1 to catch mentions outside the folder.\n2. Summarize developments in chronological order: what happened, which source reported it, what changed since the last check.\n3. Flag disagreements between sources explicitly; provenance is the point of monitoring.\n\n### 5) Keep the trail\nOffer to save key posts into a collection named after the topic (`Feeder:list_collections`, then `Feeder:add_to_collection`), so the next check can build on a curated record.\n"
}SHA-256 of public snapshot: b3cd57df800b56972a3a194ebece3af814954e6ec5c3456eeb53fef6b84f5db4