[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M718BF048K1KHQR7TGD1XKHD":3,"skill-same:01M718BF048K1KHQR7TGD1XKHD":74},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":49,"repositoryHtmlUrl":50,"repositoryHomepageUrl":6,"ownerHtmlUrl":51,"ownerBlogUrl":52,"ownerDescription":6,"updatedAt":53,"install":54,"resources":67},"01M718BF048K1KHQR7TGD1XKHD","renewal-tracker",null,"Show contracts with cancel-by deadlines coming up and warn before notice windows close, working from a maintained renewal register. Use when the user asks \"what's renewing soon\", \"what renewals are due\", \"did we miss a cancellation window\", \"add this to the renewal tracker\", or on a scheduled basis. Receives handoffs from saas-msa-review.","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\u002Fcommercial-legal\u002Fskills\u002Frenewal-tracker\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"tracker","renewal tracker","close","missed","window","change","with","review","saas","cancel","when","scheduled","use","up","for","register","show","notice","windows","msa","2026-11-10 10:12:30",false,"---\nname: renewal-tracker\ndescription: >\n  Show contracts with cancel-by deadlines coming up and warn before notice windows\n  close, working from a maintained renewal register. Use when the user asks \"what's\n  renewing soon\", \"what renewals are due\", \"did we miss a cancellation window\", \"add\n  this to the renewal tracker\", or on a scheduled basis. Receives handoffs from\n  saas-msa-review.\nargument-hint: \"[--days N to change window | --missed for lapsed windows]\"\n---\n\n# \u002Frenewal-tracker\n\nSurfaces what's renewing and when you have to cancel by.\n\n## Instructions\n\n1. **Read `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcommercial-legal\u002Frenewal-register.yaml`** (the config directory — survives plugin updates).\n\n2. **Default mode:** Mode 2 — what's coming up in the next 90 days, grouped by urgency using half-open intervals so each deadline lands in exactly one band: 🔴 0–13 days, 🟠 14–44 days, 🟡 45–89 days. Days 14, 45, and 90 are boundaries — each belongs to exactly one band, not two.\n\n3. **`--days N`:** Change the window.\n\n4. **`--missed`:** Mode 4 — cancel-by deadlines that passed without recorded cancellation.\n\n5. **If register is empty and the [CLM] is connected:** Offer Mode 3 — scan the [CLM] for active agreements with renewal dates and bulk-load.\n\n6. **Output includes recommended actions:** who to ping (the business owner from each register entry), which ones have uncapped pricing (get leverage before window closes).\n\n## Examples\n\n```\n\u002Fcommercial-legal:renewal-tracker\n```\n\n```\n\u002Fcommercial-legal:renewal-tracker --days 180\n```\n\n```\n\u002Fcommercial-legal:renewal-tracker --missed\n```\n\n---\n\n## Purpose\n\nNobody reads a contract twice. The renewal date is extracted once, at review time, and then it lives somewhere — ideally somewhere that shouts at you 45 days before the cancel-by deadline, not 45 days after.\n\nThis skill maintains the renewal register and surfaces what's coming.\n\n## The register\n\nLives at `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcommercial-legal\u002Frenewal-register.yaml` (the config directory — survives plugin updates). Each entry:\n\n```yaml\n- counterparty: \"Acme SaaS Inc.\"\n  agreement: \"Acme Platform Subscription Agreement\"\n  signed_date: 2025-06-15\n  initial_term_end: 2026-06-15\n  current_term_end: 2026-06-15     # rolls forward after each auto-renewal; compute cancel_by_* from this\n  renewal_mechanism: \"auto-renew annual\"\n  notice_period_days: 60\n  notice_method: \"email\"           # email \u002F portal \u002F certified mail \u002F registered post \u002F courier \u002F per contract §X\n  transit_buffer_days: 0           # 0 for electronic, 5 for domestic certified mail, 10 for international registered post — or per contract if specified\n  cancel_by_calendar: 2026-04-16    # current_term_end minus notice_period_days\n  cancel_by_effective: 2026-04-16   # rolled back to last business day if needed\n  send_by_effective: 2026-04-16    # cancel_by_effective minus transit_buffer_days — the date you must SEND the notice\n  cancel_by_roll_note: \"\"           # e.g., \"rolled back from Sunday 2026-11-01; verify against contract's business-day definition\"\n  cancel_by_provenance: \"[model calculation — verify against the notice clause]\"\n  price_on_renewal: \"then-current list (uncapped)\"\n  annual_value: 48000\n  business_owner: \"jane@company.com\"\n  clm_id:        \"IC-12345\"        # if connected\n  docusign_envelope: \"abc-123\"   # if connected\n  status: \"active\"               # active | cancelled | renewed | lapsed\n  notes: \"Pricing uncapped — revisit before renewal. Alt vendors: X, Y.\"\n```\n\n**Notice transit time — alert off `send_by_effective`, not `cancel_by_effective`.** A 60-day window with a certified-mail requirement is really ~55 days. The tracker that alerts on the received-by date is the tracker that misses the deadline. Compute `send_by_effective = cancel_by_effective - transit_buffer_days` and fire alerts (the 🔴 \u002F 🟠 \u002F 🟡 urgency bands in Mode 2) off `send_by_effective`. Mode 2's urgency column shows `send_by_effective`; a detail column surfaces `cancel_by_effective`, `notice_method`, and `transit_buffer_days` so the reader can see the delta and challenge the buffer.\n\n**Rolling renewals — the register that doesn't roll forward is the register that's right once.** Store `initial_term_end` for the record, but compute `cancel_by_*` from `current_term_end`. When a renewal fires (the cancel window passes and no notice was given), prompt:\n\n> This contract auto-renewed on [date]. Update the register: new `current_term_end` is [date + renewal period], new `cancel_by_effective` is [computed], new `send_by_effective` is [computed]. Confirm?\n\nAfter year one, `initial_term_end` is wrong and only `current_term_end` produces a correct cancel-by date.\n\n## Business-day check on every cancel-by date\n\n**The register's cancel-by date must be the last BUSINESS DAY on which notice\nis effective, not the calendar date.** A calendar date that falls on a\nweekend is the single most common way a renewal deadline gets missed. The\nregister catches it.\n\nWhen you compute (or ingest) a cancel-by date:\n\n1. **Compute the calendar date.** `cancel_by_calendar = initial_term_end − notice_period_days` (or whatever the clause specifies). This is the raw arithmetic.\n2. **Business-day roll-back keyed to governing law.** The contract's governing law determines which holidays count. US: federal holidays + the state's holidays if governing law is a state. England & Wales: bank holidays. Germany: Feiertage (vary by Bundesland — ask which). Canada: federal + provincial. Singapore: public holidays. If Saturday, roll back to Friday. If Sunday, roll back to Friday. If a holiday in the governing-law jurisdiction, roll back to the prior business day. Roll BACK, never forward — forward means notice arrives after the window closes. For non-US governing law, if you can't determine the holiday calendar, flag it: \"Governing law is [X] — business-day roll-back uses US federal holidays as a placeholder. Verify against the [jurisdiction] holiday calendar before relying on the effective date.\"\n3. **Check the contract's own day-counting rule.** Look for \"business day,\" \"received by,\" \"deemed received,\" \"5:00 p.m. [local time],\" or a notice-method clause. If the contract defines \"business day\" or specifies receipt mechanics (certified mail, email with read receipt), that definition controls. Flag any mismatch between the default roll-back and the contract's own rule.\n4. **Record BOTH dates in the register.** `cancel_by_calendar` is the raw arithmetic; `cancel_by_effective` is the last business day on which notice is effective; `cancel_by_roll_note` records why they differ (e.g., \"rolled back from Sunday 2026-11-01; verify against contract's business-day definition\"). Every computed `cancel_by_effective` carries a `cancel_by_provenance` tag of `[model calculation — verify against the notice clause]` so the verify flag travels with the date, not with the surrounding prose.\n5. **Fire alerts off the EFFECTIVE date, not the calendar date.** Urgency bands (🔴 \u002F 🟠 \u002F 🟡 in Mode 2) use `cancel_by_effective`. Mode 2 output shows `cancel_by_effective` in the urgency column and surfaces `cancel_by_calendar` and `cancel_by_roll_note` in a detail column where the roll-back happened, so the reader can see it and challenge it.\n\nA Mode 2 report that prints `cancel_by: 2026-11-01` (a Sunday) with no weekday and no warning is a silently wrong effective deadline. The register is the place to catch it — once, at ingest — not later, when the window has already moved.\n\n## Modes\n\n### Mode 1: Ingest a renewal (handoff from review)\n\nWhen saas-msa-review or vendor-agreement-review finds a renewal clause, it hands off a record. Append it to the register. If the counterparty already has an entry, ask whether this is a replacement (renewed agreement) or an additional agreement.\n\n### Mode 2: What's coming up\n\n**Default lookback window:** next 90 days.\n\n**Urgency bands are half-open intervals — a deadline lives in exactly one band.** Use days-until-cancel-by (`cancel_by_effective - today`). Day 14, 45, and 90 each belong to exactly one band, not two; an off-by-one here puts the most-urgent items into the less-urgent bucket.\n\n- 🔴 **0–13 days** (cancel-by in less than 14 days — including today)\n- 🟠 **14–44 days**\n- 🟡 **45–89 days**\n- (everything 90+ days is outside the default lookback window; include only if the user passed `--horizon` beyond 90)\n\n```markdown\n## Renewals — next 90 days\n\n### 🔴 Cancel-by deadline in 0–13 days\n\n| Counterparty | Cancel by | Renewal date | Annual $ | Owner | Notes |\n|---|---|---|---|---|---|\n| [name] | **[date]** | [date] | $[n] | [email] | [notes] |\n\n### 🟠 Cancel-by deadline in 14–44 days\n\n[same table]\n\n### 🟡 Cancel-by deadline in 45–89 days\n\n[same table]\n\n---\n\n**Recommended actions:**\n- [ ] [Counterparty] — ping [business owner]: do we want to keep this?\n- [ ] [Counterparty] — pricing is uncapped; get a quote from an alternative before we lose leverage\n```\n\nIf the register has more than ~10 renewals in the window, 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 urgency tier (🔴 \u002F 🟠 \u002F 🟡), a cancel-by timeline, and a sortable register with counterparty, renewal date, annual $, and owner.\n\n### Mode 3: Scan the [CLM] \u002F e-signature tool to populate the register\n\nIf MCPs are connected and the register is empty or stale:\n\n1. Query the [CLM] for all agreements with status \"Active\" and a renewal date field\n2. Query DocuSign for completed envelopes in the last 24 months with \"subscription\" \u002F \"renewal\" \u002F \"auto-renew\" in metadata\n3. For each hit, extract renewal mechanics and add to register\n4. Flag any where the renewal date can't be determined from metadata — those need a human to read the contract\n\nThis is a one-time bulk load. After that, ingest happens at review time.\n\n### Mode 4: Missed windows (the bad news report)\n\n```markdown\n## Missed cancellation windows\n\nThe following agreements had cancel-by deadlines that have passed and no\ncancellation was recorded:\n\n| Counterparty | Cancel-by was | Renewal date | Status |\n|---|---|---|---|\n| [name] | [date] | [date] | Will auto-renew on [date] |\n\n**Options:**\n- Negotiate late cancellation (rarely works but worth asking)\n- Accept the renewal, mark next year's cancel-by now\n- Check the agreement for any other termination rights (for convenience, for cause)\n```\n\n## Gate: accepting or declining a renewal\n\nTracking a renewal date is research. *Acting* on it — sending a notice of non-renewal, letting an auto-renewal fire, or countersigning a renewal form — is a consequential legal step.\n\n**Before proceeding to accept or decline a renewal (including sending a non-renewal notice or letting an auto-renewal run past the cancel-by date):** Read `## Who's using this` in `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcommercial-legal\u002FCLAUDE.md`. If the Role is Non-lawyer:\n\n> This step has legal consequences (you're either committing to another term or terminating the relationship). Have you reviewed this with an attorney? If yes, proceed. If no, here's a brief to bring to them:\n>\n> [Generate a 1-page summary: counterparty, current term end and cancel-by date, renewal price mechanism, what happens if we do nothing, alternative vendors if we want to shop, and the three things to ask the attorney before the window closes.]\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 proceed past this gate without an explicit yes.\n\n## Integration: renewal-watcher agent\n\nThe renewal-watcher agent in this plugin runs this skill on a schedule (weekly by default) and posts the \"coming up\" report to the channel named in `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcommercial-legal\u002FCLAUDE.md` → `## House style` → where work product goes. Mode 2 is the agent's primary output.\n\n## What this skill does not do\n\n- It does not cancel contracts. It tells you when to decide.\n- It does not decide whether to renew. It surfaces the deadline and the business owner.\n- It does not read contracts to find renewal dates — that happens at review time. If a contract is in the register without a renewal date, it was added manually and someone needs to fill in the gap.\n","# \u002Frenewal-tracker\n\nSurfaces what's renewing and when you have to cancel by.\n\n## Instructions\n\n1. **Read `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcommercial-legal\u002Frenewal-register.yaml`** (the config directory — survives plugin updates).\n\n2. **Default mode:** Mode 2 — what's coming up in the next 90 days, grouped by urgency using half-open intervals so each deadline lands in exactly one band: 🔴 0–13 days, 🟠 14–44 days, 🟡 45–89 days. Days 14, 45, and 90 are boundaries — each belongs to exactly one band, not two.\n\n3. **`--days N`:** Change the window.\n\n4. **`--missed`:** Mode 4 — cancel-by deadlines that passed without recorded cancellation.\n\n5. **If register is empty and the [CLM] is connected:** Offer Mode 3 — scan the [CLM] for active agreements with renewal dates and bulk-load.\n\n6. **Output includes recommended actions:** who to ping (the business owner from each register entry), which ones have uncapped pricing (get leverage before window closes).\n\n## Examples\n\n```\n\u002Fcommercial-legal:renewal-tracker\n```\n\n```\n\u002Fcommercial-legal:renewal-tracker --days 180\n```\n\n```\n\u002Fcommercial-legal:renewal-tracker --missed\n```\n\n---\n\n## Purpose\n\nNobody reads a contract twice. The renewal date is extracted once, at review time, and then it lives somewhere — ideally somewhere that shouts at you 45 days before the cancel-by deadline, not 45 days after.\n\nThis skill maintains the renewal register and surfaces what's coming.\n\n## The register\n\nLives at `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcommercial-legal\u002Frenewal-register.yaml` (the config directory — survives plugin updates). Each entry:\n\n```yaml\n- counterparty: \"Acme SaaS Inc.\"\n  agreement: \"Acme Platform Subscription Agreement\"\n  signed_date: 2025-06-15\n  initial_term_end: 2026-06-15\n  current_term_end: 2026-06-15     # rolls forward after each auto-renewal; compute cancel_by_* from this\n  renewal_mechanism: \"auto-renew annual\"\n  notice_period_days: 60\n  notice_method: \"email\"           # email \u002F portal \u002F certified mail \u002F registered post \u002F courier \u002F per contract §X\n  transit_buffer_days: 0           # 0 for electronic, 5 for domestic certified mail, 10 for international registered post — or per contract if specified\n  cancel_by_calendar: 2026-04-16    # current_term_end minus notice_period_days\n  cancel_by_effective: 2026-04-16   # rolled back to last business day if needed\n  send_by_effective: 2026-04-16    # cancel_by_effective minus transit_buffer_days — the date you must SEND the notice\n  cancel_by_roll_note: \"\"           # e.g., \"rolled back from Sunday 2026-11-01; verify against contract's business-day definition\"\n  cancel_by_provenance: \"[model calculation — verify against the notice clause]\"\n  price_on_renewal: \"then-current list (uncapped)\"\n  annual_value: 48000\n  business_owner: \"jane@company.com\"\n  clm_id:        \"IC-12345\"        # if connected\n  docusign_envelope: \"abc-123\"   # if connected\n  status: \"active\"               # active | cancelled | renewed | lapsed\n  notes: \"Pricing uncapped — revisit before renewal. Alt vendors: X, Y.\"\n```\n\n**Notice transit time — alert off `send_by_effective`, not `cancel_by_effective`.** A 60-day window with a certified-mail requirement is really ~55 days. The tracker that alerts on the received-by date is the tracker that misses the deadline. Compute `send_by_effective = cancel_by_effective - transit_buffer_days` and fire alerts (the 🔴 \u002F 🟠 \u002F 🟡 urgency bands in Mode 2) off `send_by_effective`. Mode 2's urgency column shows `send_by_effective`; a detail column surfaces `cancel_by_effective`, `notice_method`, and `transit_buffer_days` so the reader can see the delta and challenge the buffer.\n\n**Rolling renewals — the register that doesn't roll forward is the register that's right once.** Store `initial_term_end` for the record, but compute `cancel_by_*` from `current_term_end`. When a renewal fires (the cancel window passes and no notice was given), prompt:\n\n> This contract auto-renewed on [date]. Update the register: new `current_term_end` is [date + renewal period], new `cancel_by_effective` is [computed], new `send_by_effective` is [computed]. Confirm?\n\nAfter year one, `initial_term_end` is wrong and only `current_term_end` produces a correct cancel-by date.\n\n## Business-day check on every cancel-by date\n\n**The register's cancel-by date must be the last BUSINESS DAY on which notice\nis effective, not the calendar date.** A calendar date that falls on a\nweekend is the single most common way a renewal deadline gets missed. The\nregister catches it.\n\nWhen you compute (or ingest) a cancel-by date:\n\n1. **Compute the calendar date.** `cancel_by_calendar = initial_term_end − notice_period_days` (or whatever the clause specifies). This is the raw arithmetic.\n2. **Business-day roll-back keyed to governing law.** The contract's governing law determines which holidays count. US: federal holidays + the state's holidays if governing law is a state. England & Wales: bank holidays. Germany: Feiertage (vary by Bundesland — ask which). Canada: federal + provincial. Singapore: public holidays. If Saturday, roll back to Friday. If Sunday, roll back to Friday. If a holiday in the governing-law jurisdiction, roll back to the prior business day. Roll BACK, never forward — forward means notice arrives after the window closes. For non-US governing law, if you can't determine the holiday calendar, flag it: \"Governing law is [X] — business-day roll-back uses US federal holidays as a placeholder. Verify against the [jurisdiction] holiday calendar before relying on the effective date.\"\n3. **Check the contract's own day-counting rule.** Look for \"business day,\" \"received by,\" \"deemed received,\" \"5:00 p.m. [local time],\" or a notice-method clause. If the contract defines \"business day\" or specifies receipt mechanics (certified mail, email with read receipt), that definition controls. Flag any mismatch between the default roll-back and the contract's own rule.\n4. **Record BOTH dates in the register.** `cancel_by_calendar` is the raw arithmetic; `cancel_by_effective` is the last business day on which notice is effective; `cancel_by_roll_note` records why they differ (e.g., \"rolled back from Sunday 2026-11-01; verify against contract's business-day definition\"). Every computed `cancel_by_effective` carries a `cancel_by_provenance` tag of `[model calculation — verify against the notice clause]` so the verify flag travels with the date, not with the surrounding prose.\n5. **Fire alerts off the EFFECTIVE date, not the calendar date.** Urgency bands (🔴 \u002F 🟠 \u002F 🟡 in Mode 2) use `cancel_by_effective`. Mode 2 output shows `cancel_by_effective` in the urgency column and surfaces `cancel_by_calendar` and `cancel_by_roll_note` in a detail column where the roll-back happened, so the reader can see it and challenge it.\n\nA Mode 2 report that prints `cancel_by: 2026-11-01` (a Sunday) with no weekday and no warning is a silently wrong effective deadline. The register is the place to catch it — once, at ingest — not later, when the window has already moved.\n\n## Modes\n\n### Mode 1: Ingest a renewal (handoff from review)\n\nWhen saas-msa-review or vendor-agreement-review finds a renewal clause, it hands off a record. Append it to the register. If the counterparty already has an entry, ask whether this is a replacement (renewed agreement) or an additional agreement.\n\n### Mode 2: What's coming up\n\n**Default lookback window:** next 90 days.\n\n**Urgency bands are half-open intervals — a deadline lives in exactly one band.** Use days-until-cancel-by (`cancel_by_effective - today`). Day 14, 45, and 90 each belong to exactly one band, not two; an off-by-one here puts the most-urgent items into the less-urgent bucket.\n\n- 🔴 **0–13 days** (cancel-by in less than 14 days — including today)\n- 🟠 **14–44 days**\n- 🟡 **45–89 days**\n- (everything 90+ days is outside the default lookback window; include only if the user passed `--horizon` beyond 90)\n\n```markdown\n## Renewals — next 90 days\n\n### 🔴 Cancel-by deadline in 0–13 days\n\n| Counterparty | Cancel by | Renewal date | Annual $ | Owner | Notes |\n|---|---|---|---|---|---|\n| [name] | **[date]** | [date] | $[n] | [email] | [notes] |\n\n### 🟠 Cancel-by deadline in 14–44 days\n\n[same table]\n\n### 🟡 Cancel-by deadline in 45–89 days\n\n[same table]\n\n---\n\n**Recommended actions:**\n- [ ] [Counterparty] — ping [business owner]: do we want to keep this?\n- [ ] [Counterparty] — pricing is uncapped; get a quote from an alternative before we lose leverage\n```\n\nIf the register has more than ~10 renewals in the window, 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 urgency tier (🔴 \u002F 🟠 \u002F 🟡), a cancel-by timeline, and a sortable register with counterparty, renewal date, annual $, and owner.\n\n### Mode 3: Scan the [CLM] \u002F e-signature tool to populate the register\n\nIf MCPs are connected and the register is empty or stale:\n\n1. Query the [CLM] for all agreements with status \"Active\" and a renewal date field\n2. Query DocuSign for completed envelopes in the last 24 months with \"subscription\" \u002F \"renewal\" \u002F \"auto-renew\" in metadata\n3. For each hit, extract renewal mechanics and add to register\n4. Flag any where the renewal date can't be determined from metadata — those need a human to read the contract\n\nThis is a one-time bulk load. After that, ingest happens at review time.\n\n### Mode 4: Missed windows (the bad news report)\n\n```markdown\n## Missed cancellation windows\n\nThe following agreements had cancel-by deadlines that have passed and no\ncancellation was recorded:\n\n| Counterparty | Cancel-by was | Renewal date | Status |\n|---|---|---|---|\n| [name] | [date] | [date] | Will auto-renew on [date] |\n\n**Options:**\n- Negotiate late cancellation (rarely works but worth asking)\n- Accept the renewal, mark next year's cancel-by now\n- Check the agreement for any other termination rights (for convenience, for cause)\n```\n\n## Gate: accepting or declining a renewal\n\nTracking a renewal date is research. *Acting* on it — sending a notice of non-renewal, letting an auto-renewal fire, or countersigning a renewal form — is a consequential legal step.\n\n**Before proceeding to accept or decline a renewal (including sending a non-renewal notice or letting an auto-renewal run past the cancel-by date):** Read `## Who's using this` in `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcommercial-legal\u002FCLAUDE.md`. If the Role is Non-lawyer:\n\n> This step has legal consequences (you're either committing to another term or terminating the relationship). Have you reviewed this with an attorney? If yes, proceed. If no, here's a brief to bring to them:\n>\n> [Generate a 1-page summary: counterparty, current term end and cancel-by date, renewal price mechanism, what happens if we do nothing, alternative vendors if we want to shop, and the three things to ask the attorney before the window closes.]\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 proceed past this gate without an explicit yes.\n\n## Integration: renewal-watcher agent\n\nThe renewal-watcher agent in this plugin runs this skill on a schedule (weekly by default) and posts the \"coming up\" report to the channel named in `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Fcommercial-legal\u002FCLAUDE.md` → `## House style` → where work product goes. Mode 2 is the agent's primary output.\n\n## What this skill does not do\n\n- It does not cancel contracts. It tells you when to decide.\n- It does not decide whether to renew. It surfaces the deadline and the business owner.\n- It does not read contracts to find renewal dates — that happens at review time. If a contract is in the register without a renewal date, it was added manually and someone needs to fill in the gap.\n",{"name":5,"description":44,"argument-hint":45},"Show contracts with cancel-by deadlines coming up and warn before notice windows close, working from a maintained renewal register. Use when the user asks \"what's renewing soon\", \"what renewals are due\", \"did we miss a cancellation window\", \"add this to the renewal tracker\", or on a scheduled basis. Receives handoffs from saas-msa-review.\n","[--days N to change window | --missed for lapsed windows]","main","4a6c651889c97cc9140580363c73e0eb17379c2b","commercial-legal\u002Fskills\u002Frenewal-tracker",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":55,"prompt":65,"zipAvailable":66},[56,59,62],{"tool":57,"command":58},"npx","npx skills add anthropics\u002Fclaude-for-legal --skill renewal-tracker",{"tool":60,"command":61},"bunx","bunx skills add anthropics\u002Fclaude-for-legal --skill renewal-tracker",{"tool":63,"command":64},"pnpm","pnpm dlx skills add anthropics\u002Fclaude-for-legal --skill renewal-tracker","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-for-legal\u002Fblob\u002Fmain\u002Fcommercial-legal\u002Fskills\u002Frenewal-tracker\u002FSKILL.md",true,[68],{"path":69,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Frenewal-register.yaml","REFERENCE","参考文档",816,"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-for-legal\u002Fblob\u002Fmain\u002Fcommercial-legal\u002Fskills\u002Frenewal-tracker\u002Freferences\u002Frenewal-register.yaml",[75,103,123,141,162,174],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":86,"publishedAt":39},"01M718SG9G2R92ECCD0HYK2R5E","reg-feed-watcher","Check regulatory feeds now and report what's new since the last check, filtered by your materiality threshold. Use when the user says \"check the feeds\", \"what's new\", \"regulatory update\", when running from the scheduled agent, or when manually pasting a regulatory development for classification and diff.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-for-legal\u002Fblob\u002Fmain\u002Fregulatory-legal\u002Fskills\u002Freg-feed-watcher\u002FSKILL.md",[81],{"categoryNo":82,"categoryName":83,"taxonomyType":84,"taxonomyTypeDesc":85},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[87,88,89,90,91,92,93,94,33,95,96,97,31,30,29,98,99,100,101,102],"reg","watcher","reg feed watcher","running","feeds","filtered","diff","development","classification","new","now","check","last","update","report","regulatory",{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":39},"01M718SCRTBN55DMTVSPG67A7N","policy-redraft","Produce a proposed marked-up policy redraft that closes a gap found by \u002Fregulatory-legal:gaps or \u002Fregulatory-legal:policy-diff. A first draft for internal review — not for direct application to approved policy documents. Use when the user says \"redraft the policy\", \"draft the policy fix\", \"mark up the policy\", or when gap-surfacer hands off a gap for drafting.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-for-legal\u002Fblob\u002Fmain\u002Fregulatory-legal\u002Fskills\u002Fpolicy-redraft\u002FSKILL.md",[],[110,111,93,33,32,112,113,31,114,29,115,116,26,117,118,119,120,121,102,122],"policy","policy redraft","fix","produce","documents","drafting","gaps","draft","id","gap","mark","first","direct",{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":39},"01M718S8RV0C4NMVKG078CBFXP","policy-diff","Diff a specific regulatory change against the indexed policy library. Use when a reg has changed and you need to know which policies it touches and what the gap is, when the user says \"diff this reg against our policies\", \"which policy does this affect\", or \"gap analysis\", or when reg-feed-watcher hands off a material item.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-for-legal\u002Fblob\u002Fmain\u002Fregulatory-legal\u002Fskills\u002Fpolicy-diff\u002FSKILL.md",[],[93,110,130,131,29,132,133,87,134,88,24,135,136,137,31,138,119,139,140,102],"policy diff","which","you","analysis","text","paste","library","material","gap analysis","what the","name",{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":145,"categories":146,"keywords":147,"publishedAt":39},"01M718S6521Y0FT4T24VCFKVG5","matter-workspace","Manage matter workspaces — create, list, switch, close, or detach the active matter (practice-level). Use when working across multiple clients or matters and you need to keep one engagement's context separate from another, or when a substantive skill needs to know which matter it's working in.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-for-legal\u002Fblob\u002Fmain\u002Fregulatory-legal\u002Fskills\u002Fmatter-workspace\u002FSKILL.md",[],[148,149,131,150,151,152,96,31,29,132,153,154,155,156,21,157,158,159,160,161],"workspace","matter workspace","switch","manage","workspaces","keep","across","create","engagement","active","clients","list","it","context",{"skillNo":163,"name":116,"nameZh":6,"description":164,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":165,"categories":166,"keywords":167,"publishedAt":39},"01M718S3FPEJNQGCMQ1AR8M4HE","Open gaps tracker — what's flagged and not yet closed. Use when the user asks \"what gaps are open\", \"gap tracker\", \"remediation status\", or wants to close (--close GAP-ID) or risk-accept (--accept GAP-ID) a tracked gap.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-for-legal\u002Fblob\u002Fmain\u002Fregulatory-legal\u002Fskills\u002Fgaps\u002FSKILL.md",[],[116,118,119,168,21,19,169,170,171,31,172,29,173],"risk","remediation","status","open","accept","user",{"skillNo":175,"name":176,"nameZh":6,"description":177,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":178,"categories":179,"keywords":185,"publishedAt":39},"01M718S06WSZ9Y24JKYM0VVPPE","gap-surfacer","Reference: shared gap- and comment-tracker framework backing \u002Fregulatory-legal:gaps and \u002Fregulatory-legal:comments. Tracks open policy gaps with remediation status, ingests gaps from policy-diff, surfaces what's open and aging, routes to owners, and notifies gap owners via Slack with per-send confirmation. Loaded by the gaps and comments skills before doing substantive work.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-for-legal\u002Fblob\u002Fmain\u002Fregulatory-legal\u002Fskills\u002Fgap-surfacer\u002FSKILL.md",[180],{"categoryNo":181,"categoryName":182,"taxonomyType":183,"taxonomyTypeDesc":184},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[119,186,187,188,93,110,189,171,190,191,192,193,116,25,194,195,196,19,169,197],"gap surfacer","shared","tracks","send","confirmation","aging","false","comments","work","slack","via","surfaces"]