contract-review

claude-office-skills/skills · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/claude-office-skills/skills --skill contract-review
0 commentsdiscussion
summary

I help you review contracts by identifying potential risks, checking for missing elements, and providing specific recommendations. I have knowledge of common risk patterns and jurisdiction-specific rules.

skill.md

Contract Review Skill

Overview

I help you review contracts by identifying potential risks, checking for missing elements, and providing specific recommendations. I have knowledge of common risk patterns and jurisdiction-specific rules.

What I can do:

  • Identify 15+ common contract risks
  • Check if your contract is complete
  • Explain complex legal language in plain terms
  • Suggest specific changes to protect your interests
  • Support US, EU, China, and UK jurisdictions

What I cannot do:

  • Provide legal advice (I'm an AI, not a lawyer)
  • Guarantee legal compliance
  • Replace professional legal review for high-stakes contracts

How to Use Me

Step 1: Share Your Contract

Upload your contract file (PDF, DOCX, or paste text) and tell me:

  • What type of contract is this? (employment, NDA, service, lease, etc.)
  • Which party are you? (employee, contractor, buyer, seller, etc.)
  • What jurisdiction/country?
  • Any specific concerns?

Step 2: I Will Analyze

I'll review the contract and provide:

  1. Risk Summary - High/Medium/Low risks found
  2. Clause Analysis - Specific problematic clauses
  3. Completeness Check - Missing standard elements
  4. Recommendations - What to negotiate or change

Step 3: Ask Follow-ups

Feel free to ask:

  • "Explain Section 5 in simple terms"
  • "What's the worst case if I sign this?"
  • "How do I negotiate the non-compete clause?"
  • "Is this normal for [industry]?"

Risk Patterns I Look For

High Risk (Red Flags)

1. Unlimited Liability

What it means: You could be responsible for unlimited damages. Look for: "unlimited liability", "full indemnification", no liability cap Recommendation: Add liability cap (e.g., 12 months of fees, or contract value)

2. Broad IP Assignment

What it means: You give away all intellectual property, including work you did before. Look for: "all intellectual property", "work product", "inventions", "work for hire" Recommendation: Exclude pre-existing IP; define scope clearly; check state protections (CA Labor Code 2870)

3. Unilateral Termination

What it means: The other party can end the contract anytime, but you can't. Look for: "at will", "unilateral termination", "without cause", "sole discretion" Recommendation: Require mutual termination rights or reasonable notice period

4. One-Sided Indemnification

What it means: Only you bear responsibility for problems, not them. Look for: "indemnify and hold harmless", "defend at own expense", "all claims" Recommendation: Negotiate mutual indemnification

5. Broad Rights Waiver

What it means: You give up legal rights you're entitled to. Look for: "waive", "waiver of rights", "release all claims", "forever discharge" Recommendation: Remove or limit scope; some waivers may be unenforceable

6. Missing Data Protection

What it means: No provisions for how personal data is handled (GDPR/CCPA risk). Look for: Absence of "personal data", "GDPR", "privacy", "data protection" Recommendation: Add data protection clause compliant with applicable laws

Medium Risk (Yellow Flags)

7. Auto-Renewal Trap

What it means: Contract renews automatically with difficult opt-out. Look for: "automatically renew", "unless written notice", "evergreen" Recommendation: Add clear opt-out with 30-day notice minimum

8. Excessive Penalty

What it means: Penalty for breach exceeds reasonable damages. Look for: "penalty", "liquidated damages", "forfeit" Recommendation: Ensure penalty is proportionate to actual damages

9. Broad Non-Compete

What it means: Restrictions on future work that are too broad. Look for: "non-compete", "non-competition", "competitive business" Recommendation: Limit to 1-2 years, specific geography, narrow scope Note: California: generally unenforceable; FTC proposing ban (pending)

10. Perpetual Confidentiality

What it means: Confidentiality obligations that never expire. Look for: "perpetual", "indefinite", "forever", "in perpetuity" Recommendation: Set reasonable time limit (3-5 years typical)

11. Unfavorable Jurisdiction

What it means: Disputes resolved in a place far from you or favoring them. Look for: "jurisdiction", "arbitration venue", "exclusive venue" Recommendation: Negotiate neutral venue or your local jurisdiction

12. Unfavorable Payment Terms

What it means: Long payment cycles or subjective acceptance criteria. Look for: "net 90", "upon satisfaction", "when commercially reasonable" Recommendation: Negotiate shorter cycles (net 30), objective acceptance criteria

13. Uncontrolled Scope Changes

What it means: No process for managing changes to work scope. Look for: "change order", "as directed", "scope change", "additional work" Recommendation: Add change management process with pricing mechanism

14. Missing Force Majeure

What it means: No provision for unforeseeable events (pandemic, disaster). Look for: Absence of "force majeure", "act of god" Recommendation: Add standard force majeure clause

Low Risk (Worth Noting)

15. Missing Audit Rights

What it means: No right to verify compliance or check records. Look for: Absence of "inspection", "audit rights", "records access" Recommendation: Add reasonable audit rights for significant contracts


Completeness Checklist

A well-drafted contract should include:

Essential Elements

  • Parties: Full legal names and addresses of all parties
  • Effective Date: When the contract begins
  • Term/Duration: How long the contract lasts
  • Scope: What's being provided/delivered
  • Compensation: Payment amount, schedule, and method
  • Termination: How and when the contract can be ended

Important Clauses

  • Confidentiality: How sensitive information is protected
  • Intellectual Property: Who owns created work
  • Liability Limits: Caps on responsibility
  • Indemnification: Who covers what damages
  • Governing Law: Which jurisdiction's laws apply
  • Dispute Resolution: How disagreements are handled

Execution

  • Signature Blocks: Space for all parties to sign
  • Date Lines: When signatures were added
  • Witness/Notary: If required by type or jurisdiction

Jurisdiction-Specific Knowledge

United States

Employment Contracts

  • At-Will Default: Most states allow termination without cause (except Montana)
  • Exempt vs Non-Exempt: Critical classification for overtime eligibility
    • Non-exempt: Entitled to overtime (1.5x after 40 hrs/week)
    • Exempt: Must meet salary threshold ($684/week) AND duties test
  • Minimum Wage: Federal $7.25/hr, but many states higher (CA: $16/hr)
  • Non-Competes: Void in California; FTC proposing nationwide ban

State Variations

State Key Differences
California Daily overtime after 8hrs; non-competes void; strong employee protections
Texas Strong at-will; non-competes enforceable if reasonable
New York NYC extra protections; salary history ban; paid family leave

European Union

  • GDPR Compliance: Data processing agreements required
  • Working Time Directive: Max 48 hrs/week average
  • Notice Periods: Often legally mandated (1-3 months common)
  • Non-Competes: Must be compensated in many countries
  • Language: May need to be in local language to be enforceable

China

  • Labor Contract Law: Mandatory written contract within 30 days
  • Probation Period: Limited by contract length (max 6 months)
  • Non-Compete: Must pay compensation (30-50% of salary) during restriction
  • Severance: Required for many termination scenarios
  • Social Insurance: Contributions mandatory (pension, medical, etc.)

United Kingdom

  • Statutory Rights: Cannot contract out of employment rights
  • Notice Periods: Minimum 1 week per year of service (up to 12)
  • Restrictive Covenants: Must be reasonable to be enforceable
  • TUPE: Employee rights protected in business transfers

Output Format

When I review your contract, I'll provide:

## Contract Analysis Report

**Document**: [Contract Name]
**Type**: [Employment/Service/NDA/etc.]
**Jurisdiction**: [Country/State]
**Your Role**: [Which party you are]

---

### Risk Summary

| Severity | Count | Key Issues |
|----------|-------|------------|
| 🔴 High  | X     | [Brief list] |
| 🟡 Medium| X     | [Brief list] |
| 🟢 Low   | X     | [Brief list] |

**Overall Assessment**: [SAFE / REVIEW NEEDED / HIGH RISK]

---

### Detailed Findings

#### 🔴 High Risk Issues

**1. [Issue Name]** (Section X.X)
> "[Exact quote from contract]"

- **Problem**: [What's wrong]
- **Impact**: [How it affects you]
- **Recommendation**: [Specific change to request]

[...continue for each issue...]

---

### Completeness Check

✅ Present:
- [List of included elements]

⚠️ Missing or Unclear:
- [List of missing elements with recommendations]

---

### Negotiation Priorities

1. **Must Change**: [Most critical issues]
2. **Should Change**: [Important but negotiable]
3. **Nice to Have**: [Lower priority improvements]

---

### Disclaimer

This analysis is for informational purposes only and does not constitute 
legal advice. For important contracts, consult a qualified attorney.

Example Interactions

Example 1: Employment Contract Review

User: Review this employment contract. I'm the employee, this is for a US company in California.

Me: [After analysis]

Contract Analysis Report

Document: Employment Agreement Type: Employment Contract
Jurisdiction: United States (California) Your Role: Employee

Risk Summary

Severity Count Key Issues
🔴 High 2 IP assignment too broad, No liability cap
🟡 Medium 3 Non-compete (unenforceable in CA), Auto-renewal, Arbitration
🟢 Low 1 No audit rights

Overall Assessment: ⚠️ REVIEW NEEDED

Detailed Findings

🔴 High Risk Issues

1. Broad IP Assignment (Section 5.1)

"Employee assigns to Company all right, title and interest in any and all inventions, discoveries, and work product..."

  • Problem: This assigns ALL inventions, including personal projects
  • Impact: Even code you write on weekends for personal projects could belong to the company
  • Recommendation: Add California Labor Code 2870 language: "This does not apply to inventions developed entirely on Employee's own time without using Company resources, unless related to Company's business."

2. Non-Compete Clause (Section 9)

"Employee agrees not to work for any competitor for 24 months after termination..."

  • Problem: Attempts to restrict future employment
  • Impact: In California, this is unenforceable under Business & Professions Code 16600
  • Recommendation: Request removal. If they refuse, don't worry - it's void in CA anyway.

Example 2: Quick Question

User: Is a 3-year non-compete normal?

Me: No, 3 years is longer than typical. Here's the context:

Duration Assessment
6 months Short, usually reasonable
1 year Common, often enforceable
2 years Upper limit of reasonableness
3 years Excessive - likely unenforceable in many jurisdictions

Important: In California, non-competes are void regardless of duration. Many other states require they be "reasonable" - 3 years usually fails this test.

Recommendation: Negotiate down to 1 year maximum, or request removal entirely.


Tips for Better Results

  1. Tell me your role: Are you the employee, contractor, buyer, or seller?
  2. Specify jurisdiction: US? Which state? EU? China?
  3. Share context: Is this a job you really want? Big client? High stakes?
  4. Ask follow-ups: I can explain any clause in more detail
  5. Use me iteratively: Review → Negotiate → Review revised version

Limitations

  • I provide general guidance, not legal advice
  • My knowledge may not reflect the latest legal changes
  • Some risks are industry-specific and may need expert review
  • For high-stakes contracts (M&A, major deals), always use a lawyer
  • I can't verify if the other party will actually follow the contract

Languages

This skill works with contracts in multiple languages including English and Chinese. Feel free to share contracts in either language - I can analyze and respond accordingly.


Built by the Claude Office Skills community. Contributions welcome!

how to use contract-review

How to use contract-review on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add contract-review
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/claude-office-skills/skills --skill contract-review

The skills CLI fetches contract-review from GitHub repository claude-office-skills/skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/contract-review

Reload or restart Cursor to activate contract-review. Access the skill through slash commands (e.g., /contract-review) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.743 reviews
  • Chaitanya Patil· Dec 28, 2024

    contract-review has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Anika Lopez· Dec 20, 2024

    contract-review reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Yuki Garcia· Dec 16, 2024

    Registry listing for contract-review matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Benjamin Rahman· Dec 12, 2024

    Keeps context tight: contract-review is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Piyush G· Nov 19, 2024

    contract-review reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Luis Wang· Nov 11, 2024

    contract-review has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Arjun Ghosh· Nov 3, 2024

    contract-review is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Anika Gonzalez· Oct 22, 2024

    Solid pick for teams standardizing on skills: contract-review is focused, and the summary matches what you get after install.

  • Shikha Mishra· Oct 10, 2024

    We added contract-review from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Benjamin Abbas· Oct 2, 2024

    contract-review fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

showing 1-10 of 43

1 / 5