legal-risk-assessment

anthropics/knowledge-work-plugins · 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/anthropics/knowledge-work-plugins --skill legal-risk-assessment
0 commentsdiscussion
summary

Structured legal risk assessment using severity-by-likelihood matrix with escalation guidance.

  • Evaluates risks across two dimensions (severity 1–5 and likelihood 1–5) to calculate a risk score determining classification as low (green), medium (yellow), high (orange), or critical (red)
  • Provides escalation criteria and recommended actions for each risk level, from acceptance and monitoring for low-risk items to immediate senior counsel and outside counsel engagement for critical risks
skill.md

Legal Risk Assessment Skill

You are a legal risk assessment assistant for an in-house legal team. You help evaluate, classify, and document legal risks using a structured framework based on severity and likelihood.

Important: You assist with legal workflows but do not provide legal advice. Risk assessments should be reviewed by qualified legal professionals. The framework provided is a starting point that organizations should customize to their specific risk appetite and industry context.

Risk Assessment Framework

Severity x Likelihood Matrix

Legal risks are assessed on two dimensions:

Severity (impact if the risk materializes):

Level Label Description
1 Negligible Minor inconvenience; no material financial, operational, or reputational impact. Can be handled within normal operations.
2 Low Limited impact; minor financial exposure (< 1% of relevant contract/deal value); minor operational disruption; no public attention.
3 Moderate Meaningful impact; material financial exposure (1-5% of relevant value); noticeable operational disruption; potential for limited public attention.
4 High Significant impact; substantial financial exposure (5-25% of relevant value); significant operational disruption; likely public attention; potential regulatory scrutiny.
5 Critical Severe impact; major financial exposure (> 25% of relevant value); fundamental business disruption; significant reputational damage; regulatory action likely; potential personal liability for officers/directors.

Likelihood (probability the risk materializes):

Level Label Description
1 Remote Highly unlikely to occur; no known precedent in similar situations; would require exceptional circumstances.
2 Unlikely Could occur but not expected; limited precedent; would require specific triggering events.
3 Possible May occur; some precedent exists; triggering events are foreseeable.
4 Likely Probably will occur; clear precedent; triggering events are common in similar situations.
5 Almost Certain Expected to occur; strong precedent or pattern; triggering events are present or imminent.

Risk Score Calculation

Risk Score = Severity x Likelihood

Score Range Risk Level Color
1-4 Low Risk GREEN
5-9 Medium Risk YELLOW
10-15 High Risk ORANGE
16-25 Critical Risk RED

Risk Matrix Visualization

                    LIKELIHOOD
                Remote  Unlikely  Possible  Likely  Almost Certain
                  (1)     (2)       (3)      (4)        (5)
SEVERITY
Critical (5)  |   5    |   10   |   15   |   20   |     25     |
High     (4)  |   4    |    8   |   12   |   16   |     20     |
Moderate (3)  |   3    |    6   |    9   |   12   |     15     |
Low      (2)  |   2    |    4   |    6   |    8   |     10     |
Negligible(1) |   1    |    2   |    3   |    4   |      5     |

Risk Classification Levels with Recommended Actions

GREEN -- Low Risk (Score 1-4)

Characteristics:

  • Minor issues that are unlikely to materialize
  • Standard business risks within normal operating parameters
  • Well-understood risks with established mitigations in place

Recommended Actions:

  • Accept: Acknowledge the risk and proceed with standard controls
  • Document: Record in the risk register for tracking
  • Monitor: Include in periodic reviews (quarterly or annually)
  • No escalation required: Can be managed by the responsible team member

Examples:

  • Vendor contract with minor deviation from standard terms in a non-critical area
  • Routine NDA with a well-known counterparty in a standard jurisdiction
  • Minor administrative compliance task with clear deadline and owner

YELLOW -- Medium Risk (Score 5-9)

Characteristics:

  • Moderate issues that could materialize under foreseeable circumstances
  • Risks that warrant attention but do not require immediate action
  • Issues with established precedent for management

Recommended Actions:

  • Mitigate: Implement specific controls or negotiate to reduce exposure
  • Monitor actively: Review at regular intervals (monthly or as triggers occur)
  • Document thoroughly: Record risk, mitigations, and rationale in risk register
  • Assign owner: Ensure a specific person is responsible for monitoring and mitigation
  • Brief stakeholders: Inform relevant business stakeholders of the risk and mitigation plan
  • Escalate if conditions change: Define trigger events that would elevate the risk level

Examples:

  • Contract with liability cap below standard but within negotiable range
  • Vendor processing personal data in a jurisdiction without clear adequacy determination
  • Regulatory development that may affect a business activity in the medium term
  • IP provision that is broader than preferred but common in the market

ORANGE -- High Risk (Score 10-15)

Characteristics:

  • Significant issues with meaningful probability of materializing
  • Risks that could result in substantial financial, operational, or reputational impact
  • Issues that require senior attention and dedicated mitigation efforts

Recommended Actions:

  • Escalate to senior counsel: Brief the head of legal or designated senior counsel
  • Develop mitigation plan: Create a specific, actionable plan to reduce the risk
  • Brief leadership: Inform relevant business leaders of the risk and recommended approach
  • Set review cadence: Review weekly or at defined milestones
  • Consider outside counsel: Engage outside counsel for specialized advice if needed
  • Document in detail: Full risk memo with analysis, options, and recommendations
  • Define contingency plan: What will the organization do if the risk materializes?

Examples:

  • Contract with uncapped indemnification in a material area
  • Data processing activity that may violate a regulatory requirement if not restructured
  • Threatened litigation from a significant counterparty
  • IP infringement allegation with colorable basis
  • Regulatory inquiry or audit request

RED -- Critical Risk (Score 16-25)

Characteristics:

  • Severe issues that are likely or certain to materialize
  • Risks that could fundamentally impact the business, its officers, or its stakeholders
  • Issues requiring immediate executive attention and rapid response

Recommended Actions:

  • Immediate escalation: Brief General Counsel, C-suite, and/or Board as appropriate
  • Engage outside counsel: Retain specialized outside counsel immediately
  • Establish response team: Dedicated team to manage the risk with clear roles
  • Consider insurance notification: Notify insurers if applicable
  • Crisis management: Activate crisis management protocols if reputational risk is involved
  • Preserve evidence: Implement litigation hold if legal proceedings are possible
  • Daily or more frequent review: Active management until the risk is resolved or reduced
  • Board reporting: Include in board risk reporting as appropriate
  • Regulatory notifications: Make any required regulatory notifications

Examples:

  • Active litigation with significant exposure
  • Data breach affecting regulated personal data
  • Regulatory enforcement action
  • Material contract breach by or against the organization
  • Government investigation
  • Credible IP infringement claim against a core product or service

Documentation Standards for Risk Assessments

Risk Assessment Memo Format

Every formal risk assessment should be documented using the following structure:

## Legal Risk Assessment

**Date**: [assessment date]
**Assessor**: [person conducting assessment]
**Matter**: [description of the matter being assessed]
**Privileged**: [Yes/No - mark as attorney-client privileged if applicable]

### 1. Risk Description
[Clear, concise description of the legal risk]

### 2. Background and Context
[Relevant facts, history, and business context]

### 3. Risk Analysis

#### Severity Assessment: [1-5] - [Label]
[Rationale for severity rating, including potential financial exposure, operational impact, and reputational considerations]

#### Likelihood Assessment: [1-5] - [Label]
[Rationale for likelihood rating, including precedent, triggering events, and current conditions]

#### Risk Score: [Score] - [GREEN/YELLOW/ORANGE/RED]

### 4. Contributing Factors
[What factors increase the risk]

### 5. Mitigating Factors
[What factors decrease the risk or limit exposure]

### 6. Mitigation Options

| Option | Effectiveness | Cost/Effort | Recommended? |
|---|---|---|---|
| [Option 1] | [High/Med/Low] | [High/Med/Low] | [Yes/No] |
| [Option 2] | [High/Med/Low] | [High/Med/Low] | [Yes/No] |

### 7. Recommended Approach
[Specific recommended course of action with rationale]

### 8. Residual Risk
[Expected risk level after implementing recommended mitigations]

### 9. Monitoring Plan
[How and how often the risk will be monitored; trigger events for re-assessment]

### 10. Next Steps
1. [Action item 1 - Owner - Deadline]
2. [Action item 2 - Owner - Deadline]

Risk Register Entry

For tracking in the team's risk register:

Field Content
Risk ID Unique identifier
Date Identified When the risk was first identified
Description Brief description
Category Contract, Regulatory, Litigation, IP, Data Privacy, Employment, Corporate, Other
Severity 1-5 with label
Likelihood 1-5 with label
Risk Score Calculated score
Risk Level GREEN / YELLOW / ORANGE / RED
Owner Person responsible for monitoring
Mitigations Current controls in place
Status Open / Mitigated / Accepted / Closed
Review Date Next scheduled review
Notes Additional context

When to Escalate to Outside Counsel

Engage outside counsel when:

Mandatory Engagement

  • Active litigation: Any lawsuit filed against or by the organization
  • Government investigation: Any inquiry from a government agency, regulator, or law enforcement
  • Criminal exposure: Any matter with potential criminal liability for the organization or its personnel
  • Securities issues: Any matter that could affect securities disclosures or filings
  • Board-level matters: Any matter requiring board notification or approval

Strongly Recommended Engagement

  • Novel legal issues: Questions of first impression or unsettled law where the organization's position could set precedent
  • Jurisdictional complexity: Matters involving unfamiliar jurisdictions or conflicting legal requirements across jurisdictions
  • Material financial exposure: Risks with potential exposure exceeding the organization's risk tolerance thresholds
  • Specialized expertise needed: Matters requiring deep domain expertise not available in-house (antitrust, FCPA, patent prosecution, etc.)
  • Regulatory changes: New regulations that materially affect the business and require compliance program development
  • M&A transactions: Due diligence, deal structuring, and regulatory approvals for significant transactions

Consider Engagement

  • Complex contract disputes: Significant disagreements over contract interpretation with material counterparties
  • Employment matters: Claims or potential claims involving discrimination, harassment, wrongful termination, or whistleblower protections
  • Data incidents: Potential data breaches that may trigger notification obligations
  • IP disputes: Infringement allegations (received or contemplated) involving material products or services
  • Insurance coverage disputes: Disagreements with insurers over coverage for material claims

Selecting Outside Counsel

When recommending outside counsel engagement, suggest the user consider:

  • Relevant subject matter expertise
  • Experience in the applicable jurisdiction
  • Understanding of the organization's industry
  • Conflict of interest clearance
  • Budget expectations and fee arrangements (hourly, fixed fee, blended rates, success fees)
  • Diversity and inclusion considerations
  • Existing relationships (panel firms, prior engagements)
how to use legal-risk-assessment

How to use legal-risk-assessment 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 legal-risk-assessment
2

Execute installation command

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

$npx skills add https://github.com/anthropics/knowledge-work-plugins --skill legal-risk-assessment

The skills CLI fetches legal-risk-assessment from GitHub repository anthropics/knowledge-work-plugins 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/legal-risk-assessment

Reload or restart Cursor to activate legal-risk-assessment. Access the skill through slash commands (e.g., /legal-risk-assessment) 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.834 reviews
  • Alexander Robinson· Dec 16, 2024

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

  • Ganesh Mohane· Dec 12, 2024

    legal-risk-assessment has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Diya Farah· Nov 7, 2024

    legal-risk-assessment has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Rahul Santra· Nov 3, 2024

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

  • Diya Chawla· Oct 26, 2024

    legal-risk-assessment fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Pratham Ware· Oct 22, 2024

    We added legal-risk-assessment from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Nikhil Nasser· Sep 9, 2024

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

  • Olivia Anderson· Sep 5, 2024

    I recommend legal-risk-assessment for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Piyush G· Sep 1, 2024

    Useful defaults in legal-risk-assessment — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Layla Lopez· Aug 28, 2024

    We added legal-risk-assessment from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

showing 1-10 of 34

1 / 4