Contract Review

What it does

When your agent uses it

• Says review this contract
• Look at this agreement
• Is this contract fair
• Red flags in this

Example prompts

• “review this contract,”
• “look at this agreement,”
• “is this contract fair,”
• “/contract-review”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

1. 1Be specific. Reference clause numbers and exact language. "Section 7.2 caps liability at fees paid, but limits it to the prior 3 months…
2. 2Translate to plain English. Don't repeat legalese back at the user — that's why they came to you.
3. 3Prioritize ruthlessly. A 30-item list is useless. Surface the top 3-5 things to fix, and triage the rest.
4. 4Acknowledge your limits. You are a sharp first read, not a substitute for a lawyer. For anything serious, say so explicitly.
5. 5Don't moralize. If the contract is one-sided, name the imbalance neutrally — don't editorialize about the counterparty.
6. 6Compare to standard practice where possible. "A 5-year non-compete is unusual; 1-2 years is more typical for this role" gives the user…

What it can do on your machine

Read from SKILL.md and the folder at commit fdbf39b. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  No URLs in SKILL.md.

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names no API keys, tokens, secrets or passwords.

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Contract Review loads about 1.6k tokens when it runs. Until then it costs about 134 tokens; SKILL.md has 623 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~134

When it runs · the whole SKILL.md, loaded when a task matches

~1.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from TheCraigHewitt/skills at commit fdbf39b, republished under its MIT licence (© TheCraigHewitt). 623 words, ~1,624 tokens.

name

contract-review

description

Review a contract, agreement, terms-of-service, MSA, NDA, employment agreement, vendor SOW, or any legal document. Flag risks, missing terms, unusual clauses, and points worth negotiating. Use this whenever the user says 'review this contract,' 'look at this agreement,' 'is this contract fair,' 'red flags in this,' 'should I sign,' 'help me negotiate,' 'check this NDA,' or attaches/pastes any contract-like document. Output is a structured markdown review the user can read in 5 minutes before signing or negotiating.

# Contract review — [contract title]

**Date:** YYYY-MM-DD
**Contract type:** [identified type]
**Your role:** [the side you're representing]
**Bottom line:** [one sentence — should you sign, negotiate, or walk?]

## TL;DR
3-5 bullets covering: what this contract does, the headline risks, the one thing to fix before signing.

## Key terms (the deal in plain English)
- **Term:** [duration + termination]
- **Money:** [amounts, schedule, fees]
- **Scope:** [what's being agreed to]
- **IP / data:** [who owns what]
- **Liability:** [caps, indemnity]

## 🚨 Red flags
Clauses that meaningfully expose the user. For each:
- The clause (with location reference)
- Why it's a problem
- Suggested fix

## ⚠️ Yellow flags
Things that are unusual but might be acceptable depending on context. Same format.

## ❌ Missing
What's not in the contract that should be. Common omissions: liability cap, termination for convenience, IP carve-outs, dispute resolution.

## 💬 What to negotiate
Prioritized — the top 3-5 things to push back on, with suggested language where possible.

## ✅ What looks fine
Brief — what's standard and unremarkable. (Saves the user from worrying about everything.)

## Get a lawyer's eyes on
Anything outside your competence: securities terms, jurisdiction-specific labor law, IP assignment edge cases, complex tax provisions. Be honest about your limits.

© TheCraigHewitt, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in cowork/contract-review of TheCraigHewitt/skills.

• SKILL.md
• evals/evals.json

Open the folder on GitHubat commit fdbf39b