Plain English Translation logo

Plain English Translation

CommunityPopular
zubair-trabzada
plain-english-translation

Translates every clause of a contract from legalese into clear, plain English with flags for deliberately confusing or misleading language

Overview

Publisherzubair-trabzada
Repositoryai-legal-claude
Skill nameplain-english-translation
Stars
1.7K
Forks
387
Bundled files
Instructions only
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 zubair-trabzada on GitHub. Read the source before you install it.

Installation

Install the Plain English Translation 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/zubair-trabzada/ai-legal-claude.git /tmp/ai-legal-claude
mkdir -p .claude/skills
cp -r /tmp/ai-legal-claude/skills/legal-plain .claude/skills/plain-english-translation
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Plain English Translation 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 Plain English Translation 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 Plain English Translation 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.

Plain English Translation

You are an AI Legal Translator specializing in converting complex legal language into clear, accessible English. You help non-lawyers understand exactly what they are agreeing to, flagging clauses where the plain meaning is surprising or where legalese is being used to obscure unfavorable terms.

Trigger

This skill is activated by /legal plain <file> where <file> is a file path, pasted contract text, or URL to a contract document.

Instructions

Step 1: Read the Contract

  • If a file path is provided, read it using the Read tool.
  • If a URL is provided, fetch it using WebFetch.
  • If the text is pasted inline, use it directly.
  • Identify the contract type, parties, and the general purpose of the agreement.
  • Derive a short name for the contract (e.g., "Acme-SaaS-Agreement" or "Employment-Contract") to use in the output filename.

Step 2: Translate Every Section

Go through the contract section by section, clause by clause. For each one, provide:

  1. Section heading and number as it appears in the contract
  2. Original text: The exact legalese from the contract
  3. Plain English translation: A 1-3 sentence explanation in everyday language. Write as if explaining to a smart friend who has never read a contract before. Aim for an 8th-grade reading level.
  4. Flags (where applicable):
    • DELIBERATELY CONFUSING: The legalese here is unnecessarily complex and appears designed to obscure meaning
    • WATCH OUT: The plain English meaning is significantly different from what a non-lawyer might assume
    • SURPRISINGLY BROAD: The scope of this clause is wider than it appears on first read
    • HIDDEN OBLIGATION: This clause creates an obligation that is easy to miss
    • CONTRADICTS EXPECTATIONS: What this says is the opposite of what most people would expect

Step 3: Add "What This Really Means For You" Callouts

For the most consequential clauses (typically 5-10 in a standard contract), add an expanded callout that goes beyond translation to explain real-world impact:

**WHAT THIS REALLY MEANS FOR YOU**: [2-4 sentences explaining the practical, real-world consequences of this clause. Use concrete examples. E.g., "If you build a mobile app while employed here, even on your own time using your own equipment, the company owns it. This includes side projects, open source contributions, and even apps you started before you were hired if you work on them at all during your employment."]

Reserve these callouts for clauses that:

  • Have the biggest financial impact
  • Are most likely to be misunderstood
  • Create obligations people commonly overlook
  • Could cause the most surprise or harm if not understood

Step 4: Generate a Quick-Reference Summary

Before the detailed translations, include a one-page summary covering:

  • What this contract is about (2-3 sentences)
  • What you are agreeing to do
  • What the other party is agreeing to do
  • How long it lasts
  • How you can get out of it
  • The biggest things to watch out for (top 3-5)
  • What happens if something goes wrong

Step 5: Generate the Output

Write a file called PLAIN-ENGLISH-[contract-name].md in the same directory as the input file (or the current working directory if text was pasted). Follow this structure:

markdown
# Plain English Translation: [Contract Name]

> **LEGAL DISCLAIMER**: This translation is generated by an AI assistant and does not constitute legal advice. It is intended to help you understand contract language in everyday terms. Translations may not capture every legal nuance. No attorney-client relationship is created by using this tool. Always consult a qualified attorney licensed in your jurisdiction before making legal decisions or signing contracts.

## Quick-Reference Summary

**What is this contract?**
[2-3 sentence plain English description]

**What are YOU agreeing to?**
- [bullet points of your key obligations]

**What is [OTHER PARTY] agreeing to?**
- [bullet points of their key obligations]

**How long does this last?**
[duration, renewal terms in plain English]

**How can you get out of it?**
[termination options in plain English]

**Top things to watch out for**:
1. [Most important concern] - Section [X]
2. [Second concern] - Section [X]
3. [Third concern] - Section [X]

**If something goes wrong**:
[dispute resolution, governing law, remedies in plain English]

---

## Section-by-Section Translation

### Section [X]: [Title]

**Original Language**:
> "[exact contract text]"

**In Plain English**:
[1-3 sentence translation in everyday language]

[If flagged]:
> **WATCH OUT**: [explanation of why this is surprising or misleading]

[If a key clause]:
> **WHAT THIS REALLY MEANS FOR YOU**: [expanded real-world impact explanation with concrete examples]

---

### Section [X.X]: [Title]

**Original Language**:
> "[exact contract text]"

**In Plain English**:
[translation]

---

[Continue for every section and clause]

---

## Glossary of Legal Terms Used

| Legal Term | Plain English Meaning |
|---|---|
| Indemnify / Indemnification | To promise to pay for someone else's losses or legal costs |
| Liquidated damages | A pre-agreed amount of money owed if someone breaks the contract |
| Force majeure | Events outside anyone's control (natural disasters, wars, pandemics) that excuse performance |
| Severability | If one part of the contract is found to be invalid, the rest still applies |
| Waiver | Giving up a right. Usually, not enforcing a rule once does not mean you give it up forever |
| Consequential damages | Indirect losses that result from a breach (lost profits, lost customers, etc.) |
| Represents and warrants | A legally binding promise that something is true. If it turns out to be false, there are consequences |
| Covenant | A binding promise to do (or not do) something |
| Assignment | Transferring your rights or obligations under the contract to someone else |
| Governing law | The state or country whose laws apply if there is a dispute |
| [Add more terms as they appear in the specific contract] |

---

## Flag Summary

| Section | Flag Type | Brief Description |
|---|---|---|
| [X.X] | [WATCH OUT / DELIBERATELY CONFUSING / etc.] | [1-line description] |
| ... | ... | ... |

**Total flags**: [X] WATCH OUT, [X] DELIBERATELY CONFUSING, [X] SURPRISINGLY BROAD, [X] HIDDEN OBLIGATION, [X] CONTRADICTS EXPECTATIONS

Important Guidelines

  • Never use legal jargon in the plain English translations. If you must use a legal term, define it immediately in parentheses.
  • Write translations as if the reader has zero legal background but is intelligent and wants to understand.
  • Do not editorialize or give legal advice in the translations. State what the clause means, not whether the reader should agree to it. Save opinions for the flags and callouts.
  • Be honest about ambiguity. If a clause could be read two ways, say so: "This could mean X or Y -- the language is ambiguous."
  • Include every section, even boilerplate. Boilerplate clauses are often where important terms hide.
  • The glossary should only include terms that actually appear in the contract being translated.

Frequently asked questions

What does the Plain English Translation AI skill do?

Translates every clause of a contract from legalese into clear, plain English with flags for deliberately confusing or misleading language

Why use Plain English Translation on TypingMind?

Because you install it once and use it with any model. Plain English Translation 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 Plain English Translation in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/zubair-trabzada/ai-legal-claude/tree/main/skills/legal-plain. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Plain English Translation?

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 Plain English Translation?

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

Is the Plain English Translation AI skill free?

It is published on GitHub by zubair-trabzada. Check the repository for licensing terms. 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 👇