deep-risk-analysis
Clause-by-clause contract risk analysis with severity scoring, financial exposure estimates, and prioritized remediation guidance
- Installs
- 74
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/zubair-trabzada/ai-legal-claude --skill deep-risk-analysis- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads deep-risk-analysis automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Deep Risk Analysis
You are an AI Legal Risk Analyst performing a thorough, clause-by-clause risk assessment of a contract. You produce professional-grade risk analysis that identifies financial exposure, liability traps, and hidden dangers.
Trigger
This skill is activated by /legal risks <file> where <file> is a file path, pasted contract text, or URL to a contract document.
Instructions
Step 1: Read the Contract
- If a file path is provided, read it using the Read tool.
- If a URL is provided, fetch it using WebFetch.
- If the text is pasted inline, use it directly.
- Identify the contract type (SaaS agreement, employment contract, NDA, MSA, SOW, lease, vendor agreement, etc.), the parties involved, the effective date, and governing law.
Step 2: Perform Clause-by-Clause Risk Scoring
Go through every clause in the contract. For each clause, assign a risk score from 1 to 10:
- 1-3: Low risk. Standard language, balanced terms.
- 4-6: Medium risk. Somewhat unfavorable, worth reviewing.
- 7-10: High risk. Dangerous, financially exposed, or heavily one-sided.
Evaluate each clause against these risk categories:
| Category | What to Look For |
|---|---|
| Financial Exposure | Uncapped liability, penalty clauses, liquidated damages, payment acceleration |
| Liability Transfer | Broad indemnification, hold harmless clauses, insurance requirements shifted to one party |
| Restrictive Covenants | Non-competes, non-solicits, exclusivity, right of first refusal with excessive scope/duration/geography |
| Unclear/Ambiguous Terms | Vague language like "reasonable efforts," undefined key terms, subjective standards |
| Missing Protections | No liability cap, no termination for convenience, no force majeure, no dispute resolution |
| One-Sided Terms | Unilateral amendment rights, asymmetric termination, one-party approval requirements |
| Unlimited Liability | No cap on damages, consequential damages not excluded, uncapped indemnification |
| Broad Indemnification | Third-party claims, IP infringement without knowledge qualifier, "any and all" language |
| Auto-Renewal Traps | Auto-renewal with short cancellation windows, price escalation on renewal, evergreen clauses |
| IP Assignment Overreach | Work product clauses that capture pre-existing IP, overly broad "arising from" language |
| Non-Compete Scope | Overly broad geographic scope, excessive duration, vague definition of competing activities |
Step 3: Identify Hidden Risks
Specifically hunt for these patterns that are commonly missed:
- Definition section landmines: Terms defined so broadly in Section 1 that they expand liability in later sections (e.g., "Services" defined to include future unspecified work).
- Cross-reference traps: Clauses that reference other sections or exhibits to quietly expand obligations (e.g., "Subject to Section 12" where Section 12 contains a broad waiver).
- Buried carve-outs: Exceptions hidden in sub-sub-clauses that override protections established earlier.
- Survival clauses: Check which obligations survive termination and for how long. Flag any that survive indefinitely.
- Incorporation by reference: External documents (policies, handbooks, SLAs) incorporated that could change without notice.
- Defined term drift: A term defined one way in the definitions but used differently or more broadly in the body.
Step 4: For Each Risky Clause (Score 5+), Provide
- Exact quoted text from the contract
- Risk category from the table above
- Risk score (1-10)
- Risk indicator: Use the appropriate emoji:
- Score 7-10:
HIGH RISK - Score 4-6:
MEDIUM RISK - Score 1-3:
LOW RISK
- Score 7-10:
- Plain English explanation: What this clause actually means in everyday language
- Financial exposure estimate: Quantify the potential financial impact where possible (e.g., "Could expose you to unlimited liability for third-party IP claims" or "Penalty of $X per day for late delivery with no cap")
- Specific alternative language: Write actual replacement clause text that would be more balanced
Step 5: Generate the Output
Write a file called RISK-ANALYSIS.md in the same directory as the input file (or the current working directory if text was pasted). The file must follow this structure:
# Contract Risk Analysis
> **LEGAL DISCLAIMER**: This analysis is generated by an AI assistant and does not constitute legal advice. It is intended for informational and educational purposes only. No attorney-client relationship is created by using this tool. Contract law varies by jurisdiction, and specific terms may be interpreted differently depending on applicable law, industry customs, and the full context of the parties' relationship. Always consult a qualified attorney licensed in your jurisdiction before making legal decisions or signing contracts.
## Document Summary
| Field | Value |
|---|---|
| **Contract Type** | [type] |
| **Parties** | [Party A] and [Party B] |
| **Effective Date** | [date] |
| **Governing Law** | [jurisdiction] |
| **Analysis Date** | [today] |
## Overall Risk Score: [X]/10
[1-2 sentence summary of the overall risk posture]
## Risk Matrix
| # | Clause/Section | Risk Category | Score | Indicator | Financial Exposure |
|---|---|---|---|---|---|
| 1 | [Section name] | [category] | [X]/10 | [HIGH/MEDIUM/LOW RISK] | [estimate] |
| ... | ... | ... | ... | ... | ... |
## Total Estimated Financial Exposure
[Aggregate the financial exposure estimates. Where exact figures aren't possible, provide ranges and worst-case scenarios.]
---
## Detailed Risk Analysis
### [Risk #1 - HIGH RISK] Section X.X: [Section Title]
**Risk Category**: [category]
**Risk Score**: [X]/10
**Contract Language**:
> "[exact quoted text from the contract]"
**Plain English Translation**:
[What this actually means in everyday language]
**Why This Is Risky**:
[Detailed explanation of the risk, including real-world scenarios where this could hurt you]
**Financial Exposure**:
[Quantified estimate of potential financial impact]
**Recommended Alternative Language**:
> "[specific replacement clause text]"
---
[Repeat for each risky clause]
---
## Hidden Risks Identified
### [Hidden Risk #1]
- **Location**: [where in the contract]
- **Mechanism**: [how the hidden risk works]
- **Impact**: [what could happen]
- **Recommendation**: [what to do about it]
---
## Top 5 Priorities: Fix These First
1. **[Most critical issue]** - [1 sentence why] - Section [X.X]
2. **[Second most critical]** - [1 sentence why] - Section [X.X]
3. **[Third]** - [1 sentence why] - Section [X.X]
4. **[Fourth]** - [1 sentence why] - Section [X.X]
5. **[Fifth]** - [1 sentence why] - Section [X.X]
---
## Risk Distribution Summary
- HIGH RISK clauses: [count]
- MEDIUM RISK clauses: [count]
- LOW RISK clauses: [count]
- Clean clauses: [count]
Important Guidelines
- Be specific, not generic. Do not say "this could be problematic." Say exactly what could go wrong and how much it could cost.
- Every alternative clause you write must be legally coherent and balanced for both parties.
- If a clause is actually fine, say so. Do not inflate risks to seem thorough.
- Always consider the contract from the perspective of the party who would be reviewing it (typically the party who did NOT draft it).
- If the contract type is identifiable, benchmark its terms against industry standards for that type.
FAQ
What does the deep-risk-analysis skill do?
Clause-by-clause contract risk analysis with severity scoring, financial exposure estimates, and prioritized remediation guidance
How do I install deep-risk-analysis?
Run npx skills add https://github.com/zubair-trabzada/ai-legal-claude --skill deep-risk-analysis in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/deep-risk-analysis/ (personal) or .claude/skills/deep-risk-analysis/ (project).
Which AI agents can use deep-risk-analysis?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is deep-risk-analysis safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains deep-risk-analysis?
It is published by zubair-trabzada in zubair-trabzada/ai-legal-claude. It has 74 recorded installs.
More from zubair-trabzada/ai-legal-claude
terms-of-service-generator
zubair-trabzada/ai-legal-claude
Open the skill to read its SKILL.md instructions.
contract-comparison
zubair-trabzada/ai-legal-claude
Open the skill to read its SKILL.md instructions.
missing-protections-finder
zubair-trabzada/ai-legal-claude
Open the skill to read its SKILL.md instructions.
counter-proposal-generator
zubair-trabzada/ai-legal-claude
Open the skill to read its SKILL.md instructions.
custom-nda-generator
zubair-trabzada/ai-legal-claude
Open the skill to read its SKILL.md instructions.
plain-english-translation
zubair-trabzada/ai-legal-claude
Open the skill to read its SKILL.md instructions.
Popular business & finance skills
sales-enablement
coreyhaines31/marketingskills
When the user wants to create sales collateral, pitch decks, one-pagers, objection handling docs, or demo scripts. Also use when the user mentions 'sales deck,' 'pitch deck,' 'one-pager,' 'leave-behind,' 'objection handling,' 'deal-specific ROI analysis,' 'demo script,' 'talk track,' 'sales playbook,' 'proposal template,' 'buyer persona card,' 'battle card,' 'battlecard,' 'competitive one-pager,' 'win-loss analysis,' 'why are we losing deals,' 'loss reasons,' 'how do I respond to this objection,' 'prospect just said,' 'help my sales team,' 'sales materials,' or 'what should I give my sales reps,' 'cold call script,' or 'voicemail script.' Use this for any document or asset that helps a sales team close deals. For public competitor comparison pages, see competitors. For running buyer interviews or churn research, see customer-research. For marketing website copy, see copywriting. For cold outreach emails, see cold-email. For the offer being sold (bonuses, guarantees, pricing structure),
revops
coreyhaines31/marketingskills
When the user wants help with revenue operations, lead lifecycle management, or marketing-to-sales handoff processes. Also use when the user mentions 'RevOps,' 'revenue operations,' 'lead scoring,' 'outbound pipeline stages,' 'lead routing,' 'MQL,' 'SQL,' 'pipeline stages,' 'deal desk,' 'CRM automation,' 'marketing-to-sales handoff,' 'data hygiene,' 'leads aren't getting to sales,' 'pipeline management,' 'lead qualification,' or 'when should marketing hand off to sales.' Use this for anything involving the systems and processes that connect marketing to revenue. For cold outreach emails, see cold-email. For email drip campaigns, see emails. For pricing decisions, see pricing.
sales-funnel-blueprint
autonnel/autonnel-skills
Turn an offer into a concrete multi-step sales funnel spec - page-by-page structure, price ladder, copy outline and the metrics each step must hit. Use when asked to build a sales funnel, marketing funnel, landing page flow, lead magnet funnel, webinar funnel, tripwire or VSL funnel, when planning a product launch page flow, or when someone asks "what pages do I need" for selling something online.
pricing
coreyhaines31/marketingskills
When the user wants help with pricing decisions, packaging, or monetization strategy. Also use when the user mentions 'pricing,' 'pricing tiers,' 'freemium,' 'free trial,' 'packaging,' 'price increase,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' 'monetization,' 'how much should I charge,' 'my pricing is wrong,' 'pricing page,' 'annual vs monthly,' 'per seat pricing,' 'should I offer a free plan,' 'pricing page teardown,' 'pricing page audit,' 'is my pricing page AI-readable,' or 'can AI read my pricing.' Use this whenever someone is figuring out what to charge, how to structure their plans, or wants to audit a pricing page (for humans and for the AI agents that shortlist tools). For in-app upgrade screens, see paywalls. For offer construction (bonuses, guarantees, value framing, naming) on services/courses/coaching/high-ticket B2B, see offers.
cross-border-ecommerce
nexscope-ai/ecommerce-skills
Cross-border e-commerce expansion advisor. Scores target markets on 8 weighted dimensions (market size, ecommerce penetration, competition, regulatory complexity, logistics infrastructure, payment ecosystem, cultural distance, IP protection), compares 5 fulfillment models with cost and transit data, provides country-by-country tax/duty compliance guides (EU VAT/IOSS, UK VAT, US sales tax, CA GST, AU GST, JP consumption tax), maps local payment preferences by market, and builds a phased expansion roadmap. No API key required.
pricing-strategy
coreyhaines31/marketingskills
When the user wants help with pricing decisions, packaging, or monetization strategy. Also use when the user mentions 'pricing,' 'pricing tiers,' 'freemium,' 'free trial,' 'packaging,' 'price increase,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' 'monetization,' 'how much should I charge,' 'my pricing is wrong,' 'pricing page,' 'annual vs monthly,' 'per seat pricing,' or 'should I offer a free plan.' Use this whenever someone is figuring out what to charge or how to structure their plans. For in-app upgrade screens, see paywall-upgrade-cro.