Update to Clio

{
  "description": "Work with the firm's own records in Clio Manage — a matter's status, parties, notes and custom fields; documents and folders; tasks and what is due; the calendar; time entries, expenses and bills; logged calls and emails; and searching inside document and note bodies. Use it whenever the answer is in the firm's records rather than in the law, and for creating or updating those records. Clio Manage only: Grow leads and Operate matters are different products, and legal research belongs with clio-research.",
  "included_files": [],
  "name": "clio-manage",
  "skill_md_contents": "---\nname: clio-manage\ndescription: \"Work with the firm's own records in Clio Manage — a matter's status, parties, notes and custom fields; documents and folders; tasks and what is due; the calendar; time entries, expenses and bills; logged calls and emails; and searching inside document and note bodies. Use it whenever the answer is in the firm's records rather than in the law, and for creating or updating those records. Clio Manage only: Grow leads and Operate matters are different products, and legal research belongs with clio-research.\"\n---\n\n# Clio Manage\n\nClio reaches into the firm's live Clio Manage records: it can read them, and it\ncan create, update and delete them.\n\nThere is no Clio tool on this server. It is the same `start_research` /\n`continue_conversation` conversation as everything else; what selects Clio work is\nthat the question is about **the firm's own records** rather than about the law.\nCarry the user's own specifics — the matter, the client, the dates — into it.\n\n## What is Clio work rather than research\n\nThe dividing line is where the answer lives. \"What did the court hold in *Smith*\" is\nresearch. \"What is the status of the Smith matter, and what is due on it next week\"\nis Clio: nothing in the law library knows it.\n\n| The user asks about | Reaches |\n| --- | --- |\n| A matter's status, stage, parties, notes, custom fields; contacts and companies | matters and contacts |\n| Documents, folders, templates, text snippets | documents |\n| What is due, outstanding or done; task templates; docketing | tasks |\n| What is scheduled — hearings, depositions, appointments, reminders | calendar |\n| Time entries, timers, expenses, bills, payments, balances | time & billing |\n| Logged calls and emails, message history with a client | communications |\n| Users, groups, custom field definitions, reports, webhooks | admin |\n| A phrase buried *inside* a document or a note | matter content search |\n\nThe last row is the one people get wrong. Listing notes returns note **records**;\nfinding the sentence where the client agreed to something searches note **bodies**.\nAsk for the one you mean — \"search the matter's documents for…\" reads bodies, \"list\nthe notes on the matter\" reads records.\n\n## Phrase the question so it lands\n\nName the matter the way the user named it, and say which product: a firm may have\nthe same client in Manage and in Grow. If the user gives a matter number, pass it\nthrough verbatim rather than describing the matter.\n\nAsk for a date window when one is implied — \"what is due\" almost always means this\nweek or this month, and an unbounded task list is not an answer.\n\n## Writing to the record stops for approval\n\nCreating, updating and deleting are gated per resource: the run parks with a\n`tool_approval` interruption naming what Clio is about to write. Resolve it as\nevery approval is resolved here — **put it to the user in your own words and carry\nback their answer**. Never approve a write to the firm's records on the assumption\nthat an earlier instruction covered it; a matter closed or a time entry deleted is\nnot something an apology undoes.\n\n`list_approval_keys` shows what can be pre-granted through\n`start_research(initial_approval_keys=[...])`. Pre-grant only what the user actually\nasked to allow, and read the labels back to them when you do.\n\nTwo writes worth double-checking before you relay them, because they are easy to ask\nfor casually and hard to reverse: deleting anything, and changing a matter's status\nor stage.\n\n## When the tools are not there\n\nClio Manage tools appear only for a session opened with **Clio Work credentials**,\non a firm licensed for Manage, with the integration enabled. The token decides it,\nnot the person: the same user arriving with a vLex token has no Clio tools at all.\n\nWithout them Clio answers from legal research instead, which reads like a thin\nanswer rather than a missing connection. If the reply covers doctrine when firm\nrecords were asked for, or Clio says it cannot see the matter, say the session\nmay not have Clio Manage access and let the user confirm — do not retry, and do not\npresent the research fallback as the Clio Manage answer.\n\nA session with no Clio Work credential at all does not reach those records: the\nconnection is established by signing in on the web through Clio Work, and every tool\nhere answers with that until it is. If that is what you see, relay it — sign in there,\nthen try again — rather than reporting it as a Clio failure.\n\n## What the records are, and are not\n\nA Clio record is what the firm wrote down, not what happened. An empty task list\nmeans nothing was logged, which is not the same as nothing being due, and a note is\none person's account. Say which you are reporting when it matters.\n\nReport counts and dates as the records gave them. Do not total hours, fees or\nbalances yourself from a list of entries — ask Clio for the figure, so it comes\nfrom the record rather than from arithmetic in the reply.\n"
}