Contract Redliner logo

Contract Redliner

Organization
OneWave-AI
contract-redliner

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.

Overview

PublisherOneWave-AI
Repositoryclaude-skills
Skill namecontract-redliner
Stars
293
Forks
49
Bundled files
4
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 4 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by OneWave-AI on GitHub. Read the source before you install it.

Installation

Install the Contract Redliner AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/OneWave-AI/claude-skills.git /tmp/claude-skills
mkdir -p .claude/skills
cp -r /tmp/claude-skills/contract-redliner .claude/skills/contract-redliner
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Contract Redliner in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Contract Redliner on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Contract Redliner is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Contract Redliner AI skill do?

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.

Why use Contract Redliner on TypingMind?

Because you install it once and use it with any model. Contract Redliner is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Contract Redliner in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/OneWave-AI/claude-skills/tree/main/contract-redliner. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Contract Redliner?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Contract Redliner?

As many as you like. As long as a model supports skills, you can use Contract Redliner with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Contract Redliner AI skill free?

Yes. It is published on GitHub by OneWave-AI under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇