cowork-contract-renewal-radar
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.
git clone --depth 1 https://github.com/OneWave-AI/claude-skills /tmp/cowork-contract-renewal-radar && cp -r /tmp/cowork-contract-renewal-radar/cowork-contract-renewal-radar ~/.claude/skills/cowork-contract-renewal-radarSKILL.md
# 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 reportAudit websites for accessibility issues and WCAG compliance. Use when checking accessibility, fixing a11y issues, or ensuring WCAG compliance.
Deploy a 2-layer parallel agent hierarchy for large, parallelizable work — big refactors, multi-file migrations, codebase-wide audits, bulk generation. A top-tier commander (Fable or Opus) orchestrates the swarms; the user picks a power level (Max Power / Heavy / Balanced / Economy) that sets the Opus/Sonnet/Haiku model mix per layer. Layer 1 is 3-50+ specialist agents, each with its own full context window; Layer 2 is 2+ sub-agents per member. Includes git safety, tiered sizing, a pre-deploy gate, phantom-completion checks, and multi-wave follow-up.
Deploys swarms of sub-agents for massive parallel data processing tasks. Unlike agent-army (which is for code changes), this is for DATA tasks -- processing 1000 documents, analyzing datasets, bulk content generation. Configurable swarm size, task distribution, result aggregation, progress tracking, and error recovery.
Designs and deploys custom agent teams for specific business workflows. Interactive discovery of business processes, then generates complete team configurations with specialized agent roles, tool access, communication protocols, and handoff rules.
Agent-to-Agent (A2A) communication protocol. Connect two or more Claude agents that pass messages, share context, delegate tasks, and collaborate. Implements structured handoffs, shared memory, and multi-agent conversations.
Assesses how ready a business is for AI adoption across six dimensions. Evaluates data maturity, tech stack, team skills, process documentation, budget, and culture. Generates a comprehensive ai-readiness-report.md with scores, gap analysis, and recommended starting points. Aligned with OneWave AI's audit methodology.
Generate animated videos and motion graphics from natural language descriptions. Creates a standalone Vite + React project with Framer Motion scenes that auto-play in the browser. Use when the user wants to create animations, motion graphics, video intros, animated presentations, or product demos.
Generate comprehensive API documentation including endpoint descriptions, request/response examples, authentication guides, error codes, and SDKs. Creates OpenAPI/Swagger specs, REST API docs, and developer-friendly reference materials. Use when users need to document APIs, create technical references, or write developer documentation.