Contracts
Verified@ivangdavila
npx machina-cli add skill @ivangdavila/contracts --openclawRole
Manage all contracts in one place. Track dates, extract key terms, flag expiring items. Scale from personal subscriptions to enterprise contract libraries.
Storage
~/contracts/
├── index.md # Master list with quick stats
├── by-type/ # NDAs, leases, subscriptions, etc.
├── by-party/ # Organized by counterparty
├── {contract-name}/
│ ├── executed.pdf # Final fully-signed version
│ ├── meta.md # Key terms + signature status
│ ├── versions/ # Signature flow tracking
│ │ ├── 01-draft.pdf # Initial version sent
│ │ ├── 02-signed-them.pdf # Signed by counterparty
│ │ └── 03-signed-us.pdf # Countersigned (if sequential)
│ ├── history/ # Amendments after execution
│ └── notes.md # User notes, flags
Signature states: draft → pending-them → pending-us → executed
Quick Reference
| Context | Load |
|---|---|
| Role-specific workflows | roles.md |
| Contract analysis patterns | analysis.md |
| Alert and deadline tracking | alerts.md |
| Security and boundaries | security.md |
Core Capabilities
- Extract key terms — Dates, parties, amounts, notice periods, auto-renewal terms
- Track deadlines — Renewal dates, termination windows, milestone payments
- Alert proactively — 90/60/30 day warnings before renewals or expirations
- Quick clause lookup — "What's my cancellation notice period for X?"
- Cross-contract search — "Find all contracts expiring this quarter"
- Version tracking — Link amendments to parent contracts
- Cost aggregation — Total spend across subscriptions/vendors
On Upload
When user shares a new contract:
- Create folder in ~/contracts/{name}/
- Save as current.pdf
- Extract to meta.md: parties, effective date, term, value, renewal terms, notice period
- Add to index.md
- Set calendar alerts per
alerts.md
Boundaries
- NO legal advice — Cannot interpret clauses, assess risk, or recommend actions
- NO cloud storage — All contracts stay local unless user explicitly moves them
- NO sharing content — Never send contract text via messages
- "Is this clause good?" → "I can show you the clause, but consult a lawyer for interpretation"
Active Contracts
<!-- Count and categories from ~/contracts/index.md -->Expiring Soon
<!-- Next 90 days from meta.md dates -->Overview
Contracts helps organize, track, and analyze contracts in one place. It supports renewal alerts, term extraction, and multi-role workflows for individuals, landlords, freelancers, and legal teams, from personal subscriptions to enterprise libraries.
How This Skill Works
Store each contract under ~/contracts with an executed version and a meta.md capturing key terms (parties, dates, value, renewal terms). A master index.md tracks stats, while versions link amendments to the parent contract. Proactive 90/60/30 day alerts and cross-contract search enable quick insights, all while enforcing boundaries like no legal interpretation and local storage.
When to Use It
- Renewals and expiring dates across subscriptions, leases, or licenses
- Need quick, on-demand clause lookups (e.g., cancellation notice periods)
- Auditing terms across multiple contracts for consistency
- Identify contracts expiring in the next quarter and plan renewals
- Consolidate spend and manage version history across vendors
Quick Start
- Step 1: Upload a contract to ~/contracts/{name}/current.pdf; system extracts meta.md and updates index.md
- Step 2: Review/complete meta.md fields (parties, effective date, term, value, renewal terms, notice period)
- Step 3: Set alerts in alerts.md for 90/60/30 days and verify folder structure and status
Best Practices
- Keep meta.md fields consistent: parties, effective date, term, value, renewal terms, and notice period
- Organize files by-type and by-party; maintain a central index.md with quick stats
- Configure alerts in alerts.md for 90/60/30 day reminders before renewals or expirations
- Link amendments to their parent contracts via the versions/history structure
- Work locally and respect boundaries: no cloud storage or sharing contract text
Example Use Cases
- A freelancer tracks multiple subscriptions and NDAs for clients with renewal reminders
- A landlord manages leases, renewal windows, and counterparty details in one library
- A legal team builds an enterprise contract library with version history and analyses
- A small business centralizes vendor agreements and annual spend across contracts
- A startup monitors SaaS tool renewals across teams to optimize costs
