[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75HVZCHPFRQSPSCK2X1M4WS":3,"skill-same:01M75HVZCHPFRQSPSCK2X1M4WS":54},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":30,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":6,"updatedAt":33,"install":34,"resources":47},"01M75HVZCHPFRQSPSCK2X1M4WS","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.","agisota\u002Fold-one","agisota","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F121413592?v=4","01M75B4BRNT67EC1NDRT8QZEP2","01M75B4BS7QR9VP580MSCPTS3X",3,"MIT","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Frenewal-tracker\u002FSKILL.md",[],[],"2026-11-12 13:55:43",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":23,"argument-hint":24},"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","f37de8f681f0c0ca0e0ebab6e5fddf764ca7553d","skills\u002Frenewal-tracker",1,"https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one","https:\u002F\u002Fagisota.github.io\u002Fold-one\u002F","https:\u002F\u002Fgithub.com\u002Fagisota","pzd.world","2026-07-04 22:32:06",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add agisota\u002Fold-one --skill renewal-tracker",{"tool":40,"command":41},"bunx","bunx skills add agisota\u002Fold-one --skill renewal-tracker",{"tool":43,"command":44},"pnpm","pnpm dlx skills add agisota\u002Fold-one --skill renewal-tracker","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Frenewal-tracker\u002FSKILL.md",true,[48],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"references\u002Frenewal-register.yaml","REFERENCE","参考文档",816,"https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Frenewal-tracker\u002Freferences\u002Frenewal-register.yaml",[55,62,69,78,85,92],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":18},"01M75KRGZWQWE9JDBS6RX42NWV","zoom-out","Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fzoom-out\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":18},"01M75KRCZHKE0ZYAQFFYHS0YNP","zeroize-audit","Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C\u002FC++\u002FRust code handling secrets, keys, passwords, or other sensitive data.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fzeroize-audit\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":73,"licenseFileUrl":74,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":18},"01M75KR94KYQ30DTE1P9WNDAE0","yeet","Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":18},"01M75KR3H13YJ9QHMD49818FA1","yara-rule-authoring","Guides authoring of high-quality YARA-X detection rules for malware identification. Use when writing, reviewing, or optimizing YARA rules. Covers naming conventions, string selection, performance optimization, migration from legacy YARA, and false positive reduction. Triggers on: YARA, YARA-X, malware detection, threat hunting, IOC, signature, crx module, dex module.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyara-rule-authoring\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":18},"01M75KQMPY8A4Y8XTDD2DT0M9T","x-twitter-growth","X\u002FTwitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X\u002FTwitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fx-twitter-growth\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":18},"01M75KQHNZ0ANZNJGZY6M8MDAK","x-api","X\u002FTwitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fx-api\u002FSKILL.md",[],[]]