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
- insight68/Skillstheir own version, first seen Nov 8, 2026
- anthropics/knowledge-work-pluginstheir own version, first seen Oct 13, 2026
- Tgoldi/claude-skillstheir own version, first seen Oct 13, 2026
- edu6565/claude-skillstheir own version, first seen Oct 11, 2026
- EvolutionAPI/evo-nexustheir own version, first seen Oct 8, 2026
- yiyan-yixing/skillstheir own version, first seen Aug 5, 2026
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.
SentrySkillskill-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
Other versions11 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 11
- anthropics/knowledge-work-plugins★ 36ksame name
- THUYRan/Legal-Skills-Chinese★ 974same name
- EvolutionAPI/evo-nexus★ 545same name
- evolution-foundation/evo-nexus★ 535same name
- alebgl77/claude-inc★ 21same name
- insight68/Skills★ 5same name
- JustineDevs/premortem★ 2same name
- yiyan-yixing/skills★ 1same name
- edu6565/claude-skills★ 0same name
- Tgoldi/claude-skills★ 0same name
1 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository164 other files it gives its agents.
- instrument-data-to-allotropeSkill
- literature-reviewSkill
- nextflow-developmentSkill
- scientific-problem-selectionSkill
- scvi-toolsSkill
- single-cell-rna-qcSkill
- discover-brandSkill
- enforce-voiceSkill
- generate-guidelinesSkill
- csat-reportSkill
- customer-escalationSkill
- customer-researchSkill
- draft-responseSkill
- kb-articleSkill
- sentiment-analysisSkill
- ticket-triageSkill
- analyzeSkill
- build-dashboardSkill
- create-vizSkill
- data-context-extractorSkill
- data-modelingSkill
- data-pipelineSkill
- etl-designSkill
- explore-dataSkill
- sql-queriesSkill
- statistical-analysisSkill
- validate-dataSkill
- write-querySkill
- accessibility-reviewSkill
- component-librarySkill
- design-critiqueSkill
- design-handoffSkill
- design-systemSkill
- frontend-designSkill
- research-synthesisSkill
- user-researchSkill
- ux-copySkill
- wireframingSkill
- Agent DevelopmentSkill
- CLAUDE.md ManagementSkill
- MCP Server BuilderSkill
- Plugin DevelopmentSkill
- Prompt EngineeringSkill
- Skill CreatorSkill
- curriculum-designSkill
- lesson-planningSkill
- quiz-generatorSkill
- study-guideSkill
- tutoringSkill
- api-designSkill
- architectureSkill
- ci-cd-pipelineSkill
- code-reviewSkill
- database-migrationSkill
- debugSkill
- dependency-auditSkill
- deploy-checklistSkill
- documentationSkill
- error-handlingSkill
- git-workflowSkill
- The first 60 shown.
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
- Distinctive: line 87
Use ranges for financial exposure rather than single-point estimates.
“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.
Files
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.
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
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.

