contract-redliner · onewave-ai — Claude Code skill: review and install
contract-redliner reviews contracts clause by clause, rates risks, and drafts replacement language. Use it to prepare proposed edits and negotiation points.
MIT 256 installs ★ 440 updated 2026-10-20
npx skills add OneWave-AI/claude-skills --skill contract-redliner -a claude-codeWhat contract-redliner does
Give it pasted contract text, a .txt, .md, .pdf, or .docx file, or a URL. The skill identifies the contract type and parties, then checks each section against seven risk categories. It also labels acceptable clauses and adds a brief note.
The main deliverable is contract-review.md, with clause-level findings, risk ratings, and proposed edits using [-deletion-] and [+insertion+]. For issues rated MEDIUM or higher, it adds negotiation talking points. Each proposed change includes a complete replacement clause and a clean version.
The report opens with a disclaimer that the analysis is informational, not legal advice. By default, the review takes the signing party’s perspective. Enforceability can depend on jurisdiction, so the skill directs users to consult a qualified attorney before signing or changing an agreement.
What it helps with
- spot ambiguous or unfavorable contract terms
- draft complete replacement clauses for issues
- rate contract sections by risk level
- prepare talking points for negotiating edits
Example prompts for the agent
- Review this agreement and write
contract-review.mdwith risk ratings and proposed edits. - Analyze the contract from the signing party’s perspective and draft full replacements for problematic clauses.
- Review
agreement.pdfsection by section and prepare negotiation talking points.
How to install contract-redliner
1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill contract-redliner -a claude-code2Manually: put the files in place
~/.claude/skills/contract-redliner/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/contract-redliner/
1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill contract-redliner -a codex2Manually: put the files in place
.agents/skills/contract-redliner/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill contract-redliner -a cursor2Manually: put the files in place
.cursor/skills/contract-redliner/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install OneWave-AI/claude-skills contract-redliner2Manually: put the files in place
.github/skills/contract-redliner/SKILL.md1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill contract-redliner -a gemini-cli2Platform CLI
gemini skills install https://github.com/OneWave-AI/claude-skills --path contract-redlinerManually: put the files in place
.devin/skills/contract-redliner/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill contract-redliner -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about contract-redliner
How do I install contract-redliner in Claude Code?
Run npx skills add OneWave-AI/claude-skills --skill contract-redliner -a claude-code. The skill file is at ~/.claude/skills/contract-redliner/SKILL.md.
What does contract-redliner do?
It reviews contract sections, assigns risk ratings, and drafts replacement language for problematic terms. The report is saved as contract-review.md.
What contract formats can it review?
You can provide pasted text, a .txt, .md, .pdf, or .docx file path, or a URL.
Source text
SKILL.md · MIT
--- name: contract-redliner description: Reads a contract and generates redline suggestions with replacement language. Identifies unfavorable terms, missing protections, ambiguous language, liability exposure, IP risks, termination traps, and auto-renewal gotchas. Produces a contract-review.md with clause-by-clause analysis, risk ratings, tracked changes format, and negotiation talking points. Use when the user wants redline markup, contract markup, or suggested contract edits. tools: Read, Write, Glob, Grep, Bash model: inherit --- # Contract Redliner Read a contract and produce a `contract-review.md` with clause-by-clause analysis, risk ratings, replacement language in tracked-changes format, and negotiation talking points. Unlike contract-analyzer (which only flags issues), produce specific, drop-in replacement language for every problematic clause, ready for negotiation. ## Contents - `references/risk-categories.md` -- the seven risk categories, what to look for in each, and the risk-rating system. - `references/redline-format.md` -- per-issue redline entry format and tracked-changes conventions. - `references/output-template.md` -- the full `contract-review.md` structure to generate. - `references/contract-types.md` -- per-contract-type focus areas and worked examples. ## Workflow 1. **Ingest the contract.** Accept pasted text, a file path (`.txt`, `.md`, `.pdf`, `.docx`), or a URL. Load files with the Read tool; for PDFs use the pdf skill or Read PDF support. Parse the full text and identify all numbered sections, clauses, and subclauses. 2. **Identify type and parties.** Determine contract type, Party A (drafter/company), Party B (signer), governing law, effective date, and term. Apply the matching focus area from `references/contract-types.md`. 3. **Analyze every section.** Evaluate each section against the seven risk categories in `references/risk-categories.md`. Assign each section a rating (CRITICAL / HIGH / MEDIUM / LOW / ACCEPTABLE). Mark fair sections as ACCEPTABLE with a brief note -- do not skip them. 4. **Generate redlines.** For every issue, produce a redline entry per the format and tracked-changes conventions in `references/redline-format.md`. Provide complete, standalone replacement language plus a clean accepted version. 5. **Write `contract-review.md`.** Generate the file in the working directory (or the directory the user specifies) following `references/output-template.md` exactly and in order. ## Mandatory Rules - Open every output with this disclaimer verbatim: > LEGAL DISCLAIMER: This analysis is informational only and does not constitute legal advice. Contract interpretation is jurisdiction-specific and fact-dependent. Always consult a qualified attorney before signing or modifying any legal agreement. This tool is designed to surface potential issues and suggest alternative language for discussion purposes only. - Never provide incomplete replacement language; every redline includes a full, usable clause. - Never present analysis without quoting the specific contract language being discussed. - Never assume jurisdiction-specific enforceability; note when a provision's enforceability varies by jurisdiction. - Always produce `contract-review.md` as the primary deliverable. - Always use tracked-changes format (`[-deletion-]` / `[+insertion+]`) for every suggested change. - Always include negotiation talking points for every issue rated MEDIUM or above. - Always analyze from the signing party's perspective unless told otherwise. ## Quality Standards - **Be exhaustive.** Review every section, not just the obviously problematic ones. - **Be specific.** Quote exact language, reference exact section numbers, provide complete replacement text. - **Be practical.** Frame suggestions a reasonable counterparty would accept; extreme positions undermine credibility. - **Be balanced.** Note favorable provisions too -- this builds credibility for the items that need changing. - **Quantify where possible.** Estimate liability exposure and calculate penalties when the contract permits. - **Reference market standards.** When calling something non-standard, state what the market standard actually is.
© OneWave-AI · MIT · OneWave-AI/claude-skills
Similar skills
All skills for Writing and docs →contract-redliner by other authors comes first.