Update to Keeploop

{
  "description": "Today's schedule, the replies you owe, and today's monitor hits, in one short view.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 248
    },
    {
      "relative_path": "assets/keeploop.png",
      "size_in_bytes": 14672
    }
  ],
  "name": "keep-today",
  "skill_md_contents": "---\nname: keep-today\ndescription: \"Today's schedule, the replies you owe, and today's monitor hits, in one short view.\"\ncompatibility: \"Needs the Keeploop app on a Mac and its MCP connector (tools such as search_mail and find_attachments).\"\n---\n\nThe Keeploop tools may carry a prefix in this agent (for example mcp_keeploop_search_mail); use them by their Keeploop name.\n\nShow me my day, using the Keeploop tools.\n\n1. Call list_events with start and end both set to today's date (YYYY-MM-DD) to get today's events.\n2. Call awaiting_reply with direction=\"me\" and days=2 to find threads waiting on me.\n3. Call list_monitors, then check_monitor with limit=100 for each active monitor. Hits come oldest first: while a call returns 100 hits, call it again with since_hit_id set to the last_hit_id it returned. Keep the hits from today. In a Claude Duet channel, also call check_route with peek=true on its route (duet:<channel-name>) to see matches from monitors tagged for it.\nThen write three short sections. Schedule: each event's time, title and location, oldest first; mark events that are over, and flag overlaps or back-to-back meetings. Replies owed: sender, subject and mail_id, most urgent first, at most five. Monitor hits: the monitor's name and what arrived. Leave out a section that is empty and say \"Nothing on today\" if all three are.\nIf a tool is missing, is turned off in Keeploop, or answers that it needs Keeploop Pro, say so in one line and do what you can with the rest.\n"
}