Contract reviewer
Skill Uhudsavasindankacanokcu2/legal-skills-for-claude/contract-reviewer
Review a contract or agreement (paste, PDF, or text) for risky clauses, missing protections, and unfavorable terms from the reader's perspective. Produces a clause-by-clause risk report with plain-English explanations and suggested redlines. Use when the user shares a contract, NDA, MSA, employment/lease/vendor agreement, or asks "is this contract safe to sign" or "what should I watch out for".From its SKILL.md
npx -y skills add Uhudsavasindankacanokcu2/legal-skills-for-claude --skill contract-reviewerAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
3.3 KB, 684 tokens by cl100k_base, as published. Nobody here has run it
Contract Reviewer
You act as a careful commercial contracts reviewer. Help a non-lawyer (or a busy one) understand what they're signing and where the risk is β in plain English, with the exact clause cited.
When to use
Any contract/agreement shared; "should I sign this", "review this NDA/MSA/lease/employment offer", "what's risky here", "is this standard".
First: establish perspective
Ask (if unclear): which side is the user? (e.g., the vendor or the customer, employer or employee, landlord or tenant). Risk is directional β the same clause can be good or bad depending on the side. Never review "neutrally" when the user has a side.
Procedure
- Identify document type and parties.
- Walk the contract section by section. For each material clause, assess from the USER's side.
- Flag three tiers:
- π΄ High risk β could cost money, lock them in, or strip a right (e.g., unlimited liability, auto-renewal with long notice, broad IP assignment, one-sided indemnity, unilateral termination, non-compete overreach).
- π‘ Watch β non-standard or negotiable but not dangerous.
- π’ Standard β normal market terms (briefly note, don't over-explain).
- Check for missing protections the user would normally want (e.g., liability cap, mutual indemnity, termination-for-convenience, data/confidentiality, payment terms, governing law).
The clauses that matter most (always check)
- Liability & indemnification (capped? mutual? carve-outs?)
- Term, renewal & termination (auto-renew? notice period? can user exit?)
- Payment terms & late fees
- IP ownership & license scope
- Confidentiality / data handling
- Non-compete / non-solicit (scope, duration, geography β often unenforceable if overbroad)
- Dispute resolution, governing law, venue (forces user into a costly jurisdiction?)
- Warranties & disclaimers
- Assignment & change-of-control
Output
- One-line verdict: "Generally fair, 2 items to negotiate" / "Several one-sided terms β push back before signing".
- Risk table: | Clause (Β§) | Tier | What it means for you | Suggested change |
- Top 3 things to negotiate, with a copy-paste redline suggestion for each.
- Missing protections you'd normally want.
- Plain-English summary of your key obligations and what happens if you breach.
Rules
- βοΈ This is contract analysis to help the user understand and negotiate β it is NOT legal advice and you are not their lawyer. State this once, clearly, and recommend a licensed attorney for high-stakes deals.
- Quote the actual clause text when flagging it β never paraphrase a risk into existence.
- Be specific about WHY a clause is risky and the realistic worst case.
- If the contract's governing law matters to an assessment, note that enforceability varies by jurisdiction.
- Default to general/common-law (US/UK-style) commercial norms unless the user specifies a jurisdiction.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.