[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M718GJRR6Z95HV6KQ1G2ASDG":3,"skill-same:01M718GJRR6Z95HV6KQ1G2ASDG":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":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":48,"repositoryHtmlUrl":49,"repositoryHomepageUrl":6,"ownerHtmlUrl":50,"ownerBlogUrl":51,"ownerDescription":6,"updatedAt":52,"install":53,"resources":66},"01M718GJRR6Z95HV6KQ1G2ASDG","portfolio",null,"Track the IP portfolio — registrations, renewals, maintenance fees, and use declarations. Use when checking what's renewing, adding or updating an asset, recording a maintenance filing, or auditing the register for gaps, lapses, and use-in-commerce questions. Receives handoffs from prosecution and clearance work.","anthropics\u002Fclaude-for-legal","anthropics","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F76263028?v=4","01M697XGDPXJAVQ8391V2BCYTE","Anthropic","01M7189QY7HXHMC9BW4MFHPZ6H",9970,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-for-legal\u002Fblob\u002Fmain\u002Fip-legal\u002Fskills\u002Fportfolio\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"commerce","add","asset","report","update","questions","audit","maintenance","work","track","gaps","when","use","ip","filing","for","register","clearance","recording","2026-11-10 10:12:30",false,"---\nname: portfolio\ndescription: >\n  Track the IP portfolio — registrations, renewals, maintenance fees, and use\n  declarations. Use when checking what's renewing, adding or updating an\n  asset, recording a maintenance filing, or auditing the register for gaps,\n  lapses, and use-in-commerce questions. Receives handoffs from prosecution\n  and clearance work.\nargument-hint: \"[--report [--days N] | --add | --update | --audit]\"\n---\n\n# \u002Fportfolio\n\nSurfaces what's renewing, adds assets, records filings, and audits the register.\n\n## Instructions\n\n1. **Follow the workflow below** and read\n   `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fip-legal\u002Fportfolio.yaml`.\n\n2. **Default (no args):** equivalent to `--report` — show deadlines in the\n   next 90 days grouped by urgency (🔴 lapsed\u002Fgrace, ⏰ due within window,\n   🟡 upcoming, 🌐 agent-managed, ❓ unknown).\n\n3. **`--report [--days N]`:** Mode 2. Change the window with `--days`\n   (30 \u002F 60 \u002F 90 \u002F 180 typical). Always prepend the work-product header\n   per CLAUDE.md → Outputs. Always close with the verification caveat.\n\n4. **`--add`:** Mode 3. Walk through a new asset interactively — type,\n   jurisdiction, number, dates, owner, business owner. Capture a custom\n   rule if the jurisdiction isn't built in.\n\n5. **`--update`:** Mode 4. Record that a maintenance filing or fee payment\n   was made, sync with the IP management system, or change an asset's\n   status. Enforce the consequential-action gate before setting any\n   deadline to `filed`.\n\n6. **`--audit`:** Mode 5. Broader health check — deadline hygiene,\n   registration gaps, use-in-commerce questions on §8-approaching marks,\n   owner inconsistencies, expiration horizon, unwatched marks.\n\n7. **If the register is empty and an IP management system is connected:**\n   Offer Mode 1 — pull the portfolio from the system of record and\n   initialise the register.\n\n8. **Guardrail reminder:** Computed deadlines are reference only. Every\n   output closes with a line directing verification against the USPTO\n   TSDR, WIPO, or relevant registry before filing or paying. A\n   docketed-but-wrong deadline creates false confidence; do not let the\n   user treat this as the system of record unless the IP management\n   system is sync-integrated.\n\n## Examples\n\n```\n\u002Fip-legal:portfolio\n```\n\n```\n\u002Fip-legal:portfolio --report --days 180\n```\n\n```\n\u002Fip-legal:portfolio --add\n```\n\n```\n\u002Fip-legal:portfolio --update\n```\n\n```\n\u002Fip-legal:portfolio --audit\n```\n\n---\n\n## Works better connected\n\nThis skill tracks deadlines from what you tell it. It works much better\nconnected to:\n\n- **An IP management system (IPMS) via MCP** — Anaqua, Clarivate IPfolio,\n  AppColl, Patrix, Alt Legal, FoundationIP. A connected IPMS gives you the\n  full docket, maintenance fee schedules, and incoming correspondence in one\n  place, instead of the register being whatever the lawyer remembers to\n  paste. Ask your IPMS vendor if they have an MCP connector, or see\n  `CONNECTORS.md` at the repo root for how to get one added.\n- **USPTO directly via customer number** — pulls status, deadlines, and\n  correspondence for your whole portfolio rather than one application at a\n  time. Not currently available as an MCP; on the wish list in\n  `CONNECTORS.md`.\n\nWithout either, paste your docket or upload a spreadsheet and I'll track from\nthere.\n\n## Purpose\n\nA trademark registration that isn't renewed on time can be cancelled. A patent\nwithout its maintenance fee paid lapses. A domain that expires can be sniped\nwithin the hour. All of this is avoidable, and all of it depends on one thing:\nthe right deadline is on someone's calendar, tied to the right registration\nnumber, in the right jurisdiction.\n\nThis skill maintains that calendar.\n\n## Important: deadline reference caveat\n\n> The deadline rules this skill applies reflect publicly available requirements\n> as of the skill's build date. IP office requirements, grace periods, fee\n> structures, and maintenance schedules change. **Always confirm computed\n> deadlines against the USPTO TSDR \u002F Patent Center, WIPO Madrid Monitor \u002F\n> Patentscope, EUIPO eSearch, UKIPO online records, or the relevant national\n> registry before acting.** If you use Anaqua, CPA Global, Clarivate, Alt Legal,\n> or another IP management system, their docket is authoritative for your\n> assets — use this tracker to organize and surface their data, not to replace\n> it.\n>\n> A docketed-but-wrong deadline is worse than an undocketed one: it creates\n> false confidence. \"No deadline soon\" outputs especially deserve a second\n> look before you rely on them.\n\n## Jurisdiction and type assumptions\n\nMaintenance mechanics vary by jurisdiction and asset type:\n\n- **US trademarks:** §8 Declaration of Use between 5th and 6th anniversary of\n  registration (or §71 for Madrid designations), then combined §8\u002F§9 renewal\n  at 10 years and every 10 years thereafter. §15 Incontestability available\n  after 5 years of continuous use. 6-month grace period with surcharge for §8\n  and §9; no grace for the underlying use itself.\n- **Madrid International trademarks:** 10-year registration term renewable at\n  WIPO; individual designated countries may have local use or declaration\n  requirements (e.g., US §71).\n- **EUIPO trademarks:** 10-year renewal; 6-month grace with surcharge.\n- **US utility patents:** Maintenance fees due at 3.5, 7.5, and 11.5 years\n  from grant. 6-month grace window with surcharge; after that, potential\n  revival by petition if lapse was unintentional.\n- **US design patents:** No maintenance fees — 15-year term from grant for\n  applications filed on or after May 13, 2015 (14 years if earlier). No action\n  required mid-term.\n- **EPO \u002F national patents:** Annuities typically due annually from filing or\n  from national phase entry. National rules vary — confirm per jurisdiction.\n- **US copyright:** No maintenance for works created 1978 or later.\n  Pre-1978 works may have had renewal obligations; flag for attorney review\n  if the asset pre-dates 1964 (rarely in scope for modern portfolios).\n- **Domains:** Annual or multi-year renewal per registrar; typical 30-day\n  grace then redemption period (~30 days at high fee) then drop.\n\nIf the portfolio includes assets in jurisdictions not listed above, capture\nthe maintenance mechanic in the register's `custom_rules` block and the\nreport will surface them as `agent_managed` — confirm status with the\nforeign associate rather than computing a date this skill doesn't understand.\n\n---\n\n## The register\n\nLives at `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fip-legal\u002Fportfolio.yaml`.\nStructure:\n\n```yaml\n# IP Portfolio Register\n# Generated: [date]\n# Last updated: [date]\n# Disclaimer: computed deadlines are reference only — confirm with USPTO\u002FWIPO\u002F\n# relevant registry or the IP management system of record before acting.\n\nmetadata:\n  company: \"[Company Name]\"\n  generated: \"[date]\"\n  last_updated: \"[date]\"\n  last_audit: \"[date or null]\"\n  source_system: \"[Anaqua \u002F CPA Global \u002F manual \u002F none]\"\n\ncustom_rules:   # non-built-in jurisdictions captured manually\n  []\n\nassets:\n  - id: \"TM-US-001\"\n    type: \"trademark\"                          # trademark \u002F patent \u002F copyright \u002F design \u002F domain\n    jurisdiction: \"US\"\n    mark_or_title: \"[Mark or title]\"\n    owner: \"[Record owner — registered entity name]\"\n    status: \"registered\"                       # pending \u002F registered \u002F lapsed \u002F abandoned \u002F cancelled\n    application_number: \"[number or null]\"\n    registration_number: \"[number or null]\"\n    classes: [\"9\", \"42\"]                       # Nice classes for TM; CPC\u002FIPC for patents; null otherwise\n    filing_date: \"[YYYY-MM-DD or null]\"\n    registration_date: \"[YYYY-MM-DD or null]\"\n    priority_date: \"[YYYY-MM-DD or null]\"\n    grant_date: \"[YYYY-MM-DD or null]\"         # patents\n    next_deadlines:                            # computed; refreshed on --report and --audit\n      - type: \"§8 Declaration of Use\"\n        due_date: \"[YYYY-MM-DD]\"\n        grace_end: \"[YYYY-MM-DD or null]\"\n        basis: \"5th-6th anniversary of registration\"\n        action: \"File §8 Declaration of Use (or excusable nonuse)\"\n        status: \"upcoming\"                     # upcoming \u002F due_soon \u002F overdue \u002F grace \u002F filed\n    use_in_commerce: true                      # TM only — drives §8 analysis\n    agent_managed: false                       # true for foreign associate \u002F outside counsel managed\n    local_agent: null\n    docket_id: \"[IP-mgmt-system ID or null]\"\n    outside_counsel: \"[firm or null]\"\n    business_owner: \"[email or team]\"\n    notes: \"\"\n\n  - id: \"PAT-US-001\"\n    type: \"patent\"\n    jurisdiction: \"US\"\n    mark_or_title: \"[Invention title]\"\n    owner: \"[Owner]\"\n    status: \"granted\"\n    application_number: \"[number]\"\n    registration_number: \"[patent number]\"\n    filing_date: \"[YYYY-MM-DD]\"\n    grant_date: \"[YYYY-MM-DD]\"\n    priority_date: \"[YYYY-MM-DD or null]\"\n    expiration_date: \"[YYYY-MM-DD]\"            # 20 years from earliest non-provisional filing\n    next_deadlines:\n      - type: \"3.5-year maintenance fee\"\n        due_date: \"[YYYY-MM-DD]\"\n        grace_end: \"[YYYY-MM-DD]\"\n        basis: \"3.5 years from grant\"\n        action: \"Pay maintenance fee (small\u002Fmicro entity if applicable)\"\n        status: \"upcoming\"\n    claims_count: 20\n    entity_size: \"large\"                       # large \u002F small \u002F micro (drives USPTO fees)\n    docket_id: null\n    outside_counsel: null\n    business_owner: null\n    notes: \"\"\n```\n\nStatus values for `next_deadlines`:\n- `upcoming` — more than 90 days out\n- `due_soon` — due within 90 days, not yet filed\n- `overdue` — past the primary due date, within grace window (if any)\n- `grace` — in the grace period (explicit flag — carries surcharge)\n- `lapsed` — past grace with no action; asset effectively lost unless revivable\n- `filed` — action completed this cycle\n\n---\n\n## Mode 1: Initialise\n\nRun when no register exists, or with `--rebuild`.\n\n### Step 1: Determine the source\n\nRead `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fip-legal\u002FCLAUDE.md`:\n- **IP management system connected** (Anaqua, CPA Global, etc.): pull the portfolio via its integration. The IP system is the authoritative source; this register mirrors it and adds no deadlines the system doesn't already have.\n- **No IP management system, but spreadsheet \u002F export available:** ask the user to share the export. Import what's present; flag any asset missing a registration or grant date as `unknown` for deadline computation.\n- **Nothing at hand:** walk through assets interactively — type, jurisdiction, number, key dates, owner.\n\n### Step 2: For each asset, compute deadlines\n\nApply the rules at the top of this file. Populate `next_deadlines` with the\ntwo or three closest upcoming items — further-out deadlines (10-year renewals\ndecades away) are computed on demand during reports rather than stored\nspeculatively.\n\n**For assets the skill cannot confidently schedule:**\n- Unknown jurisdiction rules → add a stub under `custom_rules` and flag the\n  asset `agent_managed: true` with a TODO to confirm with the foreign associate.\n- Missing dates needed for computation (no grant date for a patent, no\n  registration date for a TM) → set `next_deadlines` empty with a note in\n  `notes`, and list the asset as `unknown` in the initialisation summary.\n\n### Step 3: Write the register\n\nGenerate `portfolio.yaml` at the config path. Show a summary:\n\n```\nPortfolio register initialised.\n\nAssets: [N]\n  Trademarks: [N]   ([N registered] \u002F [N pending])\n  Patents:    [N]   ([N granted] \u002F [N pending])\n  Copyrights: [N]\n  Designs:    [N]\n  Domains:    [N]\n\nDeadlines computed: [N]\nAgent-managed \u002F jurisdiction TBC: [N] — confirm with foreign associates\nUnknown (missing key dates): [N] — fill in before relying on reports\n\nRun \u002Fip-legal:portfolio --report to see what's due.\n```\n\n---\n\n## Mode 2: Report\n\n```\n\u002Fip-legal:portfolio --report [--days 30|60|90|180]\n```\n\nDefault window: 90 days. Refresh computed deadlines for every asset before\nproducing the report — don't rely on stored dates alone.\n\nOutput (prepend work-product header per `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fip-legal\u002FCLAUDE.md` → Outputs):\n\n```\nIP PORTFOLIO DEADLINE REPORT — [date]\n[Company Name] — window: next [N] days\n\n🔴 LAPSED \u002F IN GRACE ([N])\n  [Asset ID] \u002F [Jurisdiction] \u002F [Type] \u002F [Mark or title]\n    [Action] — original due [date], grace ends [date]\n    Status: [grace \u002F lapsed]\n\n⏰ DUE WITHIN [N] DAYS ([N])\n  [Asset ID] \u002F [Jurisdiction] \u002F [Type] \u002F [Mark or title]\n    [Action] — due [date]\n    Basis: [e.g., \"5th-6th anniversary of registration\"]\n    [Agent: firm \u002F docket: id — if present]\n\n🟡 UPCOMING (next window beyond 30 days, within [N] days)\n  [list]\n\n🌐 AGENT-MANAGED ([N])\n  [Asset ID] \u002F [Jurisdiction] — managed by [local agent]; confirm directly\n  [Asset ID] \u002F [Jurisdiction] — no local agent recorded; add with --update\n\n❓ UNKNOWN ([N])\n  [Asset ID] — missing [field]; cannot compute deadline\n  Confirm with [IP management system \u002F USPTO TSDR \u002F relevant registry] before relying on this report.\n\nSUMMARY\n  Total assets tracked: [N]\n  Deadlines in window: [N]\n  Last audit: [date]\n```\n\nClose the report with the caveat line: *\"Computed from portfolio register. Verify each deadline against the USPTO\u002FWIPO\u002Fregistry of record before filing or paying.\"*\n\nIf the report lists more than ~10 assets, 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 registration status (live \u002F in grace \u002F lapsed \u002F pending), a deadline timeline, and a sortable portfolio table with jurisdiction, type, and next-action date.\n\n---\n\n## Mode 3: Add\n\n```\n\u002Fip-legal:portfolio --add\n```\n\nInteractive add of a single asset. Ask for:\n1. Type (trademark \u002F patent \u002F copyright \u002F design \u002F domain)\n2. Jurisdiction\n3. Mark or title \u002F invention name\n4. Owner (record owner — matters for §8 filings and assignments)\n5. Key dates (per type: filing, registration, grant, priority, expiration)\n6. Number(s)\n7. Classes \u002F claims count\n8. Source — is this being tracked in the IP management system under a docket ID?\n9. Outside counsel \u002F foreign associate, if any\n10. Business owner (who does this matter to — product line, brand manager)\n\nAfter capture:\n- Compute next deadlines per the rules at the top of this file.\n- If jurisdiction rules aren't built in, walk through the `custom_rules` capture flow (see below).\n- Append to `assets:` in `portfolio.yaml`.\n\n### Custom rules capture\n\nWhen a jurisdiction isn't in the built-in list:\n\n> I don't have maintenance rules for [Jurisdiction] \u002F [Asset type] built in.\n> Let me capture them so we can track this going forward.\n>\n> 1. What maintenance events apply? (Renewal every N years? Annuities annually?\n>    Declarations of use? Something else?)\n> 2. What triggers the due date — filing date, registration date, grant date,\n>    national phase entry, anniversary of something else?\n> 3. Is there a grace period? At what cost?\n> 4. Is there a foreign associate or local agent managing this?\n\nStore under `custom_rules:` and apply to future assets in that jurisdiction.\n\n---\n\n## Mode 4: Update\n\n```\n\u002Fip-legal:portfolio --update\n```\n\n### Consequential-action gate\n\n**Before recording that a maintenance filing or fee payment was made:** Read\n`## Who's using this` in `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fip-legal\u002FCLAUDE.md`. If the Role is **Non-lawyer**:\n\n> Recording a §8 declaration, a §9 renewal, a patent maintenance fee payment,\n> or an international annuity as \"filed\" has consequences. If the record is\n> wrong — missed due date, wrong entity size, wrong specimen of use — the\n> deadline doesn't move, and the asset can still lapse. Have you confirmed\n> this with the attorney or foreign associate who actually made the filing\n> (or with the USPTO TSDR \u002F WIPO Madrid Monitor \u002F relevant registry)? If yes,\n> proceed. If no:\n>\n> - Do not record as filed yet.\n> - Here is what to bring to the attorney: asset ID, jurisdiction, deadline\n>   type, what the IP management system shows, what you believe was filed and\n>   when, and the source of that belief.\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\n> 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 set a deadline's `status` to `filed` past this gate without an\nexplicit yes. Status refresh, report generation, and upcoming-deadline\nsurfacing do not require the gate.\n\n### Sub-modes\n\n**Manual update:** \"We filed the §8 for TM-US-001 on March 4, specimen\nattached.\" Update the matching deadline: `status: filed`, `filed_date`,\nand compute the next deadline in its lifecycle (for §8 that's the §9\nrenewal 10 years out).\n\n**From IP management system sync:** If Anaqua \u002F CPA Global \u002F similar is\nconnected, pull the latest docket and reconcile. Flag mismatches between\nthe register and the system of record — the system of record wins; update\nthe register to match and surface anything the register had that the\nsystem doesn't.\n\n**Status change:** \"Mark TM-US-004 as abandoned.\" Update `status`, clear\n`next_deadlines`, note the date abandoned.\n\n---\n\n## Mode 5: Audit\n\n```\n\u002Fip-legal:portfolio --audit\n```\n\nBroader health check beyond this month's deadlines:\n\n**Deadline hygiene**\n- Any deadlines in `grace` status right now? (In progress but surcharge-costing.)\n- Any `lapsed` assets that aren't marked `abandoned` or `cancelled`? Either\n  revive or update status.\n- Any assets with no `next_deadlines` computed? Either missing data or a\n  jurisdiction the skill doesn't know.\n\n**Registration gaps**\n- Trademark applications filed more than 18 months ago still `pending`?\n  Flag for status check at the office — may need response to an action.\n- Patents filed more than 4 years ago still `pending`? Flag for prosecution\n  check.\n\n**Use-in-commerce (TM only)**\n- §8 approaching on a mark flagged `use_in_commerce: false` or uncertain?\n  The §8 requires use; mark needs a use audit before filing or an excusable\n  nonuse declaration.\n\n**Ownership hygiene**\n- Any assets where the `owner` is not a currently active entity per the\n  entity register (if available)? Flag — may need recordal of assignment.\n- Owner name inconsistencies across assets (same entity, different name\n  strings)? Surface for cleanup.\n\n**Expiration horizon**\n- Any patents expiring in the next 24 months? Even without a maintenance\n  deadline, the business may want to know — product planning, continuation\n  strategy, licensing window.\n\n**Unwatched assets**\n- Any registered marks not on the watch list in CLAUDE.md → Brand protection?\n  Flag as a gap for the attorney to decide whether to add.\n\nOutput format:\n\n```\nIP PORTFOLIO AUDIT — [date]\n\nDEADLINE HYGIENE\n  In grace: [N] — acting now avoids lapse\n  Lapsed (not marked abandoned): [N] — confirm status\n  Missing next-deadline computation: [N] — fill data or mark agent-managed\n\nREGISTRATION GAPS\n  TM applications pending >18 months: [list]\n  Patent applications pending >4 years: [list]\n\nUSE IN COMMERCE (TM)\n  §8 approaching on uncertain-use marks: [list]\n\nOWNERSHIP\n  Assets with unrecognised owner strings: [N]\n  Owner name inconsistencies: [list]\n\nEXPIRATION HORIZON (24 months)\n  Patents expiring: [list]\n\nBRAND WATCH\n  Registered marks not on watch list: [list]\n\nRECOMMENDED ACTIONS\n  1. [highest priority]\n  2. [etc.]\n```\n\n---\n\n## Integration: ip-renewal-watcher agent\n\nThe `ip-renewal-watcher` agent in this plugin runs this skill on a schedule\n(weekly by default) and posts the Mode 2 report to the channel named in\nCLAUDE.md → Renewal alerts. If 🔴 items appear (grace \u002F lapsed), the agent\nposts them immediately regardless of schedule.\n\n## Handoffs\n\n- Receives: new asset records from prosecution skills (when an application\n  is filed or a mark clears), from clearance skills (when a mark is adopted\n  and a filing is queued), and from assignment recordals.\n- Sends: \"file §8 now\" triggers to the attorney — this skill doesn't file\n  anything; it tells the attorney the deadline and what to bring.\n\n## What this skill does not do\n\n- It does not file anything. Every action it surfaces is for the attorney\n  or foreign associate to execute.\n- It does not verify deadlines against the USPTO TSDR, WIPO, or any other\n  registry. It computes them from the dates you give it. The register is\n  a working copy; the registry is the source of truth.\n- It does not decide whether to renew. Renewal is a business call — is the\n  mark still in use, is the patent still valuable, does the domain still\n  matter. This skill surfaces the deadline and the cost; the business and\n  the attorney decide.\n- It does not replace an IP management system for multi-hundred-asset\n  portfolios. Anaqua, CPA Global, Clarivate, Alt Legal, and similar systems\n  have direct registry feeds, deadline automation, and annuity payment\n  services. This skill is best suited for smaller portfolios, or as a\n  lightweight layer that surfaces what the system of record shows.\n- It does not read office records to verify status. A §8 shown as \"filed\"\n  here means someone told it so — not that the USPTO accepted it. Confirm\n  acceptance through TSDR or the IP management system.\n","# \u002Fportfolio\n\nSurfaces what's renewing, adds assets, records filings, and audits the register.\n\n## Instructions\n\n1. **Follow the workflow below** and read\n   `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fip-legal\u002Fportfolio.yaml`.\n\n2. **Default (no args):** equivalent to `--report` — show deadlines in the\n   next 90 days grouped by urgency (🔴 lapsed\u002Fgrace, ⏰ due within window,\n   🟡 upcoming, 🌐 agent-managed, ❓ unknown).\n\n3. **`--report [--days N]`:** Mode 2. Change the window with `--days`\n   (30 \u002F 60 \u002F 90 \u002F 180 typical). Always prepend the work-product header\n   per CLAUDE.md → Outputs. Always close with the verification caveat.\n\n4. **`--add`:** Mode 3. Walk through a new asset interactively — type,\n   jurisdiction, number, dates, owner, business owner. Capture a custom\n   rule if the jurisdiction isn't built in.\n\n5. **`--update`:** Mode 4. Record that a maintenance filing or fee payment\n   was made, sync with the IP management system, or change an asset's\n   status. Enforce the consequential-action gate before setting any\n   deadline to `filed`.\n\n6. **`--audit`:** Mode 5. Broader health check — deadline hygiene,\n   registration gaps, use-in-commerce questions on §8-approaching marks,\n   owner inconsistencies, expiration horizon, unwatched marks.\n\n7. **If the register is empty and an IP management system is connected:**\n   Offer Mode 1 — pull the portfolio from the system of record and\n   initialise the register.\n\n8. **Guardrail reminder:** Computed deadlines are reference only. Every\n   output closes with a line directing verification against the USPTO\n   TSDR, WIPO, or relevant registry before filing or paying. A\n   docketed-but-wrong deadline creates false confidence; do not let the\n   user treat this as the system of record unless the IP management\n   system is sync-integrated.\n\n## Examples\n\n```\n\u002Fip-legal:portfolio\n```\n\n```\n\u002Fip-legal:portfolio --report --days 180\n```\n\n```\n\u002Fip-legal:portfolio --add\n```\n\n```\n\u002Fip-legal:portfolio --update\n```\n\n```\n\u002Fip-legal:portfolio --audit\n```\n\n---\n\n## Works better connected\n\nThis skill tracks deadlines from what you tell it. It works much better\nconnected to:\n\n- **An IP management system (IPMS) via MCP** — Anaqua, Clarivate IPfolio,\n  AppColl, Patrix, Alt Legal, FoundationIP. A connected IPMS gives you the\n  full docket, maintenance fee schedules, and incoming correspondence in one\n  place, instead of the register being whatever the lawyer remembers to\n  paste. Ask your IPMS vendor if they have an MCP connector, or see\n  `CONNECTORS.md` at the repo root for how to get one added.\n- **USPTO directly via customer number** — pulls status, deadlines, and\n  correspondence for your whole portfolio rather than one application at a\n  time. Not currently available as an MCP; on the wish list in\n  `CONNECTORS.md`.\n\nWithout either, paste your docket or upload a spreadsheet and I'll track from\nthere.\n\n## Purpose\n\nA trademark registration that isn't renewed on time can be cancelled. A patent\nwithout its maintenance fee paid lapses. A domain that expires can be sniped\nwithin the hour. All of this is avoidable, and all of it depends on one thing:\nthe right deadline is on someone's calendar, tied to the right registration\nnumber, in the right jurisdiction.\n\nThis skill maintains that calendar.\n\n## Important: deadline reference caveat\n\n> The deadline rules this skill applies reflect publicly available requirements\n> as of the skill's build date. IP office requirements, grace periods, fee\n> structures, and maintenance schedules change. **Always confirm computed\n> deadlines against the USPTO TSDR \u002F Patent Center, WIPO Madrid Monitor \u002F\n> Patentscope, EUIPO eSearch, UKIPO online records, or the relevant national\n> registry before acting.** If you use Anaqua, CPA Global, Clarivate, Alt Legal,\n> or another IP management system, their docket is authoritative for your\n> assets — use this tracker to organize and surface their data, not to replace\n> it.\n>\n> A docketed-but-wrong deadline is worse than an undocketed one: it creates\n> false confidence. \"No deadline soon\" outputs especially deserve a second\n> look before you rely on them.\n\n## Jurisdiction and type assumptions\n\nMaintenance mechanics vary by jurisdiction and asset type:\n\n- **US trademarks:** §8 Declaration of Use between 5th and 6th anniversary of\n  registration (or §71 for Madrid designations), then combined §8\u002F§9 renewal\n  at 10 years and every 10 years thereafter. §15 Incontestability available\n  after 5 years of continuous use. 6-month grace period with surcharge for §8\n  and §9; no grace for the underlying use itself.\n- **Madrid International trademarks:** 10-year registration term renewable at\n  WIPO; individual designated countries may have local use or declaration\n  requirements (e.g., US §71).\n- **EUIPO trademarks:** 10-year renewal; 6-month grace with surcharge.\n- **US utility patents:** Maintenance fees due at 3.5, 7.5, and 11.5 years\n  from grant. 6-month grace window with surcharge; after that, potential\n  revival by petition if lapse was unintentional.\n- **US design patents:** No maintenance fees — 15-year term from grant for\n  applications filed on or after May 13, 2015 (14 years if earlier). No action\n  required mid-term.\n- **EPO \u002F national patents:** Annuities typically due annually from filing or\n  from national phase entry. National rules vary — confirm per jurisdiction.\n- **US copyright:** No maintenance for works created 1978 or later.\n  Pre-1978 works may have had renewal obligations; flag for attorney review\n  if the asset pre-dates 1964 (rarely in scope for modern portfolios).\n- **Domains:** Annual or multi-year renewal per registrar; typical 30-day\n  grace then redemption period (~30 days at high fee) then drop.\n\nIf the portfolio includes assets in jurisdictions not listed above, capture\nthe maintenance mechanic in the register's `custom_rules` block and the\nreport will surface them as `agent_managed` — confirm status with the\nforeign associate rather than computing a date this skill doesn't understand.\n\n---\n\n## The register\n\nLives at `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fip-legal\u002Fportfolio.yaml`.\nStructure:\n\n```yaml\n# IP Portfolio Register\n# Generated: [date]\n# Last updated: [date]\n# Disclaimer: computed deadlines are reference only — confirm with USPTO\u002FWIPO\u002F\n# relevant registry or the IP management system of record before acting.\n\nmetadata:\n  company: \"[Company Name]\"\n  generated: \"[date]\"\n  last_updated: \"[date]\"\n  last_audit: \"[date or null]\"\n  source_system: \"[Anaqua \u002F CPA Global \u002F manual \u002F none]\"\n\ncustom_rules:   # non-built-in jurisdictions captured manually\n  []\n\nassets:\n  - id: \"TM-US-001\"\n    type: \"trademark\"                          # trademark \u002F patent \u002F copyright \u002F design \u002F domain\n    jurisdiction: \"US\"\n    mark_or_title: \"[Mark or title]\"\n    owner: \"[Record owner — registered entity name]\"\n    status: \"registered\"                       # pending \u002F registered \u002F lapsed \u002F abandoned \u002F cancelled\n    application_number: \"[number or null]\"\n    registration_number: \"[number or null]\"\n    classes: [\"9\", \"42\"]                       # Nice classes for TM; CPC\u002FIPC for patents; null otherwise\n    filing_date: \"[YYYY-MM-DD or null]\"\n    registration_date: \"[YYYY-MM-DD or null]\"\n    priority_date: \"[YYYY-MM-DD or null]\"\n    grant_date: \"[YYYY-MM-DD or null]\"         # patents\n    next_deadlines:                            # computed; refreshed on --report and --audit\n      - type: \"§8 Declaration of Use\"\n        due_date: \"[YYYY-MM-DD]\"\n        grace_end: \"[YYYY-MM-DD or null]\"\n        basis: \"5th-6th anniversary of registration\"\n        action: \"File §8 Declaration of Use (or excusable nonuse)\"\n        status: \"upcoming\"                     # upcoming \u002F due_soon \u002F overdue \u002F grace \u002F filed\n    use_in_commerce: true                      # TM only — drives §8 analysis\n    agent_managed: false                       # true for foreign associate \u002F outside counsel managed\n    local_agent: null\n    docket_id: \"[IP-mgmt-system ID or null]\"\n    outside_counsel: \"[firm or null]\"\n    business_owner: \"[email or team]\"\n    notes: \"\"\n\n  - id: \"PAT-US-001\"\n    type: \"patent\"\n    jurisdiction: \"US\"\n    mark_or_title: \"[Invention title]\"\n    owner: \"[Owner]\"\n    status: \"granted\"\n    application_number: \"[number]\"\n    registration_number: \"[patent number]\"\n    filing_date: \"[YYYY-MM-DD]\"\n    grant_date: \"[YYYY-MM-DD]\"\n    priority_date: \"[YYYY-MM-DD or null]\"\n    expiration_date: \"[YYYY-MM-DD]\"            # 20 years from earliest non-provisional filing\n    next_deadlines:\n      - type: \"3.5-year maintenance fee\"\n        due_date: \"[YYYY-MM-DD]\"\n        grace_end: \"[YYYY-MM-DD]\"\n        basis: \"3.5 years from grant\"\n        action: \"Pay maintenance fee (small\u002Fmicro entity if applicable)\"\n        status: \"upcoming\"\n    claims_count: 20\n    entity_size: \"large\"                       # large \u002F small \u002F micro (drives USPTO fees)\n    docket_id: null\n    outside_counsel: null\n    business_owner: null\n    notes: \"\"\n```\n\nStatus values for `next_deadlines`:\n- `upcoming` — more than 90 days out\n- `due_soon` — due within 90 days, not yet filed\n- `overdue` — past the primary due date, within grace window (if any)\n- `grace` — in the grace period (explicit flag — carries surcharge)\n- `lapsed` — past grace with no action; asset effectively lost unless revivable\n- `filed` — action completed this cycle\n\n---\n\n## Mode 1: Initialise\n\nRun when no register exists, or with `--rebuild`.\n\n### Step 1: Determine the source\n\nRead `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fip-legal\u002FCLAUDE.md`:\n- **IP management system connected** (Anaqua, CPA Global, etc.): pull the portfolio via its integration. The IP system is the authoritative source; this register mirrors it and adds no deadlines the system doesn't already have.\n- **No IP management system, but spreadsheet \u002F export available:** ask the user to share the export. Import what's present; flag any asset missing a registration or grant date as `unknown` for deadline computation.\n- **Nothing at hand:** walk through assets interactively — type, jurisdiction, number, key dates, owner.\n\n### Step 2: For each asset, compute deadlines\n\nApply the rules at the top of this file. Populate `next_deadlines` with the\ntwo or three closest upcoming items — further-out deadlines (10-year renewals\ndecades away) are computed on demand during reports rather than stored\nspeculatively.\n\n**For assets the skill cannot confidently schedule:**\n- Unknown jurisdiction rules → add a stub under `custom_rules` and flag the\n  asset `agent_managed: true` with a TODO to confirm with the foreign associate.\n- Missing dates needed for computation (no grant date for a patent, no\n  registration date for a TM) → set `next_deadlines` empty with a note in\n  `notes`, and list the asset as `unknown` in the initialisation summary.\n\n### Step 3: Write the register\n\nGenerate `portfolio.yaml` at the config path. Show a summary:\n\n```\nPortfolio register initialised.\n\nAssets: [N]\n  Trademarks: [N]   ([N registered] \u002F [N pending])\n  Patents:    [N]   ([N granted] \u002F [N pending])\n  Copyrights: [N]\n  Designs:    [N]\n  Domains:    [N]\n\nDeadlines computed: [N]\nAgent-managed \u002F jurisdiction TBC: [N] — confirm with foreign associates\nUnknown (missing key dates): [N] — fill in before relying on reports\n\nRun \u002Fip-legal:portfolio --report to see what's due.\n```\n\n---\n\n## Mode 2: Report\n\n```\n\u002Fip-legal:portfolio --report [--days 30|60|90|180]\n```\n\nDefault window: 90 days. Refresh computed deadlines for every asset before\nproducing the report — don't rely on stored dates alone.\n\nOutput (prepend work-product header per `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fip-legal\u002FCLAUDE.md` → Outputs):\n\n```\nIP PORTFOLIO DEADLINE REPORT — [date]\n[Company Name] — window: next [N] days\n\n🔴 LAPSED \u002F IN GRACE ([N])\n  [Asset ID] \u002F [Jurisdiction] \u002F [Type] \u002F [Mark or title]\n    [Action] — original due [date], grace ends [date]\n    Status: [grace \u002F lapsed]\n\n⏰ DUE WITHIN [N] DAYS ([N])\n  [Asset ID] \u002F [Jurisdiction] \u002F [Type] \u002F [Mark or title]\n    [Action] — due [date]\n    Basis: [e.g., \"5th-6th anniversary of registration\"]\n    [Agent: firm \u002F docket: id — if present]\n\n🟡 UPCOMING (next window beyond 30 days, within [N] days)\n  [list]\n\n🌐 AGENT-MANAGED ([N])\n  [Asset ID] \u002F [Jurisdiction] — managed by [local agent]; confirm directly\n  [Asset ID] \u002F [Jurisdiction] — no local agent recorded; add with --update\n\n❓ UNKNOWN ([N])\n  [Asset ID] — missing [field]; cannot compute deadline\n  Confirm with [IP management system \u002F USPTO TSDR \u002F relevant registry] before relying on this report.\n\nSUMMARY\n  Total assets tracked: [N]\n  Deadlines in window: [N]\n  Last audit: [date]\n```\n\nClose the report with the caveat line: *\"Computed from portfolio register. Verify each deadline against the USPTO\u002FWIPO\u002Fregistry of record before filing or paying.\"*\n\nIf the report lists more than ~10 assets, 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 registration status (live \u002F in grace \u002F lapsed \u002F pending), a deadline timeline, and a sortable portfolio table with jurisdiction, type, and next-action date.\n\n---\n\n## Mode 3: Add\n\n```\n\u002Fip-legal:portfolio --add\n```\n\nInteractive add of a single asset. Ask for:\n1. Type (trademark \u002F patent \u002F copyright \u002F design \u002F domain)\n2. Jurisdiction\n3. Mark or title \u002F invention name\n4. Owner (record owner — matters for §8 filings and assignments)\n5. Key dates (per type: filing, registration, grant, priority, expiration)\n6. Number(s)\n7. Classes \u002F claims count\n8. Source — is this being tracked in the IP management system under a docket ID?\n9. Outside counsel \u002F foreign associate, if any\n10. Business owner (who does this matter to — product line, brand manager)\n\nAfter capture:\n- Compute next deadlines per the rules at the top of this file.\n- If jurisdiction rules aren't built in, walk through the `custom_rules` capture flow (see below).\n- Append to `assets:` in `portfolio.yaml`.\n\n### Custom rules capture\n\nWhen a jurisdiction isn't in the built-in list:\n\n> I don't have maintenance rules for [Jurisdiction] \u002F [Asset type] built in.\n> Let me capture them so we can track this going forward.\n>\n> 1. What maintenance events apply? (Renewal every N years? Annuities annually?\n>    Declarations of use? Something else?)\n> 2. What triggers the due date — filing date, registration date, grant date,\n>    national phase entry, anniversary of something else?\n> 3. Is there a grace period? At what cost?\n> 4. Is there a foreign associate or local agent managing this?\n\nStore under `custom_rules:` and apply to future assets in that jurisdiction.\n\n---\n\n## Mode 4: Update\n\n```\n\u002Fip-legal:portfolio --update\n```\n\n### Consequential-action gate\n\n**Before recording that a maintenance filing or fee payment was made:** Read\n`## Who's using this` in `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fip-legal\u002FCLAUDE.md`. If the Role is **Non-lawyer**:\n\n> Recording a §8 declaration, a §9 renewal, a patent maintenance fee payment,\n> or an international annuity as \"filed\" has consequences. If the record is\n> wrong — missed due date, wrong entity size, wrong specimen of use — the\n> deadline doesn't move, and the asset can still lapse. Have you confirmed\n> this with the attorney or foreign associate who actually made the filing\n> (or with the USPTO TSDR \u002F WIPO Madrid Monitor \u002F relevant registry)? If yes,\n> proceed. If no:\n>\n> - Do not record as filed yet.\n> - Here is what to bring to the attorney: asset ID, jurisdiction, deadline\n>   type, what the IP management system shows, what you believe was filed and\n>   when, and the source of that belief.\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\n> 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 set a deadline's `status` to `filed` past this gate without an\nexplicit yes. Status refresh, report generation, and upcoming-deadline\nsurfacing do not require the gate.\n\n### Sub-modes\n\n**Manual update:** \"We filed the §8 for TM-US-001 on March 4, specimen\nattached.\" Update the matching deadline: `status: filed`, `filed_date`,\nand compute the next deadline in its lifecycle (for §8 that's the §9\nrenewal 10 years out).\n\n**From IP management system sync:** If Anaqua \u002F CPA Global \u002F similar is\nconnected, pull the latest docket and reconcile. Flag mismatches between\nthe register and the system of record — the system of record wins; update\nthe register to match and surface anything the register had that the\nsystem doesn't.\n\n**Status change:** \"Mark TM-US-004 as abandoned.\" Update `status`, clear\n`next_deadlines`, note the date abandoned.\n\n---\n\n## Mode 5: Audit\n\n```\n\u002Fip-legal:portfolio --audit\n```\n\nBroader health check beyond this month's deadlines:\n\n**Deadline hygiene**\n- Any deadlines in `grace` status right now? (In progress but surcharge-costing.)\n- Any `lapsed` assets that aren't marked `abandoned` or `cancelled`? Either\n  revive or update status.\n- Any assets with no `next_deadlines` computed? Either missing data or a\n  jurisdiction the skill doesn't know.\n\n**Registration gaps**\n- Trademark applications filed more than 18 months ago still `pending`?\n  Flag for status check at the office — may need response to an action.\n- Patents filed more than 4 years ago still `pending`? Flag for prosecution\n  check.\n\n**Use-in-commerce (TM only)**\n- §8 approaching on a mark flagged `use_in_commerce: false` or uncertain?\n  The §8 requires use; mark needs a use audit before filing or an excusable\n  nonuse declaration.\n\n**Ownership hygiene**\n- Any assets where the `owner` is not a currently active entity per the\n  entity register (if available)? Flag — may need recordal of assignment.\n- Owner name inconsistencies across assets (same entity, different name\n  strings)? Surface for cleanup.\n\n**Expiration horizon**\n- Any patents expiring in the next 24 months? Even without a maintenance\n  deadline, the business may want to know — product planning, continuation\n  strategy, licensing window.\n\n**Unwatched assets**\n- Any registered marks not on the watch list in CLAUDE.md → Brand protection?\n  Flag as a gap for the attorney to decide whether to add.\n\nOutput format:\n\n```\nIP PORTFOLIO AUDIT — [date]\n\nDEADLINE HYGIENE\n  In grace: [N] — acting now avoids lapse\n  Lapsed (not marked abandoned): [N] — confirm status\n  Missing next-deadline computation: [N] — fill data or mark agent-managed\n\nREGISTRATION GAPS\n  TM applications pending >18 months: [list]\n  Patent applications pending >4 years: [list]\n\nUSE IN COMMERCE (TM)\n  §8 approaching on uncertain-use marks: [list]\n\nOWNERSHIP\n  Assets with unrecognised owner strings: [N]\n  Owner name inconsistencies: [list]\n\nEXPIRATION HORIZON (24 months)\n  Patents expiring: [list]\n\nBRAND WATCH\n  Registered marks not on watch list: [list]\n\nRECOMMENDED ACTIONS\n  1. [highest priority]\n  2. [etc.]\n```\n\n---\n\n## Integration: ip-renewal-watcher agent\n\nThe `ip-renewal-watcher` agent in this plugin runs this skill on a schedule\n(weekly by default) and posts the Mode 2 report to the channel named in\nCLAUDE.md → Renewal alerts. If 🔴 items appear (grace \u002F lapsed), the agent\nposts them immediately regardless of schedule.\n\n## Handoffs\n\n- Receives: new asset records from prosecution skills (when an application\n  is filed or a mark clears), from clearance skills (when a mark is adopted\n  and a filing is queued), and from assignment recordals.\n- Sends: \"file §8 now\" triggers to the attorney — this skill doesn't file\n  anything; it tells the attorney the deadline and what to bring.\n\n## What this skill does not do\n\n- It does not file anything. Every action it surfaces is for the attorney\n  or foreign associate to execute.\n- It does not verify deadlines against the USPTO TSDR, WIPO, or any other\n  registry. It computes them from the dates you give it. The register is\n  a working copy; the registry is the source of truth.\n- It does not decide whether to renew. Renewal is a business call — is the\n  mark still in use, is the patent still valuable, does the domain still\n  matter. This skill surfaces the deadline and the cost; the business and\n  the attorney decide.\n- It does not replace an IP management system for multi-hundred-asset\n  portfolios. Anaqua, CPA Global, Clarivate, Alt Legal, and similar systems\n  have direct registry feeds, deadline automation, and annuity payment\n  services. This skill is best suited for smaller portfolios, or as a\n  lightweight layer that surfaces what the system of record shows.\n- It does not read office records to verify status. A §8 shown as \"filed\"\n  here means someone told it so — not that the USPTO accepted it. Confirm\n  acceptance through TSDR or the IP management system.\n",{"name":5,"description":43,"argument-hint":44},"Track the IP portfolio — registrations, renewals, maintenance fees, and use declarations. Use when checking what's renewing, adding or updating an asset, recording a maintenance filing, or auditing the register for gaps, lapses, and use-in-commerce questions. Receives handoffs from prosecution and clearance work.\n","[--report [--days N] | --add | --update | --audit]","main","4a6c651889c97cc9140580363c73e0eb17379c2b","ip-legal\u002Fskills\u002Fportfolio",1958,"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-for-legal","https:\u002F\u002Fgithub.com\u002Fanthropics","https:\u002F\u002Fanthropic.com","2026-11-08 22:42:37",{"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 portfolio",{"tool":59,"command":60},"bunx","bunx skills add anthropics\u002Fclaude-for-legal --skill portfolio",{"tool":62,"command":63},"pnpm","pnpm dlx skills add anthropics\u002Fclaude-for-legal --skill portfolio","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-for-legal\u002Fblob\u002Fmain\u002Fip-legal\u002Fskills\u002Fportfolio\u002FSKILL.md",true,[],[68,95,116,135,157,170],{"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":38},"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,87,34,88,89,90,31,91,30,92,93,23,22,94],"reg","watcher","reg feed watcher","running","feeds","filtered","diff","development","classification","new","now","scheduled","check","last","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":38},"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,34,104,105,106,31,107,30,108,29,109,110,111,112,113,114,94,115],"policy","policy redraft","up","fix","produce","documents","drafting","review","draft","id","gap","mark","first","direct",{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":38},"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,123,124,30,125,126,80,127,81,128,129,130,131,31,132,112,133,134,94],"policy diff","which","you","analysis","text","change","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":38},"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,124,144,145,146,89,31,30,125,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":29,"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":38},"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",[],[29,111,112,163,151,164,165,166,167,31,168,30,169],"risk","tracker","remediation","status","open","accept","user",{"skillNo":171,"name":172,"nameZh":6,"description":173,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":174,"categories":175,"keywords":181,"publishedAt":38},"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",[176],{"categoryNo":177,"categoryName":178,"taxonomyType":179,"taxonomyTypeDesc":180},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[112,182,183,184,86,102,185,167,186,187,188,189,29,190,27,191,192,164,165,193],"gap surfacer","shared","tracks","send","confirmation","aging","false","comments","with","slack","via","surfaces"]