[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M718P8CVN728C27TC68AE25R":3,"skill-same:01M718P8CVN728C27TC68AE25R":67},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":48,"repositoryHtmlUrl":49,"repositoryHomepageUrl":6,"ownerHtmlUrl":50,"ownerBlogUrl":51,"ownerDescription":6,"updatedAt":52,"install":53,"resources":66},"01M718P8CVN728C27TC68AE25R","matter-update",null,"Append a dated event to a matter's history file and refresh the log row — captures new developments, status changes, risk re-assessments, deadline shifts, and settlement authority changes. Use when the user wants to log an update on a matter, note a development, or record a status change against the portfolio.","anthropics\u002Fclaude-for-legal","anthropics","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F76263028?v=4","01M697XGDPXJAVQ8391V2BCYTE","Anthropic","01M7189QY7HXHMC9BW4MFHPZ6H",10006,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-for-legal\u002Fblob\u002Fmain\u002Flitigation-legal\u002Fskills\u002Fmatter-update\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"matter update","update","status","portfolio","changes","change","refresh","record","log","file","when","use","authority","new","re","event","development","risk","history","brief","2026-11-10 10:12:30",false,"---\nname: matter-update\ndescription: Append a dated event to a matter's history file and refresh the log row — captures new developments, status changes, risk re-assessments, deadline shifts, and settlement authority changes. Use when the user wants to log an update on a matter, note a development, or record a status change against the portfolio.\nargument-hint: \"[slug] [brief event description]\"\n---\n\n# \u002Fmatter-update\n\n1. Follow the workflow and reference below.\n2. Confirm slug exists in `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flitigation-legal\u002Fmatters\u002F` and `_log.yaml`.\n3. Prompt for event type, date (default today), summary, and any log field updates (risk change, status change, next deadline shift, materiality reclassification).\n4. Append dated entry to `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flitigation-legal\u002Fmatters\u002F[slug]\u002Fhistory.md`.\n5. Update `_log.yaml` — set `last_updated` to today, apply any field updates.\n6. Confirm.\n\n---\n\n# Matter Update\n\n## Purpose\n\nThe portfolio only stays useful if it stays current. This skill makes logging an update cheap — two minutes of structured capture, no freeform drift.\n\n## Load context\n\n- `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flitigation-legal\u002Fmatters\u002F_log.yaml` — find the row\n- `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flitigation-legal\u002Fmatters\u002F[slug]\u002Fhistory.md` — append target\n- `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flitigation-legal\u002Fmatters\u002F[slug]\u002Fmatter.md` — reference (don't rewrite)\n- `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flitigation-legal\u002FCLAUDE.md` — risk calibration (if re-assessing risk)\n\n**Conflicts gate — unbypassable.** Before logging an update, check `_log.yaml` for the matter slug. If the matter is not in `_log.yaml`, refuse and route:\n\n> \"I don't see [matter slug] in the matter log. Run `\u002Flitigation-legal:matter-intake` first so the conflicts check runs and the matter workspace exists. I won't append history to an unmanaged matter — the conflicts check is the gate, and there's no `history.md` to append to until the matter is intaken.\"\n\n## Input\n\nSlug (required). If not provided, ask — with a short list of recently updated matters to pick from.\n\n## The update\n\n### 1. Event type\n\nOffer categories:\n\n- **Procedural** — motion filed\u002Freceived, order issued, hearing held, deadline set\n- **Discovery** — production made\u002Freceived, depositions taken, subpoena served\n- **Substantive** — new facts, key document surfaced, ruling on merits\n- **Strategy** — posture shift, settlement offer made\u002Freceived, authority update\n- **Risk re-assessment** — severity or likelihood changed\n- **Stakeholder** — new person looped in, outside counsel change\n- **Administrative** — engagement letter executed, budget adjusted, hold refreshed\n\nOr freeform if none fits.\n\n### 2. Date\n\nDefault today. Accept an override (e.g., capturing an event from last week).\n\n### 3. Summary\n\nOne-paragraph narrative. What happened, what it means, any immediate implication.\n\n### 4. Log field changes\n\nWalk through potentially affected fields:\n\n- `status:` — has the stage shifted (e.g., pleadings → fact discovery)?\n- `stage:` — substage update\n- `risk:` — reassessment required?\n- `materiality:` — any change (new facts might trigger reserve or disclosure)?\n- `exposure_range:` — revise if new information\n- `next_deadline:` — new upcoming date, if any\n- `outside_counsel:` — change?\n- `internal_owners:` — anyone new or removed?\n- `legal_hold:` — refreshed, expanded, released?\n\nOnly prompt for fields likely affected by the event type. Procedural updates usually touch `stage` and `next_deadline` only; a settlement offer might touch `materiality`, `exposure_range`, `status`.\n\n### 4pre. Settlement-acceptance gate\n\nIf the Strategy update is a **settlement acceptance** (the company is accepting a settlement offer, executing a settlement agreement, or authorizing acceptance in principle — not merely logging an offer made or received): Read `## Who's using this` in `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flitigation-legal\u002FCLAUDE.md`. If the Role is Non-lawyer:\n\n> Accepting a settlement has legal consequences — it resolves claims, typically requires a release, and can affect insurance, tax, and related matters. Have you reviewed this with an attorney? If yes, proceed. If no, here's a brief to bring to them:\n>\n> [Generate a 1-page summary: the matter, proposed settlement terms (dollar, structural, release scope, confidentiality, non-disparagement), exposure at stake, authority ladder status (see `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flitigation-legal\u002FCLAUDE.md` settlement authority), what could go wrong, what to ask the attorney before accepting.]\n>\n> If you need to find a licensed attorney, solicitor, barrister, or other authorised legal professional in your jurisdiction: your professional regulator's referral service is the fastest starting point (state bar in the US, SRA\u002FBar Standards Board in England & Wales, Law Society in Scotland\u002FNI\u002FIreland\u002FCanada\u002FAustralia, or your jurisdiction's equivalent).\n\nDo not log the acceptance or flip materiality on acceptance basis without an explicit yes. Logging offers or counters does not require the gate — acceptance does.\n\n### 4a. Materiality trigger — explicit prompt\n\nCertain event types force a materiality re-check. When the event type is in this list, **always prompt** — don't let the user move on without an explicit answer:\n\n| Event type | Materiality trigger prompt |\n|---|---|\n| Substantive (new facts, key document, merits ruling) | \"This event is substantive. Does it push `materiality`? Current: `[current]`. Options: `reserved \u002F disclosed \u002F monitored \u002F none`. Change?\" |\n| Strategy (posture shift, settlement offer made or received) | \"Settlement activity often triggers materiality reclassification. Current: `[current]`. If the offer, counter, or acceptance moves exposure or shifts from contested to probable-and-estimable, reclassify.\" |\n| Risk re-assessment (severity or likelihood changed) | \"Risk moved. Materiality should track. Current: `[current]`. Reclassify?\" |\n| Regulatory \u002F enforcement development | \"Regulator action (subpoena, CID, enforcement notice) usually triggers disclosure analysis. Current: `[current]`. Change?\" |\n\nAcceptable answers include `no change` — but `no change` must be explicit, not implied by silence. Capture in the history entry:\n\n```markdown\n**Materiality check:** [no change \u002F changed from X to Y]\n**Reasoning:** [one sentence]\n```\n\nIf materiality moves to `reserved` or `disclosed`, and the matter did not previously carry a reserve or disclosure, flag the event as requiring finance \u002F audit-committee notification per `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flitigation-legal\u002FCLAUDE.md` materiality thresholds.\n\n### 5. Seed doc prompt (optional)\n\nIf the update references a document (order, filing, correspondence), ask if there's a path to link. Not pushy.\n\n## Writing\n\n### Append to `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flitigation-legal\u002Fmatters\u002F[slug]\u002Fhistory.md`\n\nMost recent at top, directly under the `---` that follows the header.\n\n```markdown\n## [YYYY-MM-DD] — [Event type]: [short title]\n\n[Paragraph summary.]\n\n**Fields changed:**\n- [field]: [old → new]\n- [field]: [old → new]\n\n**Related doc:** [path, if provided]\n```\n\nIf no fields changed, omit the \"Fields changed\" block.\n\n### Update `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flitigation-legal\u002Fmatters\u002F_log.yaml`\n\n- Apply any field changes.\n- Set `last_updated: [today]` (or the event date if the user overrode — the log tracks when the record was last touched).\n\n## Confirm\n\nShow the user the history entry and the yaml diff before writing:\n\n> Here's what I'll append and update. Good to commit?\n\n## What this skill does not do\n\n- Edit past history entries. Corrections are new entries that reference and correct prior ones.\n- Silently change the log. Every field change is shown to the user before write.\n- Decide whether a new development warrants reserve\u002Fdisclosure. It surfaces the question (\"this might push materiality — want to reclassify?\"), the user answers.\n","# \u002Fmatter-update\n\n1. Follow the workflow and reference below.\n2. Confirm slug exists in `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flitigation-legal\u002Fmatters\u002F` and `_log.yaml`.\n3. Prompt for event type, date (default today), summary, and any log field updates (risk change, status change, next deadline shift, materiality reclassification).\n4. Append dated entry to `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flitigation-legal\u002Fmatters\u002F[slug]\u002Fhistory.md`.\n5. Update `_log.yaml` — set `last_updated` to today, apply any field updates.\n6. Confirm.\n\n---\n\n# Matter Update\n\n## Purpose\n\nThe portfolio only stays useful if it stays current. This skill makes logging an update cheap — two minutes of structured capture, no freeform drift.\n\n## Load context\n\n- `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flitigation-legal\u002Fmatters\u002F_log.yaml` — find the row\n- `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flitigation-legal\u002Fmatters\u002F[slug]\u002Fhistory.md` — append target\n- `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flitigation-legal\u002Fmatters\u002F[slug]\u002Fmatter.md` — reference (don't rewrite)\n- `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flitigation-legal\u002FCLAUDE.md` — risk calibration (if re-assessing risk)\n\n**Conflicts gate — unbypassable.** Before logging an update, check `_log.yaml` for the matter slug. If the matter is not in `_log.yaml`, refuse and route:\n\n> \"I don't see [matter slug] in the matter log. Run `\u002Flitigation-legal:matter-intake` first so the conflicts check runs and the matter workspace exists. I won't append history to an unmanaged matter — the conflicts check is the gate, and there's no `history.md` to append to until the matter is intaken.\"\n\n## Input\n\nSlug (required). If not provided, ask — with a short list of recently updated matters to pick from.\n\n## The update\n\n### 1. Event type\n\nOffer categories:\n\n- **Procedural** — motion filed\u002Freceived, order issued, hearing held, deadline set\n- **Discovery** — production made\u002Freceived, depositions taken, subpoena served\n- **Substantive** — new facts, key document surfaced, ruling on merits\n- **Strategy** — posture shift, settlement offer made\u002Freceived, authority update\n- **Risk re-assessment** — severity or likelihood changed\n- **Stakeholder** — new person looped in, outside counsel change\n- **Administrative** — engagement letter executed, budget adjusted, hold refreshed\n\nOr freeform if none fits.\n\n### 2. Date\n\nDefault today. Accept an override (e.g., capturing an event from last week).\n\n### 3. Summary\n\nOne-paragraph narrative. What happened, what it means, any immediate implication.\n\n### 4. Log field changes\n\nWalk through potentially affected fields:\n\n- `status:` — has the stage shifted (e.g., pleadings → fact discovery)?\n- `stage:` — substage update\n- `risk:` — reassessment required?\n- `materiality:` — any change (new facts might trigger reserve or disclosure)?\n- `exposure_range:` — revise if new information\n- `next_deadline:` — new upcoming date, if any\n- `outside_counsel:` — change?\n- `internal_owners:` — anyone new or removed?\n- `legal_hold:` — refreshed, expanded, released?\n\nOnly prompt for fields likely affected by the event type. Procedural updates usually touch `stage` and `next_deadline` only; a settlement offer might touch `materiality`, `exposure_range`, `status`.\n\n### 4pre. Settlement-acceptance gate\n\nIf the Strategy update is a **settlement acceptance** (the company is accepting a settlement offer, executing a settlement agreement, or authorizing acceptance in principle — not merely logging an offer made or received): Read `## Who's using this` in `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flitigation-legal\u002FCLAUDE.md`. If the Role is Non-lawyer:\n\n> Accepting a settlement has legal consequences — it resolves claims, typically requires a release, and can affect insurance, tax, and related matters. Have you reviewed this with an attorney? If yes, proceed. If no, here's a brief to bring to them:\n>\n> [Generate a 1-page summary: the matter, proposed settlement terms (dollar, structural, release scope, confidentiality, non-disparagement), exposure at stake, authority ladder status (see `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flitigation-legal\u002FCLAUDE.md` settlement authority), what could go wrong, what to ask the attorney before accepting.]\n>\n> If you need to find a licensed attorney, solicitor, barrister, or other authorised legal professional in your jurisdiction: your professional regulator's referral service is the fastest starting point (state bar in the US, SRA\u002FBar Standards Board in England & Wales, Law Society in Scotland\u002FNI\u002FIreland\u002FCanada\u002FAustralia, or your jurisdiction's equivalent).\n\nDo not log the acceptance or flip materiality on acceptance basis without an explicit yes. Logging offers or counters does not require the gate — acceptance does.\n\n### 4a. Materiality trigger — explicit prompt\n\nCertain event types force a materiality re-check. When the event type is in this list, **always prompt** — don't let the user move on without an explicit answer:\n\n| Event type | Materiality trigger prompt |\n|---|---|\n| Substantive (new facts, key document, merits ruling) | \"This event is substantive. Does it push `materiality`? Current: `[current]`. Options: `reserved \u002F disclosed \u002F monitored \u002F none`. Change?\" |\n| Strategy (posture shift, settlement offer made or received) | \"Settlement activity often triggers materiality reclassification. Current: `[current]`. If the offer, counter, or acceptance moves exposure or shifts from contested to probable-and-estimable, reclassify.\" |\n| Risk re-assessment (severity or likelihood changed) | \"Risk moved. Materiality should track. Current: `[current]`. Reclassify?\" |\n| Regulatory \u002F enforcement development | \"Regulator action (subpoena, CID, enforcement notice) usually triggers disclosure analysis. Current: `[current]`. Change?\" |\n\nAcceptable answers include `no change` — but `no change` must be explicit, not implied by silence. Capture in the history entry:\n\n```markdown\n**Materiality check:** [no change \u002F changed from X to Y]\n**Reasoning:** [one sentence]\n```\n\nIf materiality moves to `reserved` or `disclosed`, and the matter did not previously carry a reserve or disclosure, flag the event as requiring finance \u002F audit-committee notification per `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flitigation-legal\u002FCLAUDE.md` materiality thresholds.\n\n### 5. Seed doc prompt (optional)\n\nIf the update references a document (order, filing, correspondence), ask if there's a path to link. Not pushy.\n\n## Writing\n\n### Append to `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flitigation-legal\u002Fmatters\u002F[slug]\u002Fhistory.md`\n\nMost recent at top, directly under the `---` that follows the header.\n\n```markdown\n## [YYYY-MM-DD] — [Event type]: [short title]\n\n[Paragraph summary.]\n\n**Fields changed:**\n- [field]: [old → new]\n- [field]: [old → new]\n\n**Related doc:** [path, if provided]\n```\n\nIf no fields changed, omit the \"Fields changed\" block.\n\n### Update `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flitigation-legal\u002Fmatters\u002F_log.yaml`\n\n- Apply any field changes.\n- Set `last_updated: [today]` (or the event date if the user overrode — the log tracks when the record was last touched).\n\n## Confirm\n\nShow the user the history entry and the yaml diff before writing:\n\n> Here's what I'll append and update. Good to commit?\n\n## What this skill does not do\n\n- Edit past history entries. Corrections are new entries that reference and correct prior ones.\n- Silently change the log. Every field change is shown to the user before write.\n- Decide whether a new development warrants reserve\u002Fdisclosure. It surfaces the question (\"this might push materiality — want to reclassify?\"), the user answers.\n",{"name":5,"description":7,"argument-hint":44},"[slug] [brief event description]","main","4a6c651889c97cc9140580363c73e0eb17379c2b","litigation-legal\u002Fskills\u002Fmatter-update",1968,"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-for-legal","https:\u002F\u002Fgithub.com\u002Fanthropics","https:\u002F\u002Fanthropic.com","2026-11-14 23:30:58",{"source":8,"skillName":5,"commands":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add anthropics\u002Fclaude-for-legal --skill matter-update",{"tool":59,"command":60},"bunx","bunx skills add anthropics\u002Fclaude-for-legal --skill matter-update",{"tool":62,"command":63},"pnpm","pnpm dlx skills add anthropics\u002Fclaude-for-legal --skill matter-update","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-for-legal\u002Fblob\u002Fmain\u002Flitigation-legal\u002Fskills\u002Fmatter-update\u002FSKILL.md",true,[],[68,95,117,135,157,168],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":79,"publishedAt":39},"01M718SG9G2R92ECCD0HYK2R5E","reg-feed-watcher","Check regulatory feeds now and report what's new since the last check, filtered by your materiality threshold. Use when the user says \"check the feeds\", \"what's new\", \"regulatory update\", when running from the scheduled agent, or when manually pasting a regulatory development for classification and diff.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-for-legal\u002Fblob\u002Fmain\u002Fregulatory-legal\u002Fskills\u002Freg-feed-watcher\u002FSKILL.md",[74],{"categoryNo":75,"categoryName":76,"taxonomyType":77,"taxonomyTypeDesc":78},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[80,81,82,83,84,85,86,35,87,88,32,89,30,90,29,91,92,20,93,94],"reg","watcher","reg feed watcher","running","feeds","filtered","diff","for","classification","now","scheduled","check","last","report","regulatory",{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":39},"01M718SCRTBN55DMTVSPG67A7N","policy-redraft","Produce a proposed marked-up policy redraft that closes a gap found by \u002Fregulatory-legal:gaps or \u002Fregulatory-legal:policy-diff. A first draft for internal review — not for direct application to approved policy documents. Use when the user says \"redraft the policy\", \"draft the policy fix\", \"mark up the policy\", or when gap-surfacer hands off a gap for drafting.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-for-legal\u002Fblob\u002Fmain\u002Fregulatory-legal\u002Fskills\u002Fpolicy-redraft\u002FSKILL.md",[],[102,103,86,87,104,105,106,30,107,29,108,109,110,111,112,113,114,115,94,116],"policy","policy redraft","up","fix","produce","documents","drafting","gaps","review","draft","id","gap","mark","first","direct",{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":39},"01M718S8RV0C4NMVKG078CBFXP","policy-diff","Diff a specific regulatory change against the indexed policy library. Use when a reg has changed and you need to know which policies it touches and what the gap is, when the user says \"diff this reg against our policies\", \"which policy does this affect\", or \"gap analysis\", or when reg-feed-watcher hands off a material item.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-for-legal\u002Fblob\u002Fmain\u002Fregulatory-legal\u002Fskills\u002Fpolicy-diff\u002FSKILL.md",[],[86,102,124,125,29,126,127,80,128,81,24,129,130,131,30,132,113,133,134,94],"policy diff","which","you","analysis","text","paste","library","material","gap analysis","what the","name",{"skillNo":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":139,"categories":140,"keywords":141,"publishedAt":39},"01M718S6521Y0FT4T24VCFKVG5","matter-workspace","Manage matter workspaces — create, list, switch, close, or detach the active matter (practice-level). Use when working across multiple clients or matters and you need to keep one engagement's context separate from another, or when a substantive skill needs to know which matter it's working in.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-for-legal\u002Fblob\u002Fmain\u002Fregulatory-legal\u002Fskills\u002Fmatter-workspace\u002FSKILL.md",[],[142,143,125,144,145,146,32,30,29,126,147,148,149,150,151,152,153,154,155,156],"workspace","matter workspace","switch","manage","workspaces","keep","across","create","engagement","close","active","clients","list","it","context",{"skillNo":158,"name":109,"nameZh":6,"description":159,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":160,"categories":161,"keywords":162,"publishedAt":39},"01M718S3FPEJNQGCMQ1AR8M4HE","Open gaps tracker — what's flagged and not yet closed. Use when the user asks \"what gaps are open\", \"gap tracker\", \"remediation status\", or wants to close (--close GAP-ID) or risk-accept (--accept GAP-ID) a tracked gap.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-for-legal\u002Fblob\u002Fmain\u002Fregulatory-legal\u002Fskills\u002Fgaps\u002FSKILL.md",[],[109,112,113,36,151,163,164,21,165,30,166,29,167],"tracker","remediation","open","accept","user",{"skillNo":169,"name":170,"nameZh":6,"description":171,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":172,"categories":173,"keywords":179,"publishedAt":39},"01M718S06WSZ9Y24JKYM0VVPPE","gap-surfacer","Reference: shared gap- and comment-tracker framework backing \u002Fregulatory-legal:gaps and \u002Fregulatory-legal:comments. Tracks open policy gaps with remediation status, ingests gaps from policy-diff, surfaces what's open and aging, routes to owners, and notifies gap owners via Slack with per-send confirmation. Loaded by the gaps and comments skills before doing substantive work.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-for-legal\u002Fblob\u002Fmain\u002Fregulatory-legal\u002Fskills\u002Fgap-surfacer\u002FSKILL.md",[174],{"categoryNo":175,"categoryName":176,"taxonomyType":177,"taxonomyTypeDesc":178},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[113,180,181,182,86,102,183,165,184,185,186,187,109,188,189,190,191,163,164,192],"gap surfacer","shared","tracks","send","confirmation","aging","false","comments","with","work","slack","via","surfaces"]