Reviews and negotiates commercial agreements — MSAs, SOWs, order forms, NDAs, vendor and data-processing agreements — identifying material risk, proposing positions, and recommending a path rather than listing issues. Use this to review a contract before signature, prepare a negotiation position, build fallback positions and approval thresholds, or assess exposure in terms already agreed.
npx skills add https://github.com/cbrock84/headcount --skill contract-review
> Not legal advice. This structures a commercial review and identifies what needs qualified counsel.
> Jurisdiction-specific questions, litigation, employment, financing, and M&A go to a licensed
> attorney.
Read for these first. Everything else is negotiable detail.
uncapped indemnity or a carve-out for a broad category can exceed the contract's entire value.
against what you actually do; indemnifying for a use you cannot control is the trap.
data, and what survives termination. Ambiguity here surfaces years later at the worst moment.
happens to data and obligations afterward. Missed notice windows are the most common
self-inflicted contract loss.
move without price moving.
can actually deliver it. Commitments that outrun capability are made in contracts and discovered
in incidents.
An issues list moves the work back to the business. For each material point, state: the risk in
plain terms, its realistic impact, the preferred position, an acceptable fallback, and what is a
genuine walk-away.
Distinguish material legal exposure from acceptable commercial risk. Treating every
deviation as a blocker trains people to route around review, which is the worst outcome available.
Beyond a handful of contracts, the leverage is in the system: standard templates, a clause library
with pre-approved fallbacks, thresholds below which the business signs without review, and a written
escalation path. Review every contract personally and you become the bottleneck the process was
meant to prevent.
Take cbrock84/contract-review from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
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.