Contracts

Skill mehtab78/skills/skills/contracts

Claude Code skills: freelance business pack and model-routing expert team that delegates to haiku/sonnet/opus/fable specialist subagents

Install

npx -y skills add mehtab78/skills --skill contracts

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use to organize, track, and analyze contracts, client service agreements, NDAs, subscriptions, leases, with key-term extraction, renewal/termination alerts (90/60/30-day), clause lookups, and version/signature tracking. Trigger when the user shares or asks about a contract, needs to know a notice or cancellation period, wants to find contracts expiring soon, or is tracking signature status. Surfaces and organizes contract facts; does not give legal advice; it points the user to a lawyer for interpretation.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

3.1 KB, as published. Nobody here has run it

Contract tracking

Keep every contract in one place, pull out the terms that matter, and warn the user before deadlines bite. Scales from a handful of personal subscriptions to a freelancer's client agreements to a larger contract library.

Hard boundary: this skill handles facts and dates, not legal judgment. It never interprets clauses, rates a contract as safe/risky, or advises whether to sign; it points the user to a lawyer for that. See references/security.md.

Storage

~/contracts/
├── index.md                    # master list + quick stats
├── by-type/                    # NDAs, leases, subscriptions…
├── by-party/                   # grouped by counterparty
└── {contract-name}/
    ├── executed.pdf            # final signed version
    ├── meta.md                 # extracted terms + signature status
    ├── versions/               # draft → signed-them → signed-us
    ├── history/                # post-execution amendments
    └── notes.md                # user notes and flags

Signature states move draft → pending-them → pending-us → executed.

If the clients skill is also installed, this is still the canonical home for the executed file and its metadata — store it at ~/contracts/{name}/, and just link to it (don't copy it) from that client's documents/ folder.

What it does

Extract key terms: parties, dates, amounts, notice periods, auto-renewal.
Track deadlines: renewals, termination windows, milestone payments.
Alert ahead of time: 90/60/30-day warnings (see references/alerts.md).
Answer clause lookups: "what's my cancellation notice on X?"
Search across contracts: "everything expiring this quarter."
Track versions: link amendments to the parent contract.
Aggregate cost: total spend across subscriptions and vendors.

When a contract arrives

Create ~/contracts/{name}/ and save the file.
Extract into meta.md: parties, effective date, term, value, renewal terms, notice period (pattern in references/analysis.md).
Add it to index.md.
Set the deadline alerts per references/alerts.md.

References

Need	File
Role-specific workflows (consumer, landlord, freelancer, legal)	`references/roles.md`
Term extraction + clause lookups + red flags	`references/analysis.md`
Alert schedule and dashboards	`references/alerts.md`
Security, privacy, and legal boundaries	`references/security.md`