contract-clocks
Skill0 starsChanged 51 days agoMITView on GitHub
Contract Clocks from My Business Brain. Extracts the key dates from any contract with a term longer than one month (end, auto-renewal, notice deadline, breaks, price reviews, payments, milestones), shows them for confirmation, and adds them to the user's preferred calendar (Google, Outlook, Apple or any open-source/CalDAV calendar via .ics) with reminders 7 days, 3 days and 24 hours before. Use when the user runs /my-business-brain:contract-clocks, shares a contract, lease, subscription or agreement, or asks when a contract renews, ends or needs notice.
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Never miss a renewal, notice deadline or expiry.
- Very specific: line 14
Use the calendar from the plugin settings (${user_config.calendar}) or _system/preferences.md, or ask once and save it.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/my-business-brain:contract-clocks
Never miss a renewal, notice deadline or expiry.
- Load the
my-business-brainskill from this plugin (via the Skill tool). If it cannot be loaded, read../my-business-brain/references/contract-clocks.mddirectly. - Read the whole contract. For a scanned PDF or a Word file, use a converter the research toolkit lists (
scripts/toolkit.py <brain> has pdftotext, or the installed pdf and docx skills) before reading by hand. Qualify it: term longer than one month, or auto-renewing (scripts/decide.py rules <brain> --type contract_qualifies --start <start> --end <end>settles it from the dates). Otherwise say so and stop (offer to store it anyway). - Extract the dates and terms with clause references, and compute derived dates with
scripts/contract_dates.py(from the core skill folder). Flag weekends and ask about public holidays in the contract's jurisdiction. - Show the date table with the notice deadline first and highlighted. Ask the user to confirm or correct. Never add unconfirmed dates.
- Use the calendar from the plugin settings (
${user_config.calendar}) or_system/preferences.md, or ask once and save it. Time zone:${user_config.timezone}; weekend:${user_config.weekend}(pass it tocontract_dates.py --weekend).- Google Calendar connector: create events with popup reminders at 10,080, 4,320 and 1,440 minutes, after a clear yes.
- Outlook connector: main event with a 24-hour reminder plus reminder events 7 and 3 days before, or the .ics file.
- Apple, Thunderbird, Nextcloud, Proton, any CalDAV, or no connector: build an
.icswithscripts/make_ics.py(three alarms per event) and send it to import.
- Record the contract entry and register in the brain (when one exists), with the calendar status and
sensitivity: confidential. Without a brain, still deliver the dates and the calendar file. - Remind the user that this tracks dates, not legal meaning; unclear terms go to a lawyer.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

