MCPInstall

plain-english-translation

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

Installs
65
Last 24h
—
Trending rank
—
Security
Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/zubair-trabzada/ai-legal-claude --skill plain-english-translation
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads plain-english-translation automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

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:

# 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.

FAQ

What does the plain-english-translation skill do?

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

How do I install plain-english-translation?

Run npx skills add https://github.com/zubair-trabzada/ai-legal-claude --skill plain-english-translation in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/plain-english-translation/ (personal) or .claude/skills/plain-english-translation/ (project).

Which AI agents can use plain-english-translation?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is plain-english-translation safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains plain-english-translation?

It is published by zubair-trabzada in zubair-trabzada/ai-legal-claude. It has 65 recorded installs.

More from zubair-trabzada/ai-legal-claude

View all →

terms-of-service-generator

zubair-trabzada/ai-legal-claude

Open the skill to read its SKILL.md instructions.

deep-risk-analysis

zubair-trabzada/ai-legal-claude

Clause-by-clause contract risk analysis with severity scoring, financial exposure estimates, and prioritized remediation guidance

contract-comparison

zubair-trabzada/ai-legal-claude

Side-by-side comparison of two contract versions or two different contracts with change tracking, favorability analysis, and risk assessment

missing-protections-finder

zubair-trabzada/ai-legal-claude

Identifies critical clauses and protections that should be in a contract but are missing, with urgency ratings and ready-to-insert language

counter-proposal-generator

zubair-trabzada/ai-legal-claude

Generates specific counter-proposals for every unfavorable clause, with replacement language, negotiation talking points, and a ready-to-send email template

custom-nda-generator

zubair-trabzada/ai-legal-claude

Generates a complete, customized Non-Disclosure Agreement with plain English annotations, tailored to the specific parties and situation

Popular docs & writing skills

View category →

grill-with-docs

mattpocock/skills

A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.

Docs & Writing1.2M installs

lark-markdown

open.feishu.cn

飞书 Markdown:查看、创建、上传、编辑和比较飞书中的原生 Markdown 文件。当用户要操作飞书 Markdown 文件,或比较其远端版本及本地草稿时使用。纯本地 Markdown 文件操作不触发本 skill。不负责将 Markdown 导入为飞书在线文档,也不负责文件搜索、权限、评论、移动、删除等云空间管理操作。

Docs & Writing778.7K installs

writing-beats

mattpocock/skills

Writing, exploit; assemble raw material into a journey of beats, grounding each term before a beat leans on it.

Docs & Writing490.7K installs

writing-shape

mattpocock/skills

Writing, exploit: shape raw material into an article, paragraph by paragraph.

Docs & Writing490.2K installs

writing-fragments

mattpocock/skills

Writing, explore: mine raw fragments, no structure yet.

Docs & Writing489.6K installs

writing-for-agents

mattpocock/skills

Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.

Docs & Writing479.3K installs