[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M718CQJDCX96TQQV1CCZFHJ9":3,"skill-same:01M718CQJDCX96TQQV1CCZFHJ9":81},{"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":31,"publishedAt":52,"linkOnly":53,"markdownContent":54,"markdownBody":55,"frontMatter":56,"refName":59,"commitSha":60,"skillDirectory":61,"forksCount":62,"repositoryHtmlUrl":63,"repositoryHomepageUrl":6,"ownerHtmlUrl":64,"ownerBlogUrl":65,"ownerDescription":6,"updatedAt":66,"install":67,"resources":80},"01M718CQJDCX96TQQV1CCZFHJ9","entity-compliance",null,"Entity compliance tracker — initialize, report upcoming deadlines, update status, run health audit, export to CSV. Maintains a compliance-tracker.yaml built from the entity table, calculates filing deadlines by entity and jurisdiction, and surfaces what's due in the next 30\u002F60\u002F90 days. Use when user says \"entity compliance\", \"filing deadlines\", \"annual reports due\", \"entity tracker\", \"what filings are due\", \"entity health\", or \"good standing\".","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\u002Fcorporate-legal\u002Fskills\u002Fentity-compliance\u002FSKILL.md",[18,23,28],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000004","电子表格","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",{"categoryNo":29,"categoryName":30,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000037","律师与法务",[32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51],"entity compliance","entity","compliance","run","tracker","audit","next","health","reports","health audit","sweep","csv","compliance tracker","when","use","init","good","filing","filings","initialize","2026-11-10 10:12:30",false,"---\nname: entity-compliance\ndescription: >\n  Entity compliance tracker — initialize, report upcoming deadlines, update\n  status, run health audit, export to CSV. Maintains a compliance-tracker.yaml\n  built from the entity table, calculates filing deadlines by entity and\n  jurisdiction, and surfaces what's due in the next 30\u002F60\u002F90 days. Use when\n  user says \"entity compliance\", \"filing deadlines\", \"annual reports due\",\n  \"entity tracker\", \"what filings are due\", \"entity health\", or \"good standing\".\nargument-hint: \"[--init | --report [--days N] | --update [--from-report] | --sweep | --audit | --export [--format csv|table]]\"\n---\n\n# \u002Fentity-compliance\n\n1. Load `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002FCLAUDE.md` → `## Entity Management` (entity table, jurisdictions, registered agent).\n2. Route to the correct mode below based on flag:\n   - No flag or `--init`: Mode 1 — initialize tracker from entity table\n   - `--report`: Mode 2 — surface upcoming deadlines and overdue items\n   - `--update`: Mode 3a (manual) or 3b (--from-report upload) — update status\n   - `--sweep`: Mode 3c — walk through unknown\u002Foverdue items one by one\n   - `--audit`: Mode 4 — full health audit\n   - `--export`: Mode 5 — produce CSV or table export\n3. Read\u002Fwrite `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002Fentities\u002Fcompliance-tracker.yaml`.\n4. After any update: show summary of changes and next action.\n\n---\n\n## Purpose\n\nAnnual reports, franchise taxes, Statements of Information, biennial filings —\nevery entity in every state has its own schedule and its own consequences for\nmissing the deadline. This skill maintains a single YAML tracker that knows\nwhat's due, when, and for which entity. It's lightweight by design: the tracker\nis a file you own, Claude updates it on command, and you export it when you need\nto share it.\n\n## Important: deadline reference caveat\n\n> The filing deadlines in this skill's reference table reflect publicly available\n> requirements as of the skill's build date. State filing requirements and due\n> dates can change. **Always confirm deadlines with your registered agent or\n> directly with the relevant Secretary of State before relying on them for\n> compliance purposes.** If you use CT Corp, National Registered Agents, or\n> another registered agent service, their compliance calendar is authoritative\n> for your specific entities — use this tracker to organize and surface their\n> data, not to replace it.\n\n## Jurisdiction assumption\n\n> This tracker computes deadlines against the state or country of formation \u002F qualification recorded per entity. Filing rules, due-date mechanics, and fee structures vary materially by jurisdiction. If an entity's actual footprint differs from what's in `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002FCLAUDE.md` (undisclosed foreign qualification, dissolved entities, jurisdictional re-domestication, international filings managed by a local agent), the output may not apply as written — confirm with the registered agent or local counsel for that jurisdiction.\n\n## Entity-type disambiguation (especially Delaware)\n\n> The filing calendar depends on **entity type**, not just jurisdiction. Treating a \"Delaware entity\" as a single bucket is a common and consequential error — DE corporations, DE LLCs, and DE LPs have different filings, different deadlines, and different consequences for a miss. Confirm the entity type from the entity table before computing or reporting a deadline, and never copy a deadline from one entity-type to another in the same state.\n>\n> **Delaware — the split that matters:**\n>\n> - **DE Corporation (Inc., Corp.):** Annual report AND franchise tax, both due **March 1**. Franchise tax is calculated by the authorized-shares method or the assumed-par-value capital method (whichever is lower); the annual report captures director \u002F officer information. Statutory basis: 8 Del. C. §§ 501–502 [verify current].\n> - **DE LLC:** No annual report required. Annual tax is a **flat $300**, due **June 1**. Statutory basis: 6 Del. C. § 18-1107(d) [verify current fee and date].\n> - **DE LP:** No annual report required. Annual tax is a **flat $300**, due **June 1** (parallel to the LLC rule). Statutory basis: 6 Del. C. § 17-1109 [verify current].\n>\n> A DE LLC is NOT required to file a March 1 annual report — writing that deadline for an LLC carries real risk (spurious \"overdue\" flags that mask actual June 1 exposure, or worse, the inverse: a user who treats the March 1 corporation rule as universal and misses the June 1 LLC deadline). If the entity table records a Delaware entity without a type, flag it as `type_unknown` and ask the user to confirm before computing either deadline.\n>\n> The same entity-type discipline applies in every other jurisdiction with divergent filing regimes by entity type (e.g., CA corp Statement of Information vs. CA LLC SOI cadence; TX franchise tax applies to corporations, LLCs, and LPs but with different no-tax-due thresholds). When the reference table for a jurisdiction is populated, make sure it is indexed by entity type, not just by state.\n\n---\n\n## Tracker file\n\nLives at `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002Fentities\u002Fcompliance-tracker.yaml`. Structure:\n\n```yaml\n# Entity Compliance Tracker\n# Generated: [date]\n# Last updated: [date]\n# Disclaimer: deadlines are reference only — confirm with registered agent or Secretary of State\n\nmetadata:\n  company: \"[Company Name]\"\n  generated: \"[date]\"\n  last_updated: \"[date]\"\n  last_audit: \"[date or null]\"\n\ncustom_jurisdictions:   # manually added — US states or countries not in built-in reference table\n  []                    # populated when a new jurisdiction is encountered\n\nentities:\n  - name: \"[Entity Name]\"\n    type: \"[Corporation \u002F LLC \u002F LP \u002F other]\"\n    state_of_formation: \"[state]\"\n    formation_date: \"[date or null]\"\n    status: \"[active \u002F dormant \u002F dissolving]\"\n    registered_agent: \"[CT Corp \u002F National \u002F in-house \u002F other]\"\n    notes: \"\"\n\n    jurisdictions:\n      - state: \"[state]\"\n        qualification: \"[domestic \u002F foreign]\"\n        qualified_date: \"[date or null]\"\n        agent_managed: false   # set true for international entities where a local agent handles compliance\n        local_agent: \"[name or null]\"\n        filings:\n          - type: \"[Annual Report \u002F Franchise Tax \u002F Statement of Information \u002F Biennial Statement \u002F other]\"\n            due_date: \"[YYYY-MM-DD]\"\n            due_basis: \"[fixed date \u002F anniversary month \u002F other]\"\n            last_filed: \"[date or null]\"\n            last_fee: \"[amount or null]\"\n            status: \"[current \u002F due_soon \u002F overdue \u002F unknown]\"\n            confirmed_good_standing: \"[date or null]\"\n            notes: \"\"\n```\n\nStatus values:\n- `current` — filed for current period, nothing due within 90 days\n- `due_soon` — due within 90 days\n- `overdue` — past due date with no filed date recorded\n- `unknown` — no information; needs manual confirmation\n\n---\n\n## Mode 1: Initialise\n\nRun when no tracker exists, or with `--rebuild` to regenerate from scratch.\n\n### Step 1: Load entity table\n\nRead `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002FCLAUDE.md` → `## Entity Management` → Entity table. If the entity table\nis populated (from org chart upload at cold-start), use it directly. If not,\nask the user to either run the cold-start module or provide the entity list.\n\n### Step 2: For each entity × jurisdiction, confirm the filing requirements\n\nFor each entity, confirm the current filing schedule with the registered agent or the relevant Secretary of State. State filing schedules change (some states move from fixed dates to anniversary-based schedules and back, fee structures are revised, filing categories are reclassified). Do not rely on a cached schedule. The tracker below records the dates you confirm; update them when your registered agent sends reminders.\n\nFor each jurisdiction where the entity is registered (domestic or foreign):\n\n1. Ask the user whether they have a current compliance report from the registered agent — that's the most authoritative source.\n2. If not, ask the user what they know (filing type, due-date basis, last filed date, typical fee). Record what they provide.\n3. For anything the user does not know, flag the entity × jurisdiction entry as `unknown` — do not populate dates from a cached reference. The user's next step is to confirm with the registered agent or Secretary of State.\n\n**Capture details in the tracker rather than a reference table:**\n\n> I don't have filing requirements for [Jurisdiction] in the reference table.\n> Let me capture them so we can track this going forward.\n>\n> For [Entity] in [Jurisdiction]:\n> 1. What type of filing is required? (Annual report, franchise tax, confirmation\n>    statement, annual return, or something else?)\n> 2. When is it due? (Fixed date like May 1, anniversary month, or other?)\n> 3. What's the typical fee? (Approximate is fine — or \"unknown\".)\n> 4. Who is your registered agent or local filing agent there?\n\nStore the answer in a `custom_jurisdictions` block in the tracker:\n\n```yaml\ncustom_jurisdictions:\n  - jurisdiction: \"[State \u002F Country]\"\n    jurisdiction_type: \"[US state \u002F Canada province \u002F EU member state \u002F other]\"\n    filings:\n      - type: \"[filing type]\"\n        due_basis: \"[fixed: MM-DD \u002F anniversary month \u002F other description]\"\n        typical_fee: \"[amount or unknown]\"\n        notes: \"[any other relevant information — e.g., local agent required, filing in local language]\"\n    added_by: \"manual\"\n    added_date: \"[date]\"\n```\n\nThis custom definition is then applied to all entities in that jurisdiction.\nFuture `--init` runs and entity additions will use it automatically.\n\n**International jurisdictions specifically:**\n\nInternational filings vary enormously by jurisdiction. Always go through the\ncustom definition flow above — confirm the filing type, cadence, and fee with\nthe local filing agent or registered office agent before populating the tracker.\n\nFor international entities, also ask:\n- Is there a local filing agent or registered office agent handling compliance?\n  If yes, note the agent name — the tracker can flag when to follow up with them\n  rather than calculating due dates independently.\n- Is the entity required to file any group-level reports in this jurisdiction\n  (e.g., country-by-country reporting, beneficial ownership registers,\n  economic substance filings)?\n\nFlag international entities with a local agent as `agent_managed: true` in the\ntracker. The report mode will list them separately with a note to confirm status\nwith the local agent rather than showing a calculated due date.\n\nFor anniversary-based filings: calculate from the formation_date in the tracker.\nIf formation_date is null: set status to `unknown` and flag for confirmation.\n\n### Step 3: Write the tracker\n\nGenerate `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002Fentities\u002Fcompliance-tracker.yaml` with all entities and their\ncalculated filing requirements. Set initial status:\n- `current` if last_filed is within the current filing period\n- `due_soon` if due within 90 days and no last_filed for current period\n- `overdue` if due date has passed and no last_filed for current period\n- `unknown` if formation_date is missing or state is not in reference table\n\nShow a summary after generating:\n\n```\nEntity compliance tracker initialized.\n\nEntities: [N]\nTotal jurisdictions: [N]\nFilings tracked: [N]\n\nStatus summary:\n  ✅ Current:   [N]\n  ⏰ Due soon:  [N] (next 90 days)\n  🔴 Overdue:   [N]\n  ❓ Unknown:   [N] (confirm with registered agent)\n\nRun \u002Fcorporate-legal:entity-compliance --report to see what's due.\n```\n\n---\n\n## Mode 2: Report\n\nSurfaces upcoming deadlines and flags overdue items. Default: next 90 days.\n\n```\n\u002Fcorporate-legal:entity-compliance --report [--days 30|60|90|180]\n```\n\nOutput format:\n\n```\nENTITY COMPLIANCE REPORT — [date]\n[Company Name]\n\n🔴 OVERDUE ([N]):\n  [Entity] \u002F [State] \u002F [Filing type] — was due [date]\n\n⏰ DUE WITHIN [N] DAYS ([N]):\n  [Entity] \u002F [State] \u002F [Filing type] — due [date]  [registered agent]\n  [Entity] \u002F [State] \u002F [Filing type] — due [date]\n\n✅ RECENTLY FILED ([N] in last 90 days):\n  [Entity] \u002F [State] \u002F [Filing type] — filed [date]\n\n❓ UNKNOWN STATUS ([N]):\n  [Entity] \u002F [State] \u002F [Filing type] — no information; confirm with registered agent\n\n🌐 AGENT-MANAGED ([N]):\n  [Entity] \u002F [Country] \u002F [Filing type] — managed by [local agent]; confirm status directly\n  [Entity] \u002F [Country] — no local agent recorded; add one with --update\n\nGOOD STANDING:\n  Last confirmed: [date]\n  Entities with confirmed good standing: [N] of [total]\n  Entities not confirmed in last 12 months: [list]\n```\n\nIf the tracker covers more than ~10 entities, or any time the user asks: offer the dashboard (see CLAUDE.md `## Outputs → Dashboard offer for data-heavy outputs`). Shape the offer for this output — counts by filing status (overdue \u002F due soon \u002F filed \u002F unknown), counts by good-standing state, and a sortable entity table with jurisdiction, filing type, and next due date.\n\n---\n\n## Mode 3: Update\n\nUpdates one or more entities in the tracker. Three sub-modes:\n\n### Consequential-action gate (file SOI \u002F annual report)\n\n**Before directing or confirming a filing:** Read `## Who's using this` in `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002FCLAUDE.md`. If the Role is **Non-lawyer**:\n\n> Filing a Statement of Information, annual report, or franchise tax return with a Secretary of State has legal consequences — it's a formal representation from the entity, it carries fees, and missed or incorrect filings can cause loss of good standing or franchise-tax defaults. Have you reviewed this with an attorney (or a qualified registered agent) before filing? If yes, proceed to record the filing. If no, here's a brief to bring to them:\n>\n> - Entity, jurisdiction, filing type, and due date\n> - What the tracker says about the last filing (date, fee, officer\u002Fdirector information last reported)\n> - Open questions (is the officer\u002Fdirector information still accurate; has the registered agent changed; has the principal office changed)\n> - What could go wrong (out-of-date officer information, missed deadline triggering franchise tax or dissolution, fee calculation error)\n> - What to ask the attorney (is a filing actually needed this year; are there any charter amendments or officer changes that need to be reflected; who should sign)\n>\n> If you need to find an attorney, solicitor, barrister, or other authorised legal professional: contact your professional regulator (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) for a referral service.\n\nDo not record a new `last_filed` date past this gate without an explicit yes. Tracker reads, deadline reports, and \"what's due soon\" output do not require the gate.\n\n### 3a: Manual update\n\n```\n\u002Fcorporate-legal:entity-compliance --update\n```\n\nAttorney tells Claude what was filed:\n> \"We filed the Delaware annual report for [Entity] on March 1. Fee was $450.\"\n\nClaude updates:\n- `last_filed` → March 1 date\n- `last_fee` → $450\n- `status` → `current`\n- `last_updated` in metadata\n\n### 3b: Registered agent report upload\n\n```\n\u002Fcorporate-legal:entity-compliance --update --from-report\n```\n\nUser uploads a CT Corp, National Registered Agents, or similar compliance\nreport (PDF, CSV, or Excel). Claude reads it and updates matching entities:\n\nFrom the report, extract for each entity:\n- Filing type and due date\n- Last filed date (if present)\n- Good standing status and date confirmed\n- Any flags or warnings from the agent\n\nMatch report entities to tracker entities by name (flag near-matches for\nconfirmation — \"Acme Holdings LLC\" vs. \"Acme Holdings, LLC\" are probably\nthe same entity).\n\nAfter processing:\n```\nUpdated [N] entities from report.\n\nMatched: [N]\nUnmatched (in report, not in tracker): [list — may need to add to entity table]\nNot in report (in tracker, no update): [list — status unchanged]\n```\n\n### 3c: Bulk status sweep\n\n```\n\u002Fcorporate-legal:entity-compliance --sweep\n```\n\nWalks through each entity with `unknown` or `overdue` status and asks for\ncurrent information one at a time:\n\n> [Entity] \u002F [State] \u002F [Filing type] — currently showing as [status].\n> Has this been filed? If yes, when and what was the fee?\n\nUpdates tracker after each confirmation. Produces a completion summary.\n\n---\n\n## Mode 4: Health audit\n\n```\n\u002Fcorporate-legal:entity-compliance --audit\n```\n\nBroader review beyond just filing status. Surfaces:\n\n**Filing compliance:**\n- Overdue items (from report mode)\n- Unknown status items\n\n**Entity health:**\n- Entities marked as `dormant` — flag for review: should these be dissolved?\n  Carrying dormant entities costs money (annual fees, registered agent fees)\n  and creates ongoing compliance obligations.\n- Entities with formation_date older than 5 years and status `dormant` — flag\n  as dissolution candidates.\n- Entities missing formation_date — flag as data gap.\n\n**Good standing gaps:**\n- Entities with no `confirmed_good_standing` date — unknown whether in good\n  standing; risk if a transaction requires a certificate on short notice.\n- Entities with `confirmed_good_standing` older than 12 months — stale; worth\n  refreshing, especially if M&A or financing is anticipated.\n\n**Foreign qualification gaps:**\n- Based on `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002FCLAUDE.md` entity table: are there states in the company's\n  operational footprint (offices, employees) where entities are not foreign\n  qualified? This requires the attorney to confirm operational presence —\n  Claude can flag the question but cannot determine presence independently.\n\n**Intercompany agreement gaps:**\n- From `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002FCLAUDE.md`: if intercompany agreements are marked as partial or no,\n  flag which entity relationships likely need agreements (parent-subsidiary\n  services, IP licenses, loans).\n\nOutput format:\n\n```\nENTITY HEALTH AUDIT — [date]\n\nFILING COMPLIANCE\n  Overdue: [N]\n  Unknown status: [N]\n  Action: run --sweep to confirm unknown items\n\nDORMANT ENTITIES ([N])\n  [List of dormant entities with age and annual carrying cost if known]\n  Dissolution candidates (>5 years dormant): [list]\n\nGOOD STANDING\n  No record: [N] entities\n  Stale (>12 months): [N] entities\n  Consider refreshing before: [any upcoming transactions or contract renewals if known]\n\nPOTENTIAL GAPS\n  Foreign qualification: [flag question — confirm operational presence in:]\n    [list of states from `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002FCLAUDE.md` footprint not in tracker as qualified]\n  Intercompany agreements: [status from `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002FCLAUDE.md`]\n\nRECOMMENDED ACTIONS\n  1. [Highest priority action]\n  2. [etc.]\n```\n\n---\n\n## Mode 5: Export\n\n```\n\u002Fcorporate-legal:entity-compliance --export [--format csv|table]\n```\n\nProduces a flat export suitable for sharing with finance, legal ops, or\noutside registered agent. Default: CSV.\n\nCSV columns:\n`Entity Name, Entity Type, State of Formation, Formation Date, Status,\nRegistered Agent, Jurisdiction, Qualification Type, Filing Type, Due Date,\nLast Filed, Last Fee, Good Standing Confirmed, Notes`\n\nOne row per filing per jurisdiction. Multiple rows per entity (one per\njurisdiction × filing type combination).\n\nIf `--format table`: produce a markdown table suitable for pasting into\na report or Slack message, showing only the next 90 days of filings.\n\n---\n\n## What this skill does not do\n\n- It does not file anything. Output is a tracker and a to-do list; filing\n  is done by the attorney, outside counsel, or registered agent.\n- It does not pull good standing certificates. It tracks when certificates\n  were last confirmed; obtaining them is manual or via registered agent.\n- It does not determine whether foreign qualification is required in a given\n  state. That analysis depends on facts about business activity that the\n  attorney must confirm.\n- It does not replace a registered agent service for companies with complex\n  multi-entity structures. CT Corp, National Registered Agents, and similar\n  services have dedicated compliance teams and direct state relationships.\n  This skill is best suited for smaller organizations without agent support,\n  or as a lightweight layer on top of agent data for organizations that do\n  have support.\n- The filing deadline reference table is not legal advice and may not reflect\n  current requirements. Confirm all deadlines before relying on them.\n\n\n## Formula injection defense\n\nBefore writing any cell in Excel, Sheets, or CSV output, neutralize formula injection. Counterparty-sourced text (contract quotes, party names, registered agent data, CLM exports) is attacker-controlled. A cell starting with `=`, `+`, `-`, `@`, `\t`, `\n`, or `\n` will be interpreted as a formula or break the row structure.\n\n- **Prefix with a single quote:** `'=SUM(A1:A10)` → `=SUM(A1:A10)` (displayed as text, not executed)\n- **Applies to every cell that contains text sourced from a document, a tool result, or a user paste.** Column headers you control and computed values you produce are safe.\n- **CSV: also escape embedded commas, double quotes, newlines** (RFC 4180 quoting).\n- This is not optional. A spreadsheet your user opens in Excel that triggers a macro or exfiltrates data via DDE is a supply-chain attack on your user.\n","# \u002Fentity-compliance\n\n1. Load `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002FCLAUDE.md` → `## Entity Management` (entity table, jurisdictions, registered agent).\n2. Route to the correct mode below based on flag:\n   - No flag or `--init`: Mode 1 — initialize tracker from entity table\n   - `--report`: Mode 2 — surface upcoming deadlines and overdue items\n   - `--update`: Mode 3a (manual) or 3b (--from-report upload) — update status\n   - `--sweep`: Mode 3c — walk through unknown\u002Foverdue items one by one\n   - `--audit`: Mode 4 — full health audit\n   - `--export`: Mode 5 — produce CSV or table export\n3. Read\u002Fwrite `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002Fentities\u002Fcompliance-tracker.yaml`.\n4. After any update: show summary of changes and next action.\n\n---\n\n## Purpose\n\nAnnual reports, franchise taxes, Statements of Information, biennial filings —\nevery entity in every state has its own schedule and its own consequences for\nmissing the deadline. This skill maintains a single YAML tracker that knows\nwhat's due, when, and for which entity. It's lightweight by design: the tracker\nis a file you own, Claude updates it on command, and you export it when you need\nto share it.\n\n## Important: deadline reference caveat\n\n> The filing deadlines in this skill's reference table reflect publicly available\n> requirements as of the skill's build date. State filing requirements and due\n> dates can change. **Always confirm deadlines with your registered agent or\n> directly with the relevant Secretary of State before relying on them for\n> compliance purposes.** If you use CT Corp, National Registered Agents, or\n> another registered agent service, their compliance calendar is authoritative\n> for your specific entities — use this tracker to organize and surface their\n> data, not to replace it.\n\n## Jurisdiction assumption\n\n> This tracker computes deadlines against the state or country of formation \u002F qualification recorded per entity. Filing rules, due-date mechanics, and fee structures vary materially by jurisdiction. If an entity's actual footprint differs from what's in `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002FCLAUDE.md` (undisclosed foreign qualification, dissolved entities, jurisdictional re-domestication, international filings managed by a local agent), the output may not apply as written — confirm with the registered agent or local counsel for that jurisdiction.\n\n## Entity-type disambiguation (especially Delaware)\n\n> The filing calendar depends on **entity type**, not just jurisdiction. Treating a \"Delaware entity\" as a single bucket is a common and consequential error — DE corporations, DE LLCs, and DE LPs have different filings, different deadlines, and different consequences for a miss. Confirm the entity type from the entity table before computing or reporting a deadline, and never copy a deadline from one entity-type to another in the same state.\n>\n> **Delaware — the split that matters:**\n>\n> - **DE Corporation (Inc., Corp.):** Annual report AND franchise tax, both due **March 1**. Franchise tax is calculated by the authorized-shares method or the assumed-par-value capital method (whichever is lower); the annual report captures director \u002F officer information. Statutory basis: 8 Del. C. §§ 501–502 [verify current].\n> - **DE LLC:** No annual report required. Annual tax is a **flat $300**, due **June 1**. Statutory basis: 6 Del. C. § 18-1107(d) [verify current fee and date].\n> - **DE LP:** No annual report required. Annual tax is a **flat $300**, due **June 1** (parallel to the LLC rule). Statutory basis: 6 Del. C. § 17-1109 [verify current].\n>\n> A DE LLC is NOT required to file a March 1 annual report — writing that deadline for an LLC carries real risk (spurious \"overdue\" flags that mask actual June 1 exposure, or worse, the inverse: a user who treats the March 1 corporation rule as universal and misses the June 1 LLC deadline). If the entity table records a Delaware entity without a type, flag it as `type_unknown` and ask the user to confirm before computing either deadline.\n>\n> The same entity-type discipline applies in every other jurisdiction with divergent filing regimes by entity type (e.g., CA corp Statement of Information vs. CA LLC SOI cadence; TX franchise tax applies to corporations, LLCs, and LPs but with different no-tax-due thresholds). When the reference table for a jurisdiction is populated, make sure it is indexed by entity type, not just by state.\n\n---\n\n## Tracker file\n\nLives at `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002Fentities\u002Fcompliance-tracker.yaml`. Structure:\n\n```yaml\n# Entity Compliance Tracker\n# Generated: [date]\n# Last updated: [date]\n# Disclaimer: deadlines are reference only — confirm with registered agent or Secretary of State\n\nmetadata:\n  company: \"[Company Name]\"\n  generated: \"[date]\"\n  last_updated: \"[date]\"\n  last_audit: \"[date or null]\"\n\ncustom_jurisdictions:   # manually added — US states or countries not in built-in reference table\n  []                    # populated when a new jurisdiction is encountered\n\nentities:\n  - name: \"[Entity Name]\"\n    type: \"[Corporation \u002F LLC \u002F LP \u002F other]\"\n    state_of_formation: \"[state]\"\n    formation_date: \"[date or null]\"\n    status: \"[active \u002F dormant \u002F dissolving]\"\n    registered_agent: \"[CT Corp \u002F National \u002F in-house \u002F other]\"\n    notes: \"\"\n\n    jurisdictions:\n      - state: \"[state]\"\n        qualification: \"[domestic \u002F foreign]\"\n        qualified_date: \"[date or null]\"\n        agent_managed: false   # set true for international entities where a local agent handles compliance\n        local_agent: \"[name or null]\"\n        filings:\n          - type: \"[Annual Report \u002F Franchise Tax \u002F Statement of Information \u002F Biennial Statement \u002F other]\"\n            due_date: \"[YYYY-MM-DD]\"\n            due_basis: \"[fixed date \u002F anniversary month \u002F other]\"\n            last_filed: \"[date or null]\"\n            last_fee: \"[amount or null]\"\n            status: \"[current \u002F due_soon \u002F overdue \u002F unknown]\"\n            confirmed_good_standing: \"[date or null]\"\n            notes: \"\"\n```\n\nStatus values:\n- `current` — filed for current period, nothing due within 90 days\n- `due_soon` — due within 90 days\n- `overdue` — past due date with no filed date recorded\n- `unknown` — no information; needs manual confirmation\n\n---\n\n## Mode 1: Initialise\n\nRun when no tracker exists, or with `--rebuild` to regenerate from scratch.\n\n### Step 1: Load entity table\n\nRead `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002FCLAUDE.md` → `## Entity Management` → Entity table. If the entity table\nis populated (from org chart upload at cold-start), use it directly. If not,\nask the user to either run the cold-start module or provide the entity list.\n\n### Step 2: For each entity × jurisdiction, confirm the filing requirements\n\nFor each entity, confirm the current filing schedule with the registered agent or the relevant Secretary of State. State filing schedules change (some states move from fixed dates to anniversary-based schedules and back, fee structures are revised, filing categories are reclassified). Do not rely on a cached schedule. The tracker below records the dates you confirm; update them when your registered agent sends reminders.\n\nFor each jurisdiction where the entity is registered (domestic or foreign):\n\n1. Ask the user whether they have a current compliance report from the registered agent — that's the most authoritative source.\n2. If not, ask the user what they know (filing type, due-date basis, last filed date, typical fee). Record what they provide.\n3. For anything the user does not know, flag the entity × jurisdiction entry as `unknown` — do not populate dates from a cached reference. The user's next step is to confirm with the registered agent or Secretary of State.\n\n**Capture details in the tracker rather than a reference table:**\n\n> I don't have filing requirements for [Jurisdiction] in the reference table.\n> Let me capture them so we can track this going forward.\n>\n> For [Entity] in [Jurisdiction]:\n> 1. What type of filing is required? (Annual report, franchise tax, confirmation\n>    statement, annual return, or something else?)\n> 2. When is it due? (Fixed date like May 1, anniversary month, or other?)\n> 3. What's the typical fee? (Approximate is fine — or \"unknown\".)\n> 4. Who is your registered agent or local filing agent there?\n\nStore the answer in a `custom_jurisdictions` block in the tracker:\n\n```yaml\ncustom_jurisdictions:\n  - jurisdiction: \"[State \u002F Country]\"\n    jurisdiction_type: \"[US state \u002F Canada province \u002F EU member state \u002F other]\"\n    filings:\n      - type: \"[filing type]\"\n        due_basis: \"[fixed: MM-DD \u002F anniversary month \u002F other description]\"\n        typical_fee: \"[amount or unknown]\"\n        notes: \"[any other relevant information — e.g., local agent required, filing in local language]\"\n    added_by: \"manual\"\n    added_date: \"[date]\"\n```\n\nThis custom definition is then applied to all entities in that jurisdiction.\nFuture `--init` runs and entity additions will use it automatically.\n\n**International jurisdictions specifically:**\n\nInternational filings vary enormously by jurisdiction. Always go through the\ncustom definition flow above — confirm the filing type, cadence, and fee with\nthe local filing agent or registered office agent before populating the tracker.\n\nFor international entities, also ask:\n- Is there a local filing agent or registered office agent handling compliance?\n  If yes, note the agent name — the tracker can flag when to follow up with them\n  rather than calculating due dates independently.\n- Is the entity required to file any group-level reports in this jurisdiction\n  (e.g., country-by-country reporting, beneficial ownership registers,\n  economic substance filings)?\n\nFlag international entities with a local agent as `agent_managed: true` in the\ntracker. The report mode will list them separately with a note to confirm status\nwith the local agent rather than showing a calculated due date.\n\nFor anniversary-based filings: calculate from the formation_date in the tracker.\nIf formation_date is null: set status to `unknown` and flag for confirmation.\n\n### Step 3: Write the tracker\n\nGenerate `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002Fentities\u002Fcompliance-tracker.yaml` with all entities and their\ncalculated filing requirements. Set initial status:\n- `current` if last_filed is within the current filing period\n- `due_soon` if due within 90 days and no last_filed for current period\n- `overdue` if due date has passed and no last_filed for current period\n- `unknown` if formation_date is missing or state is not in reference table\n\nShow a summary after generating:\n\n```\nEntity compliance tracker initialized.\n\nEntities: [N]\nTotal jurisdictions: [N]\nFilings tracked: [N]\n\nStatus summary:\n  ✅ Current:   [N]\n  ⏰ Due soon:  [N] (next 90 days)\n  🔴 Overdue:   [N]\n  ❓ Unknown:   [N] (confirm with registered agent)\n\nRun \u002Fcorporate-legal:entity-compliance --report to see what's due.\n```\n\n---\n\n## Mode 2: Report\n\nSurfaces upcoming deadlines and flags overdue items. Default: next 90 days.\n\n```\n\u002Fcorporate-legal:entity-compliance --report [--days 30|60|90|180]\n```\n\nOutput format:\n\n```\nENTITY COMPLIANCE REPORT — [date]\n[Company Name]\n\n🔴 OVERDUE ([N]):\n  [Entity] \u002F [State] \u002F [Filing type] — was due [date]\n\n⏰ DUE WITHIN [N] DAYS ([N]):\n  [Entity] \u002F [State] \u002F [Filing type] — due [date]  [registered agent]\n  [Entity] \u002F [State] \u002F [Filing type] — due [date]\n\n✅ RECENTLY FILED ([N] in last 90 days):\n  [Entity] \u002F [State] \u002F [Filing type] — filed [date]\n\n❓ UNKNOWN STATUS ([N]):\n  [Entity] \u002F [State] \u002F [Filing type] — no information; confirm with registered agent\n\n🌐 AGENT-MANAGED ([N]):\n  [Entity] \u002F [Country] \u002F [Filing type] — managed by [local agent]; confirm status directly\n  [Entity] \u002F [Country] — no local agent recorded; add one with --update\n\nGOOD STANDING:\n  Last confirmed: [date]\n  Entities with confirmed good standing: [N] of [total]\n  Entities not confirmed in last 12 months: [list]\n```\n\nIf the tracker covers more than ~10 entities, or any time the user asks: offer the dashboard (see CLAUDE.md `## Outputs → Dashboard offer for data-heavy outputs`). Shape the offer for this output — counts by filing status (overdue \u002F due soon \u002F filed \u002F unknown), counts by good-standing state, and a sortable entity table with jurisdiction, filing type, and next due date.\n\n---\n\n## Mode 3: Update\n\nUpdates one or more entities in the tracker. Three sub-modes:\n\n### Consequential-action gate (file SOI \u002F annual report)\n\n**Before directing or confirming a filing:** Read `## Who's using this` in `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002FCLAUDE.md`. If the Role is **Non-lawyer**:\n\n> Filing a Statement of Information, annual report, or franchise tax return with a Secretary of State has legal consequences — it's a formal representation from the entity, it carries fees, and missed or incorrect filings can cause loss of good standing or franchise-tax defaults. Have you reviewed this with an attorney (or a qualified registered agent) before filing? If yes, proceed to record the filing. If no, here's a brief to bring to them:\n>\n> - Entity, jurisdiction, filing type, and due date\n> - What the tracker says about the last filing (date, fee, officer\u002Fdirector information last reported)\n> - Open questions (is the officer\u002Fdirector information still accurate; has the registered agent changed; has the principal office changed)\n> - What could go wrong (out-of-date officer information, missed deadline triggering franchise tax or dissolution, fee calculation error)\n> - What to ask the attorney (is a filing actually needed this year; are there any charter amendments or officer changes that need to be reflected; who should sign)\n>\n> If you need to find an attorney, solicitor, barrister, or other authorised legal professional: contact your professional regulator (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) for a referral service.\n\nDo not record a new `last_filed` date past this gate without an explicit yes. Tracker reads, deadline reports, and \"what's due soon\" output do not require the gate.\n\n### 3a: Manual update\n\n```\n\u002Fcorporate-legal:entity-compliance --update\n```\n\nAttorney tells Claude what was filed:\n> \"We filed the Delaware annual report for [Entity] on March 1. Fee was $450.\"\n\nClaude updates:\n- `last_filed` → March 1 date\n- `last_fee` → $450\n- `status` → `current`\n- `last_updated` in metadata\n\n### 3b: Registered agent report upload\n\n```\n\u002Fcorporate-legal:entity-compliance --update --from-report\n```\n\nUser uploads a CT Corp, National Registered Agents, or similar compliance\nreport (PDF, CSV, or Excel). Claude reads it and updates matching entities:\n\nFrom the report, extract for each entity:\n- Filing type and due date\n- Last filed date (if present)\n- Good standing status and date confirmed\n- Any flags or warnings from the agent\n\nMatch report entities to tracker entities by name (flag near-matches for\nconfirmation — \"Acme Holdings LLC\" vs. \"Acme Holdings, LLC\" are probably\nthe same entity).\n\nAfter processing:\n```\nUpdated [N] entities from report.\n\nMatched: [N]\nUnmatched (in report, not in tracker): [list — may need to add to entity table]\nNot in report (in tracker, no update): [list — status unchanged]\n```\n\n### 3c: Bulk status sweep\n\n```\n\u002Fcorporate-legal:entity-compliance --sweep\n```\n\nWalks through each entity with `unknown` or `overdue` status and asks for\ncurrent information one at a time:\n\n> [Entity] \u002F [State] \u002F [Filing type] — currently showing as [status].\n> Has this been filed? If yes, when and what was the fee?\n\nUpdates tracker after each confirmation. Produces a completion summary.\n\n---\n\n## Mode 4: Health audit\n\n```\n\u002Fcorporate-legal:entity-compliance --audit\n```\n\nBroader review beyond just filing status. Surfaces:\n\n**Filing compliance:**\n- Overdue items (from report mode)\n- Unknown status items\n\n**Entity health:**\n- Entities marked as `dormant` — flag for review: should these be dissolved?\n  Carrying dormant entities costs money (annual fees, registered agent fees)\n  and creates ongoing compliance obligations.\n- Entities with formation_date older than 5 years and status `dormant` — flag\n  as dissolution candidates.\n- Entities missing formation_date — flag as data gap.\n\n**Good standing gaps:**\n- Entities with no `confirmed_good_standing` date — unknown whether in good\n  standing; risk if a transaction requires a certificate on short notice.\n- Entities with `confirmed_good_standing` older than 12 months — stale; worth\n  refreshing, especially if M&A or financing is anticipated.\n\n**Foreign qualification gaps:**\n- Based on `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002FCLAUDE.md` entity table: are there states in the company's\n  operational footprint (offices, employees) where entities are not foreign\n  qualified? This requires the attorney to confirm operational presence —\n  Claude can flag the question but cannot determine presence independently.\n\n**Intercompany agreement gaps:**\n- From `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002FCLAUDE.md`: if intercompany agreements are marked as partial or no,\n  flag which entity relationships likely need agreements (parent-subsidiary\n  services, IP licenses, loans).\n\nOutput format:\n\n```\nENTITY HEALTH AUDIT — [date]\n\nFILING COMPLIANCE\n  Overdue: [N]\n  Unknown status: [N]\n  Action: run --sweep to confirm unknown items\n\nDORMANT ENTITIES ([N])\n  [List of dormant entities with age and annual carrying cost if known]\n  Dissolution candidates (>5 years dormant): [list]\n\nGOOD STANDING\n  No record: [N] entities\n  Stale (>12 months): [N] entities\n  Consider refreshing before: [any upcoming transactions or contract renewals if known]\n\nPOTENTIAL GAPS\n  Foreign qualification: [flag question — confirm operational presence in:]\n    [list of states from `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002FCLAUDE.md` footprint not in tracker as qualified]\n  Intercompany agreements: [status from `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcorporate-legal\u002FCLAUDE.md`]\n\nRECOMMENDED ACTIONS\n  1. [Highest priority action]\n  2. [etc.]\n```\n\n---\n\n## Mode 5: Export\n\n```\n\u002Fcorporate-legal:entity-compliance --export [--format csv|table]\n```\n\nProduces a flat export suitable for sharing with finance, legal ops, or\noutside registered agent. Default: CSV.\n\nCSV columns:\n`Entity Name, Entity Type, State of Formation, Formation Date, Status,\nRegistered Agent, Jurisdiction, Qualification Type, Filing Type, Due Date,\nLast Filed, Last Fee, Good Standing Confirmed, Notes`\n\nOne row per filing per jurisdiction. Multiple rows per entity (one per\njurisdiction × filing type combination).\n\nIf `--format table`: produce a markdown table suitable for pasting into\na report or Slack message, showing only the next 90 days of filings.\n\n---\n\n## What this skill does not do\n\n- It does not file anything. Output is a tracker and a to-do list; filing\n  is done by the attorney, outside counsel, or registered agent.\n- It does not pull good standing certificates. It tracks when certificates\n  were last confirmed; obtaining them is manual or via registered agent.\n- It does not determine whether foreign qualification is required in a given\n  state. That analysis depends on facts about business activity that the\n  attorney must confirm.\n- It does not replace a registered agent service for companies with complex\n  multi-entity structures. CT Corp, National Registered Agents, and similar\n  services have dedicated compliance teams and direct state relationships.\n  This skill is best suited for smaller organizations without agent support,\n  or as a lightweight layer on top of agent data for organizations that do\n  have support.\n- The filing deadline reference table is not legal advice and may not reflect\n  current requirements. Confirm all deadlines before relying on them.\n\n\n## Formula injection defense\n\nBefore writing any cell in Excel, Sheets, or CSV output, neutralize formula injection. Counterparty-sourced text (contract quotes, party names, registered agent data, CLM exports) is attacker-controlled. A cell starting with `=`, `+`, `-`, `@`, `\t`, `\n`, or `\n` will be interpreted as a formula or break the row structure.\n\n- **Prefix with a single quote:** `'=SUM(A1:A10)` → `=SUM(A1:A10)` (displayed as text, not executed)\n- **Applies to every cell that contains text sourced from a document, a tool result, or a user paste.** Column headers you control and computed values you produce are safe.\n- **CSV: also escape embedded commas, double quotes, newlines** (RFC 4180 quoting).\n- This is not optional. A spreadsheet your user opens in Excel that triggers a macro or exfiltrates data via DDE is a supply-chain attack on your user.\n",{"name":5,"description":57,"argument-hint":58},"Entity compliance tracker — initialize, report upcoming deadlines, update status, run health audit, export to CSV. Maintains a compliance-tracker.yaml built from the entity table, calculates filing deadlines by entity and jurisdiction, and surfaces what's due in the next 30\u002F60\u002F90 days. Use when user says \"entity compliance\", \"filing deadlines\", \"annual reports due\", \"entity tracker\", \"what filings are due\", \"entity health\", or \"good standing\".\n","[--init | --report [--days N] | --update [--from-report] | --sweep | --audit | --export [--format csv|table]]","main","4a6c651889c97cc9140580363c73e0eb17379c2b","corporate-legal\u002Fskills\u002Fentity-compliance",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":68,"prompt":78,"zipAvailable":79},[69,72,75],{"tool":70,"command":71},"npx","npx skills add anthropics\u002Fclaude-for-legal --skill entity-compliance",{"tool":73,"command":74},"bunx","bunx skills add anthropics\u002Fclaude-for-legal --skill entity-compliance",{"tool":76,"command":77},"pnpm","pnpm dlx skills add anthropics\u002Fclaude-for-legal --skill entity-compliance","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-for-legal\u002Fblob\u002Fmain\u002Fcorporate-legal\u002Fskills\u002Fentity-compliance\u002FSKILL.md",true,[],[82,110,132,151,173,185],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":91,"publishedAt":52},"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",[88],{"categoryNo":89,"categoryName":90,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[92,93,94,95,96,97,98,99,100,101,102,103,46,104,45,105,106,107,108,109],"reg","watcher","reg feed watcher","running","feeds","filtered","diff","development","for","classification","new","now","scheduled","check","last","update","report","regulatory",{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":52},"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",[],[117,118,98,100,119,120,121,46,122,45,123,124,125,126,127,128,129,130,109,131],"policy","policy redraft","up","fix","produce","documents","drafting","gaps","review","draft","id","gap","mark","first","direct",{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":136,"categories":137,"keywords":138,"publishedAt":52},"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",[],[98,117,139,140,45,141,142,92,143,93,144,145,146,147,46,148,128,149,150,109],"policy diff","which","you","analysis","text","change","paste","library","material","gap analysis","what the","name",{"skillNo":152,"name":153,"nameZh":6,"description":154,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":155,"categories":156,"keywords":157,"publishedAt":52},"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",[],[158,159,140,160,161,162,102,46,45,141,163,164,165,166,167,168,169,170,171,172],"workspace","matter workspace","switch","manage","workspaces","keep","across","create","engagement","close","active","clients","list","it","context",{"skillNo":174,"name":124,"nameZh":6,"description":175,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":176,"categories":177,"keywords":178,"publishedAt":52},"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",[],[124,127,128,179,167,36,180,181,182,46,183,45,184],"risk","remediation","status","open","accept","user",{"skillNo":186,"name":187,"nameZh":6,"description":188,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":189,"categories":190,"keywords":192,"publishedAt":52},"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",[191],{"categoryNo":29,"categoryName":30,"taxonomyType":26,"taxonomyTypeDesc":27},[128,193,194,195,98,117,196,182,197,198,199,200,124,201,202,203,204,36,180,205],"gap surfacer","shared","tracks","send","confirmation","aging","false","comments","with","work","slack","via","surfaces"]