mcpbeat Sign in

Cowork Contract Renewal Radar Skill for Claude

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.

911 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
235
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/OneWave-AI/claude-skills --skill cowork-contract-renewal-radar

The instruction itself

5 sections, as written by the author

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

  • 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.
  • 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)
  • 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.
  • 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.
  • 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

Other skills for the same job

different authors, same section of the catalogue
Doc Coauthoring
by anthropics
vendor ×10

Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.

4k tokens
File Organizer
by frostant
×10

Intelligently organizes your files and folders across your computer by understanding context, finding duplicates, suggesting better structures, and automating cleanup tasks. Reduces cognitive load and keeps your digital workspace tidy without manual effort.

3k tokens
Domain Name Brainstormer
by frostant
×8

Generates creative domain name ideas for your project and checks availability across multiple TLDs (.com, .io, .dev, .ai, etc.). Saves hours of brainstorming and manual checking.

1k tokens
Brainstorming
by ZhanlinCui
×4

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

626 tokens
Planning With Files
by ZhanlinCui
×3

Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls.

9k tokens scripts
Scientific Brainstorming
by christophacham
×3

Creative research ideation and exploration. Use for open-ended brainstorming sessions, exploring interdisciplinary connections, challenging assumptions, or identifying research gaps. Best for early-stage research planning when you do not have specific observations yet. For formulating testable hypotheses from data use hypothesis-generation.

5k tokens
GitHub Project Management
by ComeOnOliver
×3

Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning

14k tokens
Grill Me
by ComeOnOliver
×3

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".

3k tokens

How to use it

Copy the folder

Take onewave-ai/cowork-contract-renewal-radar from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.