{"id":88101,"plugin_id":"plugin_asdk_app_6aa5b6f101448191aa891472072098b0","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-10T00:09:14.991Z","digest":"d47cce98167b2a98185e5c46a87e1a312a1fe9fff22d79501153ee953f6acb9d","against":null,"payload":{"description":"Brief the user on what is new across their Feeder feeds; use when they ask what's new, want a morning brief, or want to catch up on their subscriptions.","included_files":[],"name":"feeder-daily-brief","skill_md_contents":"---\nname: feeder-daily-brief\ndescription: Brief the user on what is new across their Feeder feeds; use when they ask what's new, want a morning brief, or want to catch up on their subscriptions.\nmetadata:\n  short-description: Catch up on your feeds with a structured brief\n---\n\n# Daily Brief\n\nTurn the user's unread feeds into a short, structured brief they can act on.\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- If a Feeder tool returns `Tool <name> not found`, treat Feeder as unavailable for this task and ask the user to connect the Feeder app, then retry.\n- Post lists can be long. Work folder by folder rather than fetching everything at once.\n\n## Workflow\n\n### 1) Map the reading landscape\n1. Call `Feeder:list_folders` and `Feeder:list_feeds` to see the user's structure and unread counts.\n2. If the user asked about a specific area (\"my crypto feeds\"), narrow to the matching folder or feeds.\n\n### 2) Gather what is new\n1. For each folder or feed with unread posts, call `Feeder:get_posts` for the recent window (default: last 24 hours; use the user's requested window if given).\n2. Prioritize by unread count and recency. Skip feeds with nothing new.\n3. Only call `Feeder:expand_post` when a summary is too thin to describe a story the brief highlights.\n\n### 3) Write the brief\n- Lead with the 3 to 5 stories that matter most across all feeds, one line each with the source name.\n- Then a short section per folder (or feed, if unfoldered): what changed, in 1 to 3 bullets.\n- Note volume (\"12 new posts in Design, mostly about X\") instead of listing everything.\n- End with anything time-sensitive spotted (deadlines, releases, breaking items).\n\n### 4) Offer cleanup\n- Ask before marking anything read. If the user agrees, use `Feeder:mark_folder_read` or `Feeder:mark_feed_read` for the sections they confirm. Use `Feeder:mark_all_read` only when the user explicitly asks for everything.\n- If a story should be kept, offer to save it with `Feeder:add_to_collection` (list options with `Feeder:list_collections` first).\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}