cowork-contract-renewal-radar — Claude Code skill: setup and features
cowork-contract-renewal-radar — a skill for Claude Code and Codex that audits contract folders, extracts notice terms, and calculates actual renewal decision deadlines.
MIT 105 installs ★ 440 updated 2026-10-20
npx skills add OneWave-AI/claude-skills --skill cowork-contract-renewal-radar -a claude-codeWhat cowork-contract-renewal-radar does
The skill catalogs executed PDF and .docx agreements across a target folder, separating drafts and gathering terms into renewal-calendar.md for a 24-month horizon. It isolates term dates, price uplifts, termination windows, and the exact notice requirement text accompanied by page numbers.
Decision dates take precedence over formal expiry dates. The tool calculates radar timing by subtracting the required notice period and a 14-day cushion from the renewal date. Agreements already running inside the notice window receive an URGENT banner at the top of the generated markdown report. When integrations for Microsoft 365 or Google Calendar are present, it schedules reminders upon user confirmation.
Omission of a renewal clause triggers a manual review flag rather than an assumption that auto-renewal does not exist. Contract value figures must be explicit in the text, leaving no room for estimates.
What it helps with
- extract notice periods and renewal clauses from PDF and DOCX files
- compute decision cutoffs using notice requirements and a 14-day margin
- generate a 24-month chronological timeline in
renewal-calendar.md - push renewal reminder events to Microsoft 365 or Google Calendar
Example prompts for the agent
- Sweep ./contracts and build the renewal calendar
- What contracts are renewing this quarter?
- Calendar it based on the existing report
How to install cowork-contract-renewal-radar
1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill cowork-contract-renewal-radar -a claude-code2Manually: put the files in place
~/.claude/skills/cowork-contract-renewal-radar/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/cowork-contract-renewal-radar/
1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill cowork-contract-renewal-radar -a codex2Manually: put the files in place
.agents/skills/cowork-contract-renewal-radar/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill cowork-contract-renewal-radar -a cursor2Manually: put the files in place
.cursor/skills/cowork-contract-renewal-radar/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install OneWave-AI/claude-skills cowork-contract-renewal-radar2Manually: put the files in place
.github/skills/cowork-contract-renewal-radar/SKILL.md1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill cowork-contract-renewal-radar -a gemini-cli2Platform CLI
gemini skills install https://github.com/OneWave-AI/claude-skills --path cowork-contract-renewal-radarManually: put the files in place
.devin/skills/cowork-contract-renewal-radar/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill cowork-contract-renewal-radar -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about cowork-contract-renewal-radar
How to install cowork-contract-renewal-radar in Claude Code?
Run npx skills add OneWave-AI/claude-skills --skill cowork-contract-renewal-radar -a claude-code in your terminal.
What does cowork-contract-renewal-radar do?
It reviews a folder of contracts, calculates exact notice deadlines, outputs renewal-calendar.md, and prepares calendar reminders.
What is required to create calendar reminders?
Connected calendar write tools for Microsoft 365 or Google Calendar are needed, alongside explicit approval of the proposed event list.
Source text
SKILL.md · MIT
---
name: cowork-contract-renewal-radar
description: Sweep a contracts folder and extract every renewal date, auto-renew clause, notice window, and price-escalation term into a renewal calendar -- then create calendar reminders ahead of each notice deadline via Cowork's calendar write tools. The skill that stops auto-renewals from ambushing you.
tools: Read, Glob, Grep, Write, Bash
model: inherit
---
# Cowork Contract Renewal Radar
Read a folder of contracts the way outside counsel prepping a renewal calendar does: find every date-driven obligation, compute the real decision deadline (notice deadline, not renewal date), and put it somewhere it will actually be seen. Complements `contract-analyzer` (deep single-contract review) -- this skill is the portfolio sweep.
## Workflow
1. **Inventory.** Catalog every contract in the folder (PDF, .docx): counterparty, contract type (vendor, customer, lease, SaaS subscription, employment, NDA), and executed vs. draft status. Skip drafts but list them.
2. **Extract the clock terms** from each executed contract, quoting the clause verbatim with page/section:
- Term start/end dates and initial term length
- Auto-renewal: yes/no, renewal period, and the exact non-renewal notice requirement ("60 days written notice prior to expiration")
- Price escalations tied to renewal (CPI adjustments, fixed % uplifts, "then-current pricing")
- Termination-for-convenience windows and fees
- Any other dated obligation (insurance certificate renewals, option exercise windows)
3. **Compute decision deadlines.** For every auto-renewing contract, the date that matters is `renewal date minus notice period minus a 14-day decision buffer`. That is the radar date. Contracts already inside their notice window get flagged `URGENT` at the top of the report.
4. **Build the calendar.** Write `renewal-calendar.md`: chronological table of radar dates for the next 24 months with counterparty, annual value (when stated), what happens if nothing is done, and the verbatim notice clause. Separately list contracts with no end date or missing signature pages as data-quality issues.
5. **Set reminders.** If calendar write tools (Microsoft 365 / Google Calendar) are connected, create an event on each radar date -- title `Renewal decision: [counterparty]`, description containing the notice deadline, clause quote, and file path -- after showing the user the list of events to be created and getting approval.
## Rules
- The notice deadline is the deliverable, not the renewal date. A calendar that reminds you on the renewal date is a calendar of things it is too late to change.
- Quote clauses verbatim with location. Renewal terms are exactly where paraphrasing creates liability.
- Never mark a contract "no auto-renewal" from silence -- distinguish "clause states no renewal" from "no renewal clause found," and flag the latter for human review.
- Annual value comes from the contract only; no estimates.
- This is calendaring support, not legal advice. Frame judgment calls as "counsel should confirm...".
- On re-runs, diff against the previous calendar: new contracts, changed dates, and passed deadlines get called out first.
## Scheduled Mode
As a monthly Cowork scheduled task: re-sweep the folder for new/amended contracts, update the calendar, and deliver a digest leading with anything entering its decision window in the next 60 days.
## Quick Commands
- "Sweep [folder]" -- full workflow
- "What's renewing this quarter?" -- filtered radar view
- "Anything urgent?" -- contracts already inside their notice window
- "Calendar it" -- step 5 against the existing report
© OneWave-AI · MIT · OneWave-AI/claude-skills