Update to LegalQuants Litigation

{
  "name": "wiki",
  "description": "Build, explore, and maintain a lawyer's personal legal wiki: linked, source-grounded Markdown notes that preserve reusable law and method, never matter facts. Use when the user wants to add trusted knowledge, ask what their wiki says, browse it, or check its health.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 244
    },
    {
      "relative_path": "references/automation.md",
      "size_in_bytes": 3203
    },
    {
      "relative_path": "references/gate_prompts.md",
      "size_in_bytes": 14563
    },
    {
      "relative_path": "references/getting-started.md",
      "size_in_bytes": 1127
    },
    {
      "relative_path": "references/note_types.md",
      "size_in_bytes": 11804
    },
    {
      "relative_path": "references/okf-profile.md",
      "size_in_bytes": 19643
    },
    {
      "relative_path": "references/positions.md",
      "size_in_bytes": 3392
    },
    {
      "relative_path": "references/source_policy.md",
      "size_in_bytes": 2192
    },
    {
      "relative_path": "references/source_profile.json",
      "size_in_bytes": 2156
    },
    {
      "relative_path": "references/wiki_schema.md",
      "size_in_bytes": 11393
    },
    {
      "relative_path": "scripts/wiki.py",
      "size_in_bytes": 158480
    },
    {
      "relative_path": "scripts/wiki_retrieval.py",
      "size_in_bytes": 10508
    },
    {
      "relative_path": "scripts/wiki_wording.py",
      "size_in_bytes": 4080
    }
  ],
  "skill_md_contents": "---\nname: wiki\ndescription: >-\n  Build, explore, and maintain a lawyer's personal legal wiki: linked,\n  source-grounded Markdown notes that preserve reusable law and method,\n  never matter facts. Use when the user wants to add trusted knowledge, ask\n  what their wiki says, browse it, or check its health.\n---\n\n# Wiki\n\nBuild a persistent, browsable legal wiki the lawyer owns. The wiki is ordinary\nMarkdown plus a small `.wiki/` sidecar: readable in any editor and useful\nwithout a particular host, chat, or visual view.\n\nThe governing boundary is **record reusable law and method, never the matter**.\nDo not store client or party facts, matter names or numbers, or matter-document\ntitles and paths. Do not treat an unsourced inference as authority.\n\n## Start by finding the wiki\n\nResolve this skill's helper files relative to the directory containing this\nloaded `SKILL.md`: [scripts/wiki.py](scripts/wiki.py) is the entry point and\n`references/` contains its guidance. Use the absolute path derived from that\nlocation when invoking a helper, preserving the task's working directory.\nCommands below use `wiki.py` as shorthand for that entry point. Do not guess a\nrepository layout or search for a development checkout. The installed skill\ndirectory contains tools; the user's wiki location comes from the registry\nrules below. If local execution is unavailable, use the Markdown workflow.\n\nRead [the wiki layout and registry contract](references/wiki_schema.md) before\nchanging files.\n\n1. If the user named a wiki, use it.\n2. Otherwise use the current folder's wiki manifest, then the registered\n   default, then the sole registered wiki.\n3. If a registered path is unavailable, say that it needs reconnecting; never\n   create a replacement silently.\n4. Ask setup questions only when no usable wiki is registered. Set up one\n   default wiki unless the user asks for several.\n\nThe registry is operational metadata, not legal knowledge and not a playbook\npreference. A new chat must read it before asking where the wiki lives.\n\n## The four things a lawyer can do\n\nUse the user's language; these are modes, not a command vocabulary they must\nlearn.\n\n### Add\n\nAdd a trusted public source, an authorised non-matter local source, or a\nreusable insight the user expressly wants saved. Read\n[the note types](references/note_types.md) and [source policy](references/source_policy.md).\n\n“Save the reusable lessons from this conversation” is an Add request. Use the\ncurrent context once to prepare eligible, source-grounded proposals for review.\nSave no raw transcript. On a later request, check existing notes and proposals\nbefore adding newly discussed knowledge to avoid duplicates.\n\n- Classify the result as **new**, **update**, **disputed**, **no reusable\n  knowledge**, or **matter-specific**.\n- Link every load-bearing proposition to its source, pinpoint, and (where\n  useful) a short supporting extract.\n- Update related notes rather than producing near-duplicates. Do not resolve a\n  genuine legal conflict silently; place it in the review queue.\n- Return a short receipt: what changed, what was linked, and what needs review.\n\n### Ask\n\nRead the Wiki Home/index and search note titles, tags, source titles, and the\nfull text for useful synonyms before saying the wiki has no answer.\n\n- Explain whether the response is a source-backed rule, analysis, an\n  unverified note, a gap, or a disputed/outdated point.\n- Link the underlying note and its safe source reference so the lawyer can\n  check it.\n- Asking is read-only. Save a new note, answer, or link only when the user\n  asks to do so.\n\nFor “what am I missing?” or a draft comparison, identify the draft's main\nclaims, assumptions and decisions. Search the wiki separately for each, using\nsynonyms and adjacent concepts, then read the matching notes in full. Return\nonly supported omissions, contrary material, useful connections and conditional\nalternatives, each linked to its note and source. Explain why each matters to\nthe draft. Distinguish a gap in this collection from absence of evidence in the\nworld. Keep the comparison read-only; the current draft is not wiki content.\n\nDifferent positions may apply to different circumstances, objectives, dates or\njurisdictions. Explain those conditions before treating them as a conflict.\nReserve disputed status for incompatible guidance under comparable conditions.\nDo not manufacture objections or analogies when the collection supplies none.\n\nFor stored model wording, follow [Position notes and wording](references/positions.md).\nQuote the approved block exactly, including brackets, punctuation and line\nbreaks; keep explanation outside it. State source and approval status. If no\napproved block exists, report the gap rather than composing replacement text.\nApproval for storage does not establish suitability for this particular use.\n\n### Browse\n\nFor **browse, open, show, or explore the wiki**, deliver an inline reader in\nthe same turn. Prefer the host's built-in visualization skill when available;\nread and follow its current rendering, design and verification instructions.\nUse another native artifact capability if needed, or Markdown links/a table\nwhen visual rendering is unavailable. Do not merely offer a reader or return\nonly a file path. Opening a named note shows that note; **map relationships**\nrequests a relationship view grounded in the wiki's actual links.\n\nBrowse is read-only. Take the short path: resolve the wiki, obtain the eligible\npayload once, compose the native reader, verify it, and deliver. When scripts\nare available, use the browse helper; otherwise read the eligible Markdown\nnotes directly. Do not load mutation references or re-read source documents\nunless needed to resolve a specific issue. Follow the visualization skill's\nverification requirements; launch a separate preview only when those require\nit or a concrete layout/runtime uncertainty warrants it. A standalone website\nor export is a separate user request.\n\nBuild the browser from the **complete eligible wiki by default**. Use\n`wiki.py browse --json` without `--topic` or `--note`. Narrow the dataset only\nwhen the user explicitly requests a topic or note; a recent question, search\nresult, selected example or convenient sample does not define the browse scope.\nInclude every eligible note and its complete body, related notes and safe source\nlinks. Search, filters and pagination may change what is visible, but must keep\nthe full eligible dataset accessible. Never silently truncate or summarise\naway note content to fit a host's size or context limit; read in batches, or\nexplain the limit and provide access to the remaining content. Before\ndelivering, reconcile the reader's note IDs and count against the browse\npayload and check that complete bodies and sources remain accessible. State\nthe scope and included count in the handoff.\n\nThe Wiki reader's default interaction includes **text search across note titles\nand full bodies**. Add simple topic or note-type filters when the collection\nhas useful distinctions; omit redundant single-option filters. Start with an\nempty search and all notes selected, show matching/total counts when narrowed,\nand make returning to all notes straightforward. These are requested reader\ncapabilities; let the visualization skill choose the smallest fitting layout\nand native controls. Do not add dashboards or custom application chrome by\ndefault. A single-note view need not include collection search.\n\nThe visual is a view of canonical Markdown, not a second database, and must\nnot expose hidden matter metadata.\n\n### Check\n\nCheck links, source references, duplicate candidates, stale material,\nunsupported load-bearing propositions, and open conflicts. Repair only\nmechanical defects such as generated indexes or clear broken internal links.\nPut judgment calls in the review queue with a reason; do not rewrite a legal\nconclusion as a maintenance operation.\n\n## Automation is an optional enhancement\n\nManual add, ask, browse, and check are the complete normal product. Do not ask\nabout capture, hooks, matter labels, or automation during ordinary setup.\n\nAutomatic retrieval requires Codex lifecycle hooks.\n\nIn ChatGPT Work say: \"Automation cannot be enabled in ChatGPT Work; use Codex.\"\nIn any other host without active lifecycle hooks, say that automation is\nunavailable there. Do not offer to enable it or write automation playbook\nentries; manual add, ask, browse, and check remain fully available.\n\nOffer automation only after the current task has positively proved that its\nlifecycle hooks are active and trusted. Otherwise explain that the hooks must\nbe trusted and a fresh task started. Automatic retrieval is off by default.\nWhen it is off, do not read or log prompt text.\n\nWhen the user asks to enable automation, follow\n[automation settings](references/automation.md). Offer **Selected projects**\nand **All projects** equally, with neither preselected nor recommended. The\nfeature is **Bring in relevant notes**. Show one compact scope-and-feature\npreview and obtain explicit approval before saving. The short notice is: “Wiki\nwill bring in relevant notes in [chosen scope].” Include “You can change this\nor turn it off through Wiki automation settings.”\nThe scope controls where these hooks run, not which folders to ingest.\n\nIf asked about automatic saving, explain: “Wiki saves when you ask it to. You\ncan save reusable lessons from the current conversation with one request.\nAutomatic retrieval can bring existing notes into your work.” Ordinary Wiki\nuse never enables automation.\n\nFor a first-use walkthrough or starter prompts, use\n[Getting started](references/getting-started.md).\n\n## Finish well\n\nRegenerate the human-browsable Wiki Home after a change. Preserve history and\nsource references. State what is source-backed, what is analysis, and what\nneeds human review. If no reusable knowledge was found, say so plainly rather\nthan manufacturing a note.\n"
}