← FeederCONTENT HISTORY

Update to Feeder

Snapshot Nov 10, 2026 · 00:09 UTC · version 1.0.0

Collection source: downloaded plugin package.

WHAT CHANGED

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 JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Research a question across the user's Feeder posts and build a cited collection; use when the user wants sourced research, a literature pass over their feeds, or a curated set of posts on a question.",
  "included_files": [],
  "name": "feeder-research-collection",
  "skill_md_contents": "---\nname: feeder-research-collection\ndescription: Research a question across the user's Feeder posts and build a cited collection; use when the user wants sourced research, a literature pass over their feeds, or a curated set of posts on a question.\nmetadata:\n  short-description: Research your feeds and save a cited collection\n---\n\n# Research Collection\n\nAnswer a research question from the user's own subscriptions, with every claim traceable to a post, and leave behind a curated collection.\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- `Feeder:expand_post` fetches full content for one post. Use it selectively on the posts that will carry the answer, not on every search hit.\n- Cite by post title and source feed. Do not invent posts or attribute claims to posts you did not read.\n\n## Workflow\n\n### 1) Frame the question\nRestate the research question and agree on scope with the user: time window, which feeds or folders count, and what the output should be (short answer, comparison, timeline).\n\n### 2) Sweep\n1. Run `Feeder:search_posts` with 3 to 6 phrasings: synonyms, key entities, and opposing terms. Scope to specific feeds or folders when the user named them.\n2. Collect candidate posts and dedupe. Note which searches came up empty; that is a finding too.\n\n### 3) Read\n1. Rank candidates by relevance and recency.\n2. Call `Feeder:expand_post` on the top posts (typically 5 to 10) to get full content.\n3. Extract facts, numbers, dates, and quotes with their source post.\n\n### 4) Synthesize\n- Answer the question first, in a few sentences.\n- Support with the evidence: one bullet per key fact, each ending with its source (post title, feed).\n- State conflicts between sources plainly, and say what is unknown or not covered by the user's feeds.\n\n### 5) Save the trail\n1. Ask whether to save the curated set. List existing collections with `Feeder:list_collections`.\n2. Save the load-bearing posts with `Feeder:add_to_collection` into the collection the user picks.\n3. Close by telling the user what was saved and where.\n"
}

SHA-256 of public snapshot: a01a34ac2e084b2083f2093b5c8f955354e5bec0929ec090e6c21ae02232a87f