agentleFS
nisarthnisarth/claude-skills-store/skills/legal/legal-risk-assessment/SKILL.md

legal-risk-assessment

Skill1 starsChanged 7 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, or determining whether a matter needs senior counsel. Trigger with "legal risk assessment", "assess this risk", "what's the legal exposure", "risk matrix", or "classify this legal risk".

11 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use skill-creator.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • SentrySkill

    skill-creator

    Create new agent skills following the Agent Skills specification. Use when asked to "create a skill", "add a new skill", "write a skill", "make a skill", "build a skill", or scaffold a new skill with SKILL.md. Guides through requirements, writing, registration, and verification.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 1

    Distinctive

    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:

    Use ranges for financial exposure rather than single-point estimates.

    line 87

“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “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

Assess legal risks using a severity-by-likelihood matrix. Classify risks, determine escalation paths, and produce mitigation recommendations.

Workflow

Step 1: Define Scope

Identify the matter, risk category, stakeholders, jurisdiction, and time horizon (immediate, near-term, long-term).

Step 2: Identify Specific Risks

Enumerate risks: contract (unfavorable terms, unlimited liability), litigation (breach, infringement), regulatory (non-compliance, enforcement), IP (infringement, open source), employment (wrongful termination, wage), data privacy (breach, consent failures).

Step 3: Score Each Risk

  • Likelihood: 1 (Rare <10%) to 5 (Almost certain >75%)
  • Severity: 1 (Minimal <$50K) to 5 (Critical >$10M)
  • Risk score = Likelihood x Severity (1-25)

Step 4: Classify and Escalate

  • LOW (1-4): Monitor with standard processes.
  • MEDIUM (5-9): Assign owner and mitigation plan.
  • HIGH (10-15): Escalate to senior counsel with regular reporting.
  • CRITICAL (16-25): Escalate to GC and executive team immediately.

Step 5: Develop Mitigations

For each MEDIUM+ risk, define actions, owners, deadlines, expected risk reduction, and residual risk.

Output Format

## Legal Risk Assessment
**Matter**: [Description] | **Date**: [YYYY-MM-DD]
**Overall Rating**: [LOW / MEDIUM / HIGH / CRITICAL]

### Risk Matrix
| # | Risk | Likelihood | Severity | Score | Rating |
|---|------|-----------|----------|-------|--------|
| 1 | [Risk] | 4 | 3 | 12 | HIGH |

### Detailed Analysis
**Risk 1: [Name]** -- Rating: HIGH
- Financial exposure: [$X - $Y range]
- Trigger events: [What causes materialization]

### Mitigation Plan
| # | Action | Owner | Deadline | Status |
|---|--------|-------|----------|--------|
| 1 | [Action] | [Name] | [Date] | OPEN |

Examples

User: "Assess the risk of this contract with unlimited liability" Action: Score unlimited liability exposure, indemnification breadth, data processing terms, and IP ambiguity. Flag unlimited liability as HIGH, recommend capping at 12 months of fees.

User: "What's our exposure if we proceed without the DPIA?" Action: Assess GDPR enforcement risk (fine up to 4% of global revenue), reputational risk, and individual claims. Classify as HIGH and recommend completing the DPIA first.

Best Practices

  • Score risks independently -- do not let one high-severity risk bias others.
  • Use ranges for financial exposure rather than single-point estimates.
  • Distinguish inherent risk (before controls) from residual risk (after controls).
  • For contracts, assess the worst-case reading of ambiguous terms.
  • Include trigger events that would cause each risk to materialize.
  • The overall rating should reflect the highest individual risk, not the average.

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.