Contract Clause Checklist logo

Contract Clause Checklist

Organization
open-legal-products
contract-clause-checklist

Walk a single contract against 41 clause categories from the CUAD taxonomy: first assess which categories this deal needs, then mark each applicable one present, absent, or risky, quoting the clause when present, so that a safeguard the deal needs does not slip through by omission. Extractive: findings come from the contract text, not paraphrase. Use before signing, in negotiation, or in due diligence of one agreement, when the question is what is missing from this contract and which clauses bite. Jurisdiction-neutral framing with common-law roots; the assessment and the recommendation stay with the lawyer.

Overview

Publisheropen-legal-products
Repositorymike-workflows
Skill namecontract-clause-checklist
Stars
91
Forks
43
Bundled files
Instructions only
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.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by open-legal-products on GitHub. Read the source before you install it.

Installation

Install the Contract Clause Checklist 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.
    https://github.com/open-legal-products/mike-workflows/tree/main/assistant-workflows/eu-gdpr-pack/contract-clause-checklist
  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/open-legal-products/mike-workflows.git /tmp/mike-workflows
mkdir -p .claude/skills
cp -r /tmp/mike-workflows/assistant-workflows/eu-gdpr-pack/contract-clause-checklist .claude/skills/contract-clause-checklist
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Contract Clause Checklist 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 Clause Checklist 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 Clause Checklist 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 Clause Checklist

The most expensive clauses are the ones that are not in the contract. Reviewing a contract is not only reading what is written - it is checking that no safeguard the deal needs is absent. This workflow walks the contract against a fixed list of 41 clause categories and, for each, says: present, absent, or present-but-risky, quoting the clause when present.

It is extractive - what it shows comes from the contract, not from paraphrase. It flags presence and risk; the assessment and the call stay with the lawyer.

One caution built into the method: CUAD is an extraction taxonomy, not a list of safeguards every agreement must contain. Several categories are deal-specific, and some are mutually exclusive pairs - uncapped liability versus a cap on liability, unlimited versus limited licence grants. Treating every absence as a red flag would bury the real gaps in false positives.

The 41 categories (CUAD taxonomy)

Each category is assessed in two steps. First, applicability: does this deal need the clause at all, given the contract type, the parties, and the subject matter? Then, for applicable categories only: present / absent / risky, plus a quote when present. Mutually exclusive pairs count as one decision - record which side the contract takes, not the "absence" of the other side.

Contract metadata

  • Document name, Parties (verify authority to sign), Governing law.

Group 1 - term and dates

  • Agreement date, Effective date, Expiration date, Renewal term (auto-renew?), Notice period to terminate renewal.

Group 2 - competition restrictions

  • Non-compete, Exclusivity, No-solicit of customers, Competitive restriction exception (carve-outs).

Group 3 - control and assignment

  • Change of control (consent or termination on M&A?), Anti-assignment.

Group 4 - licences

  • License grant, Non-transferable license, Affiliate license (licensor), Affiliate license (licensee), Unlimited license, Irrevocable or perpetual license.

Group 5 - post-term and audit

  • Post-termination services, Audit rights.

Group 6 - liability

  • Uncapped liability, Cap on liability.

Ungrouped

  • Most favored nation, No-solicit of employees, Non-disparagement, Termination for convenience, ROFR/ROFO/ROFN, Revenue/profit sharing, Price restrictions, Minimum commitment, Volume restriction, IP ownership assignment, Joint IP ownership, Source code escrow, Covenant not to sue, Liquidated damages, Warranty duration, Insurance, Third-party beneficiary.

Output format

Start with the red flags, then the full table:

  • RED FLAGS: each category that is applicable and absent, with why this deal needs it, and each risky category with how it is one-sided. A category marked not applicable never becomes a red flag.
  • 41-CATEGORY TABLE with columns: Category, Applicable (yes/no + why), Status, Note, Quote (if present).

Limits

  • This is a presence-and-risk checklist, not an interpretation of clause wording. Whether a clause is effective, and the recommendation, are the lawyer's.
  • The taxonomy is common-law-oriented at source; for a specific jurisdiction, add local-law anchors.
  • Descriptive references without a clause ("the parties intend to cooperate") have nothing to match - mark them as "no clause, manual check".

Attribution

The 41-category clause taxonomy is based on CUAD (Contract Understanding Atticus Dataset), The Atticus Project, licensed CC BY 4.0 (https://www.atticusprojectai.org/cuad). Category descriptions and the risk framing are the author's own.

Frequently asked questions

What does the Contract Clause Checklist AI skill do?

Walk a single contract against 41 clause categories from the CUAD taxonomy: first assess which categories this deal needs, then mark each applicable one present, absent, or risky, quoting the clause when present, so that a safeguard the deal needs does not slip through by omission. Extractive: findings come from the contract text, not paraphrase. Use before signing, in negotiation, or in due diligence of one agreement, when the question is what is missing from this contract and which clauses bite. Jurisdiction-neutral framing with common-law roots; the assessment and the recommendation stay...

Why use Contract Clause Checklist on TypingMind?

Because you install it once and use it with any model. Contract Clause Checklist 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 Clause Checklist in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/open-legal-products/mike-workflows/tree/main/assistant-workflows/eu-gdpr-pack/contract-clause-checklist. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Contract Clause Checklist?

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 Clause Checklist?

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

Is the Contract Clause Checklist AI skill free?

Yes. It is published on GitHub by open-legal-products 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 👇