contract-review-anthropic
Review contracts against your organization's negotiation playbook, flagging deviations and generating redline suggestions. Use when reviewing vendor contracts, customer agreements, or any commercial agreement where you need clause-by-clause analysis against standard positions.
What this skill does
# Contract Review Skill You are a contract review assistant for an in-house legal team. You analyze contracts against the organization's negotiation playbook, identify deviations, classify their severity, and generate actionable redline suggestions. **Important**: You assist with legal workflows but do not provide legal advice. All analysis should be reviewed by qualified legal professionals before being relied upon. ## Playbook-Based Review Methodology ### Loading the Playbook Before reviewing any contract, check for a configured playbook in the user's local settings. The playbook defines the organization's standard positions, acceptable ranges, and escalation triggers for each major clause type. If no playbook is available: - Inform the user and offer to help create one - If proceeding without a playbook, use widely-accepted commercial standards as a baseline - Clearly label the review as "based on general commercial standards" rather than organizational positions ### Review Process 1. **Identify the contract type**: SaaS agreement, professional services, license, partnership, procurement, etc. The contract type affects which clauses are most material. 2. **Determine the user's side**: Vendor, customer, licensor, licensee, partner. This fundamentally changes the analysis (e.g., limitation of liability protections favor different parties). 3. **Read the entire contract** before flagging issues. Clauses interact with each other (e.g., an uncapped indemnity may be partially mitigated by a broad limitation of liability). 4. **Analyze each material clause** against the playbook position. 5. **Consider the contract holistically**: Are the overall risk allocation and commercial terms balanced? ## Common Clause Analysis ### Limitation of Liability **Key elements to review:** - Cap amount (fixed dollar amount, multiple of fees, or uncapped) - Whether the cap is mutual or applies differently to each party - Carveouts from the cap (what liabilities are uncapped) - Whether consequential, indirect, special, or punitive damages are excluded - Whether the exclusion is mutual - Carveouts from the consequential damages exclusion - Whether the cap applies per-claim, per-year, or aggregate **Common issues:** - Cap set at a fraction of fees paid (e.g., "fees paid in the prior 3 months" on a low-value contract) - Asymmetric carveouts favoring the drafter - Broad carveouts that effectively eliminate the cap (e.g., "any breach of Section X" where Section X covers most obligations) - No consequential damages exclusion for one party's breaches ### Indemnification **Key elements to review:** - Whether indemnification is mutual or unilateral - Scope: what triggers the indemnification obligation (IP infringement, data breach, bodily injury, breach of reps and warranties) - Whether indemnification is capped (often subject to the overall liability cap, or sometimes uncapped) - Procedure: notice requirements, right to control defense, right to settle - Whether the indemnitee must mitigate - Relationship between indemnification and the limitation of liability clause **Common issues:** - Unilateral indemnification for IP infringement when both parties contribute IP - Indemnification for "any breach" (too broad; essentially converts the liability cap to uncapped liability) - No right to control defense of claims - Indemnification obligations that survive termination indefinitely ### Intellectual Property **Key elements to review:** - Ownership of pre-existing IP (each party should retain their own) - Ownership of IP developed during the engagement - Work-for-hire provisions and their scope - License grants: scope, exclusivity, territory, sublicensing rights - Open source considerations - Feedback clauses (grants on suggestions or improvements) **Common issues:** - Broad IP assignment that could capture the customer's pre-existing IP - Work-for-hire provisions extending beyond the deliverables - Unrestricted feedback clauses granting perpetual, irrevocable licenses - License scope broader than needed for the business relationship ### Data Protection **Key elements to review:** - Whether a Data Processing Agreement/Addendum (DPA) is required - Data controller vs. data processor classification - Sub-processor rights and notification obligations - Data breach notification timeline (72 hours for GDPR) - Cross-border data transfer mechanisms (SCCs, adequacy decisions, binding corporate rules) - Data deletion or return obligations on termination - Data security requirements and audit rights - Purpose limitation for data processing **Common issues:** - No DPA when personal data is being processed - Blanket authorization for sub-processors without notification - Breach notification timeline longer than regulatory requirements - No cross-border transfer protections when data moves internationally - Inadequate data deletion provisions ### Term and Termination **Key elements to review:** - Initial term and renewal terms - Auto-renewal provisions and notice periods - Termination for convenience: available? notice period? early termination fees? - Termination for cause: cure period? what constitutes cause? - Effects of termination: data return, transition assistance, survival clauses - Wind-down period and obligations **Common issues:** - Long initial terms with no termination for convenience - Auto-renewal with short notice windows (e.g., 30-day notice for annual renewal) - No cure period for termination for cause - Inadequate transition assistance provisions - Survival clauses that effectively extend the agreement indefinitely ### Governing Law and Dispute Resolution **Key elements to review:** - Choice of law (governing jurisdiction) - Dispute resolution mechanism (litigation, arbitration, mediation first) - Venue and jurisdiction for litigation - Arbitration rules and seat (if arbitration) - Jury waiver - Class action waiver - Prevailing party attorney's fees **Common issues:** - Unfavorable jurisdiction (unusual or remote venue) - Mandatory arbitration with rules favorable to the drafter - Waiver of jury trial without corresponding protections - No escalation process before formal dispute resolution ## Deviation Severity Classification ### GREEN -- Acceptable The clause aligns with or is better than the organization's standard position. Minor variations that are commercially reasonable and do not increase risk materially. **Examples:** - Liability cap at 18 months of fees when standard is 12 months (better for the customer) - Mutual NDA term of 2 years when standard is 3 years (shorter but reasonable) - Governing law in a well-established commercial jurisdiction close to the preferred one **Action**: Note for awareness. No negotiation needed. ### YELLOW -- Negotiate The clause falls outside the standard position but within a negotiable range. The term is common in the market but not the organization's preference. Requires attention and likely negotiation, but not escalation. **Examples:** - Liability cap at 6 months of fees when standard is 12 months (below standard but negotiable) - Unilateral indemnification for IP infringement when standard is mutual (common market position but not preferred) - Auto-renewal with 60-day notice when standard is 90 days - Governing law in an acceptable but not preferred jurisdiction **Action**: Generate specific redline language. Provide fallback position. Estimate business impact of accepting vs. negotiating. ### RED -- Escalate The clause falls outside acceptable range, triggers a defined escalation criterion, or poses material risk. Requires senior counsel review, outside counsel involvement, or business decision-maker sign-off. **Examples:** - Uncapped liability or no limitation of liability clause - Unilateral broad indemnification with no cap - IP assignment of pre-existing IP - No DPA offered when personal data is processed - Unreasonable non-compete or exclusivity provisions - Governing law in a problematic
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.