contract-review
Clause-by-clause contract analysis against your organization's negotiation playbook, with severity flagging and redline suggestions.
- Loads a configured playbook defining your standard positions, acceptable ranges, and escalation triggers for each major clause type; uses general commercial standards as baseline if no playbook exists
- Analyzes material clauses (limitation of liability, indemnification, IP ownership, data protection, term/termination, governing law) with holistic contract review to catch interactions between provisions
- Classifies deviations as GREEN (acceptable), YELLOW (negotiate), or RED (escalate), with specific redline language, rationale, and fallback positions ready for counterparty counsel
- Organizes redlines by negotiation priority (must-haves, should-haves, nice-to-haves) and estimates business impact of accepting vs. negotiating each term
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
More from anthropics/knowledge-work-plugins
data-visualization
Create effective data visualizations with Python (matplotlib, seaborn, plotly). Use when building charts, choosing the right chart type for a dataset, creating publication-quality figures, or applying design principles like accessibility and color theory.
6.4Kcode-review
Review code changes for security, performance, and correctness. Trigger with a PR URL or diff, "review this before I merge", "is this code safe?", or when checking a change for N+1 queries, injection risks, missing edge cases, or error handling gaps.
4.2Ktask-management
Simple task management using a shared TASKS.md file. Reference this when the user asks about their tasks, wants to add/complete tasks, or needs help tracking commitments.
3.5Ksystem-design
Design systems, services, and architectures. Trigger with "design a system for", "how should we architect", "system design for", "what's the right architecture for", or when the user needs help with API design, data modeling, or service boundaries.
3.3Kdocumentation
Write and maintain technical documentation. Trigger with "write docs for", "document this", "create a README", "write a runbook", "onboarding guide", or when the user needs help with any form of technical writing — API docs, architecture docs, or operational runbooks.
3.3Kmemory-management
Two-tier memory system that makes Claude a true workplace collaborator. Decodes shorthand, acronyms, nicknames, and internal language so Claude understands requests like a colleague would. CLAUDE.md for working memory, memory/ directory for the full knowledge base.
3.3K