Immediate result: A side-by-side table of each changed clause, what changed, why it matters and a response.
Problem it solvesComparing the other side's redline with your standard terms clause by clause is slow and error-prone.
Our indemnity clause vs the client's redlined version
Theirs adds 'and any indirect or consequential losses' → widens your exposure significantly.
Response: reject; counter with direct losses only, capped at fees paid.
Formatting-only changes: 3 (listed).
Comparing the other side's redline with your standard terms clause by clause is slow and easy to get wrong. This skill aligns the clauses of both versions, describes each substantive change in plain words, assesses the impact on your position and suggests whether to accept, reject or counter with specific wording. Formatting-only changes are listed separately at the end so they don't distract. Lawyers and contract managers use it to get through a negotiation round faster. To use it, paste the skill into your assistant and send your standard clause (or contract) and their version; the reply is laid out as “Comparison table: clause, ours, theirs, what changed, impact, response”.
# Skill: Clause comparison
You are running the "Clause comparison" skill for me. I work as: Contract manager / lawyer. What I need from you: a side-by-side table of each changed clause, what changed, why it matters and a response.
## When I send you my standard clause (or contract) and their version
1. Align clauses between the two versions.
2. Describe each substantive change in plain words.
3. Assess the impact on your position.
4. Suggest accept, reject or counter wording.
## Reply in this format
- Comparison table: clause, ours, theirs, what changed, impact, response
## Rules
- Ignore formatting-only changes but list them at the end.
- Not legal advice: end every reply with a reminder that a qualified lawyer should review before anything is signed, sent or filed.
- Use only the facts I give you; mark anything you had to assume with [ASSUMPTION].
- If something essential is missing, ask me one short question, then continue.
- No preamble or filler: start with the result.
Confirm you're ready in one line, then wait for me to send my standard clause (or contract) and their version.Then sendYour standard clause (or contract) and their version. For example: Our indemnity clause vs the client's redlined version
Upload it to Claude, add it to ChatGPT's Codex app, clone it into Claude Code, or download the SKILL.md for any agent. Full guide with screenshots →
Download the ZIP and upload it in Claude. Claude then uses the skill on its own whenever a request matches.
Download ZIP
OpenAI's Codex app reads the same SKILL.md format. Copy the skill into your Codex skills folder:
$ git -c http.version=HTTP/1.1 clone https://scienceofapps.com/skills/ai-skills.git
$ cp -r ai-skills/clause-comparison ~/.codex/skills/
Clone the library and copy this skill into your Claude Code skills folder.
$ git -c http.version=HTTP/1.1 clone https://scienceofapps.com/skills/ai-skills.git
$ cp -r ai-skills/clause-comparison ~/.claude/skills/~/.claude/skills/ for all projects, or .claude/skills/ inside one project.Download the skill file and put it in a folder named after the skill.
Download SKILL.md~/.claude/skills/clause-comparison/SKILL.md.Repositoryscienceofapps.com/skills/ai-skills.git · all 200 skills, one folder each, plain git over HTTPS
Comparing the other side's redline with your standard terms clause by clause is slow and error-prone. The skill fixes that: a side-by-side table of each changed clause, what changed, why it matters and a response.
Copy the skill and paste it as the first message of a new chat, then send your input. To keep it, paste it into a ChatGPT Project or custom GPT, a Claude Project or a Gemini Gem, or upload the SKILL.md file as a Claude Skill.
Send your standard clause (or contract) and their version. If something essential is missing, the skill asks you one short question and then continues.
Yes. It's free to copy, use and adapt, with no sign-up, and works in the free versions of ChatGPT, Claude, Gemini and Copilot.
ProblemTeams sign NDAs without reading them, including one-way terms and very long durations.
One-way NDA from a large company, 7-year term, includes a 2-year non-solicit
One-way: only protects them — ask for mutual if you share anything.
Non-solicit (clause 9) doesn't belong in an NDA — ask to remove.
Verdict: negotiate.
Immediate resultA quick check of an NDA against a standard checklist, with issues and suggested edits.
ProblemPrivacy notices are copied from other sites and don't describe what the product actually does with data.
Fitness app: email, phone, workouts, heart rate from wearables; analytics via PostHog; servers in Mumbai
What we collect: your email and phone number, the workouts you log, and heart-rate data if you connect a wearable.
Gap: how long do you keep heart-rate data after someone deletes their account?
Rights (India): access, correction, erasure, grievance redressal — name a contact.
Immediate resultA plain-English privacy notice draft based on your real data practices, with gaps flagged.
ProblemIndian companies must comply with the DPDP Act and Rules by May 2027 and don't know where they stand.
Edtech app for students aged 10–18, consent via a checkbox at sign-up, no breach process
Children's data: missing — verifiable parental consent is required for under-18s.
Breach notification: missing — you need a process to inform the Board and affected users.
Priority 1: parental consent flow.
Immediate resultA gap assessment against the main DPDP Act and Rules duties, with priorities and owners.
All 10 legal & compliance skillsAll 200 skillsRead it in the articleProve it: Contract Review and Document Management Basics Certification (free test)
60 research-backed principles in 6 categories — what each one means, why it works on the human brain and how to use it on your own screens. Written by Sushant Singh, founder of Science of Apps, who has scaled consumer apps to lacs of users and spent 10+ years leading product across startups and digital businesses in the US, EU & India.
110 real paywalls from top apps, taken apart, rated out of 5 and decoded with the Laws of UX — plus the frameworks, copy and checklists to ship your own. By Sushant Singh, founder of Science of Apps.