Get a plain-language summary of a contract and a list of questions to take to a lawyer before you sign.
WHEN TO USE IT
When you have a contract to read and want to understand it before getting proper advice.
Formats change. If a field stops working, check it against Anthropic's documentation.
One file. The description is what Claude matches against, so it says plainly when to use the skill.
---
name: contract-summary
description: Explain a contract in plain language and list questions to ask a lawyer. Use when the user pastes a contract or agreement and asks what it means or what to watch for.
---
Explain a contract in plain language.
1. If the contract text, which party the user is, or what they care about most
is missing, ask once, in one message, then continue.
2. Start by saying this is a plain-language explanation, not legal advice.
3. Use these headings:
- What this is: the type of agreement and the parties, in two sentences.
- Key terms: a table of Topic, What it says, Clause number.
Cover payment, length and ending, duties, liability, confidentiality,
ownership of work, and disputes.
- Points to look at closely: terms that seem one-sided, unclear or unusual.
- Questions to ask a lawyer: a numbered list.
4. Quote the clause number for every point so they can check it.
Rules:
- Explain only what the text says; do not invent terms or laws.
- Write [unclear] where wording is ambiguous rather than guessing.
- Do not tell the user whether to sign; suggest a qualified lawyer for that.
Put the folder in your skills directory. Then ask in plain words, and Claude loads the skill when your request matches its description; or type the command yourself.
# for you, in every project
mkdir -p ~/.claude/skills/contract-summary
mv SKILL.md ~/.claude/skills/contract-summary/
# then, inside Claude Code, either ask naturally:
# explain this freelance contract in simple words before i sign
# or run it by name:
# /contract-summary
MORE SKILLS
The authority
Anthropic's documentation for Skills
This template is a starting point. Field names and options are defined by Claude Code, and its documentation wins whenever the two disagree.
https://code.claude.com/docs/en/skills