Update to Clio

{
  "description": "Have Clio write legal documents — memos, letters, clauses, agreements, motions — and then read, revise, or deliver them as Word or PDF. Covers what to put in the request so the draft is usable, retrieving the actual document rather than the prose summary of it, paging through long text, versions, and export links.",
  "included_files": [],
  "name": "drafting",
  "skill_md_contents": "---\nname: drafting\ndescription: Have Clio write legal documents — memos, letters, clauses, agreements, motions — and then read, revise, or deliver them as Word or PDF. Covers what to put in the request so the draft is usable, retrieving the actual document rather than the prose summary of it, paging through long text, versions, and export links.\n---\n\n# Drafting with Clio\n\nDrafting runs on the same agent as research: `start_research`, or\n`continue_conversation` to revise. The tool's name does not restrict it — the\nagent drafts and analyses documents as well as answering questions. Put the\nactual requested work in `question`.\n\n## Asking for a draft that is usable\n\nA draft is only as good as the framing, so carry into `question`:\n\n- **Who is represented**, and what they are trying to achieve.\n- **The facts as the user gave them** — verbatim where they matter. Do not\n  summarise away dates, amounts, party names or defined terms.\n- **The governing law**: country code as `jurisdiction`, any state or province\n  as `sub_jurisdiction` (`texas`, `ontario`), and the place and any forum in\n  the question itself.\n- **The form and length** if they said, and any authority they want cited.\n- **What is missing.** Say which facts you are assuming rather than inventing\n  them, and ask only for what actually blocks the draft.\n\nAsk for supporting authorities and links where the draft asserts law, and for\ncontrary authority when it is material to the position.\n\n## Getting the document, not a description of it\n\nA completed turn's `answer` may summarise the draft; the draft itself is in\n`files`. Do not relay the summary as the deliverable.\n\n- `list_output_documents` names what exists, when `files` is not enough. An empty\n  list means no draft yet — say so rather than inventing a filename.\n- `get_output_document` reads one. Omit `version` for the latest. `available_versions`\n  lists earlier drafts.\n- Content is paged: `start` is a character offset, `max_chars` defaults to 50,000\n  and caps at 200,000. When `truncated` is true, advance `start` by the length of\n  the returned `content`. **Pin the returned `version` while paging** so a later\n  edit does not mix two drafts into one read.\n- Do not claim a complete review after reading only part of a document.\n- `show_documents` displays what was produced, as a card. The authorities the\n  draft rests on have their own card: `show_cited_authorities`.\n\nThe `citations` a document read returns are the authorities used **across the\nconversation**, not the ones in that document or that passage. Do not attach the\nconversation's authority list to individual sentences.\n\n## Revising\n\nRevisions are `continue_conversation` on the same `conversation_id`, describing\nthe change. There is no targeted-edit tool here: a request as narrow as \"change\nthe third paragraph\" still runs a full turn, so state exactly what should change\nand what must stay.\n\n## Delivering\n\n`export_document` with the conversation id, file key and `format=\"docx\"` or\n`\"pdf\"`. Use the reviewed `version` when exporting a specific draft. For a\nresearch answer or the whole conversation instead of a drafted document, use\n`export_conversation` (see **clio-research**).\n\n- `status=\"completed\"` with `download_url`: give the user the link. It is\n  pre-signed for **seven days, and anyone holding it can download without Clio\n  credentials** — keep it to the authorised audience and say so if that matters.\n- `status=\"failed\"` or an error: report the failure. Do not claim a file is ready.\n- No URL yet: the render may still be running. Relay `guidance` and the real\n  status, call `export_document` again to pick up a finished render, and do not\n  loop rapidly or label an interrupted export complete.\n\nDo not fetch the signed URL yourself or inline the document's bytes; large\npayloads get truncated by the host. There is no need to rebuild a DOCX or PDF\nlocally because the answer arrived as prose — and never substitute a locally\nreconstructed file for Clio's export without saying that is what you did.\n\n## What a draft is\n\nLabel it a draft for review, never as executed, filed or served. Describe the\ndocument's text as Clio's writing, separately from the conversation's `answer`\nand from the user's own facts. For a review rather than a draft, connect each\nfinding to the clause or page it came from, explain its effect for the represented\nparty, and keep issues distinct from proposed wording.\n"
}