Update to Refix

{
  "description": "Use Refix to answer questions about company data, run ongoing watchers, and catch up on what Refix found.",
  "included_files": [],
  "name": "work-with-refix",
  "skill_md_contents": "---\nname: work-with-refix\ndescription: Use Refix to answer questions about company data, run ongoing watchers, and catch up on what Refix found.\n---\n# Work with Refix\n\nCall `refix_get_context` before new work. If something is missing, send the user to the\nreturned link. Never ask for passwords or other secrets in chat.\nUse only the sources that `refix_get_context` lists as usable.\nRefix only reads data. Source writes are not available through this connection.\n\n## Ask a question\n\n- Call `refix_investigate` with a new `idempotency_key`. Keep the `investigation_id`.\n- Call `refix_get_investigation` until the run finishes. Each call waits up to 25 seconds\n  for news, so call again right away. Do not start another investigation to check progress.\n- If the state is `needs_input`, ask the user the pending question. Send the answer with\n  `refix_investigate` and `response_to_input_id`.\n- For a follow-up in a finished conversation, use `session_id`. To dig into a finding,\n  use `finding_id`. Send only one of these.\n- Investigations count toward the workspace's Refix usage. They send no Slack messages or emails.\n\n## Set up a watcher\n\nA watcher carries a goal. Refix keeps working on it and tells the user what it finds. Offer\none when the user wants an ongoing outcome, not a single answer.\n\n- Call `refix_list_watchers` first. Do not create a duplicate watcher.\n- Tell the user that watchers count toward the workspace's Refix usage and that everyone in\n  the workspace can see the watcher.\n- Ask where alerts go. Read `alert_channel` from `refix_get_context`:\n  - Offer this option only if you can run scheduled tasks:\n    **Here.** I'll check Refix on a schedule and tell you here. Alerts arrive when I next check, not instantly.\n  - `slack`: also offer **Slack DM.** Refix messages you in Slack as soon as it finds something.\n  - `email`: also offer **Email.** Refix emails you as soon as it finds something.\n  - `none`: say alerts stay here, and give the `connect_slack` link for instant Slack alerts.\n- Create the watcher with `refix_create_watcher`. Use `alerts: \"mcp_assistant\"` for \"here\".\n- After creation, say: Done. Refix will [keep alerts here / DM you on Slack / email you].\n  Everyone in your workspace can see this watcher in Refix. To change where alerts go, open\n  the watcher in Refix: <watcher_url>\n- If the user picked \"here\" and you can schedule tasks, set up a scheduled task that calls\n  `refix_list_findings` with the watcher's `watcher_id`, passing `since` as the time of the\n  previous check. If you cannot schedule tasks, say that alerts appear when the user asks\n  what is new. Never promise a check you cannot run.\n- To change a watcher, use `refix_update_watcher`. The objective cannot change: stop the watcher\n  and create a new one.\n\n## Catch up\n\n- Call `refix_list_findings` without `watcher_id` to get watcher alerts and other Refix updates.\n- Call it with no `since` for \"what's new\" in a new chat. It returns the last 7 days, newest first.\n- For a scheduled check, pass `since` as the time of the previous check.\n- Say \"nothing new\" only when the call succeeds with no items. Report errors as errors.\n- Reading findings changes nothing in Refix.\n\n## Rules\n\n- Let Refix do the analysis. Do not rebuild it with other tools.\n- Reuse an `idempotency_key` only to retry the identical request.\n- Follow the `next_action` in an error.\n"
}