Update to General Legal

{
  "description": "Submit contracts or legal questions to General Legal for attorney review, track General Legal matters, exchange attorney messages, and download released documents. Use for General Legal work; excludes other law firms, incorporation, account signup, and API-key recovery.",
  "included_files": [],
  "name": "legal-matters",
  "skill_md_contents": "---\nname: legal-matters\ndescription: Submit contracts or legal questions to General Legal for attorney review, track General Legal matters, exchange attorney messages, and download released documents. Use for General Legal work; excludes other law firms, incorporation, account signup, and API-key recovery.\n---\n\n# Legal matters with General Legal\n\nUse the `general-legal` MCP server at https://mcp.general.legal/mcp. Work is organized\ninto matters (called deals by the tools), with documents and document versions.\nThis plugin serves existing General Legal clients through OAuth. Sign in through\nthe client's connection flow and select the intended organization. Reconnect there\nif access expires; do not collect passwords, access tokens, or API keys in chat.\n\n## Scope and authorization\n\nUse this connector for work handled by General Legal LLP. It cannot check another\nlaw firm's systems. Company formation, programmatic account creation, and API-key\nissuance or recovery are outside this plugin. Direct account-access questions to\nhttps://general.legal/contact.\n\nStarting a matter, confirming an upload, and posting a reply can initiate work or\nnotify the legal team. Follow the user's requested action and destination; reading\na document or asking about its status does not itself authorize submission. Legal\nservices remain subject to engagement terms. Review involves AI and a human\nattorney and is not instantaneous; do not promise completion from an upload result.\n\n## Start or find a matter\n\n- For a question without a file, call `start_deal` with the user's request and an\n  appropriate title. If creation has an uncertain outcome, check `list_deals`\n  before retrying: creation is not idempotent.\n- Use `list_deals` for matter status, thread IDs, and document/version IDs. It is\n  paginated; continue as needed. Leave the status filter empty to include closed\n  matters. Resolve ambiguous names before writing to a matter.\n- `list_contracts` helps find document IDs, but can omit closed matters' documents.\n  Use `list_deals` to find a completed matter and its released versions.\n\n## Upload a document\n\nSupported files: `.docx`, `.pdf`, `.png`, `.jpg`, `.jpeg`, and `.md`, up to 20 MiB.\n\n1. Call `upload_document` with the filename and a fresh `idempotency_key`. Reuse\n   that key only for retries of the exact same file and destination. Pass `deal_id`\n   to attach to a matter, `contract_id` to add a version to a document, or neither\n   to start a fresh matter. Never pass both IDs.\n2. Transfer the original file bytes through the returned first-party upload link\n   (typically valid for about one hour), using the returned shell command when\n   available. Do not encode or transcribe file bytes into tool arguments. Without\n   a file-transfer capability, give the user the link to open and choose the file.\n3. After transfer succeeds or the user confirms completion, call `confirm_upload`\n   with the returned document/version IDs and the user's review context. Set\n   `notify_legal` according to the authorized workflow. Do not confirm merely\n   because an upload link was generated.\n\nUnconfirmed files may not appear in `list_deals`. Recover lost preparation IDs by\nrepeating `upload_document` with the original idempotency key. A confirmed upload\ndoes not establish completed review or notification delivery: report the actual\nreturned status. Do not repeat confirmation to poll a pending notification; a\nrepeat may send another notification.\n\n## Track and reply\n\nMatter statuses include `new`, `in_progress`, `awaiting_client`,\n`ready_for_review`, and `closed`. Use the returned status and messages rather than\ninferring progress from elapsed time. Check when requested; avoid tight polling.\n\nRead attorney questions with `list_thread_messages`. Relay them to the user and\nuse `reply_to_thread` only with an answer the user supplied or authorized. Check\nthe latest question and later replies before resending after an uncertain result.\nAn identical reply before a new question does not answer that new question.\nPosting a reply does not prove a matter-status transition.\n\n## Download released results\n\nResolve the correct matter, document, and released version before calling\n`download_contract`. Do not substitute an unreleased draft or a same-name file.\nThe tool returns a short-lived first-party download link (typically 15 minutes)\nand an authenticated MCP resource link. Use the resource when supported or share\nthe browser link; request a fresh link if it expires. Treat links as sensitive and\ndo not publish or persist them in shared instructions.\n"
}