agentleFS
insight68insight68/Skills/skills/legal-risk-assessment/SKILL.md

legal-risk-assessment

Skill5 starsChanged 9 months agoMITView on GitHub

Assess and classify legal risks using a severity-by-likelihood framework with escalation criteria. Use when evaluating contract risk, assessing deal exposure, classifying issues by severity, or determining whether a matter needs senior counsel or outside legal review.

11 other projects use a version of this.

Adopted by

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projectsWeek of Nov 8: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Assign owner: Ensure a specific person is responsible for monitoring and mitigation

    line 94
  2. Distinctive:

    Develop mitigation plan: Create a specific, actionable plan to reduce the risk

    line 113
  3. Distinctive:

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

    line 157
  4. Distinctive:

    When recommending outside counsel engagement, suggest the user consider:

    line 258

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
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):

LevelLabelDescription
1NegligibleMinor inconvenience; no material financial, operational, or reputational impact. Can be handled within normal operations.
2LowLimited impact; minor financial exposure (< 1% of relevant contract/deal value); minor operational disruption; no public attention.
3ModerateMeaningful impact; material financial exposure (1-5% of relevant value); noticeable operational disruption; potential for limited public attention.
4HighSignificant impact; substantial financial exposure (5-25% of relevant value); significant operational disruption; likely public attention; potential regulatory scrutiny.
5CriticalSevere 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):

LevelLabelDescription
1RemoteHighly unlikely to occur; no known precedent in similar situations; would require exceptional circumstances.
2UnlikelyCould occur but not expected; limited precedent; would require specific triggering events.
3PossibleMay occur; some precedent exists; triggering events are foreseeable.
4LikelyProbably will occur; clear precedent; triggering events are common in similar situations.
5Almost CertainExpected to occur; strong precedent or pattern; triggering events are present or imminent.

Risk Score Calculation

Risk Score = Severity x Likelihood

Score RangeRisk LevelColor
1-4Low RiskGREEN
5-9Medium RiskYELLOW
10-15High RiskORANGE
16-25Critical RiskRED

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:

FieldContent
Risk IDUnique identifier
Date IdentifiedWhen the risk was first identified
DescriptionBrief description
CategoryContract, Regulatory, Litigation, IP, Data Privacy, Employment, Corporate, Other
Severity1-5 with label
Likelihood1-5 with label
Risk ScoreCalculated score
Risk LevelGREEN / YELLOW / ORANGE / RED
OwnerPerson responsible for monitoring
MitigationsCurrent controls in place
StatusOpen / Mitigated / Accepted / Closed
Review DateNext scheduled review
NotesAdditional 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)

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.