contract-summarizer
Skill0 starsChanged 3 months agoMITView on GitHub
Produce a plain-English summary of a contract or agreement. Use when someone pastes a contract, MSA, NDA, or terms document and wants the key terms, obligations, and risks explained clearly.
In this repository19 other files it gives its agents.
- ad-copySkill
- blog-writerSkill
- cold-outreachSkill
- content-repurposerSkill
- crm-note-cleanerSkill
- data-cleanerSkill
- expense-summarySkill
- faq-builderSkill
- follow-up-emailSkill
- invoice-builderSkill
- lead-qualifierSkill
- meeting-notesSkill
- newsletter-writerSkill
- proposal-writerSkill
- review-responderSkill
- social-post-packSkill
- sop-writerSkill
- support-replySkill
- weekly-reportSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 35
Never claim a clause is fine or enforceable.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Contract Summarizer
Turn dense legal text into what it actually means for the reader.
Inputs needed
- The contract text or the relevant sections.
- (Optional) Which side the reader is on (client or vendor) so risks are framed for them.
Steps
- State what the contract is and who the parties are in one line.
- Summarize the core terms: scope, payment, term length, renewal, termination.
- List each party's main obligations in plain language.
- Flag the clauses that carry risk: liability, indemnity, auto-renewal, exclusivity, penalties, IP ownership.
- Note anything that looks unusual or one-sided for the reader's side.
- List key dates and deadlines.
Output format
What this is: one line
Key terms: payment, term, renewal, termination
Your obligations: bullets
Their obligations: bullets
Watch out for: risky or unusual clauses
Key dates: deadlines and renewal triggersVoice & rules
- Plain language. Explain legal terms, don't repeat them.
- Flag risk clearly, but state this is a summary, not legal advice, and suggest a lawyer for anything high-stakes.
- Never claim a clause is fine or enforceable; point it out and let a professional judge.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

