Structured legal risk assessment with 5x5 Severity x Likelihood matrix. Use for risk scoring, risk registers, escalation decisions, and risk memos.
npx clawhub@latest install legal-risk-assessment⚠️ EXPERIMENTAL — This skill is provided for educational and informational purposes only. It does NOT constitute legal advice. All responsibility for usage rests with the user. Consult qualified legal professionals before acting on any output.
Structured legal risk assessment using a quantitative 5x5 Severity x Likelihood matrix. Scores risks, maintains registers, generates assessment memos, and guides escalation decisions.
Calculates risk scores from severity and likelihood inputs, assigns color-coded risk levels, and generates summary statistics.
# Score a single risk python scripts/risk_scorer.py --severity 4 --likelihood 3 \ --category "Contract" --description "Vendor SLA non-compliance" # JSON output python scripts/risk_scorer.py --severity 4 --likelihood 3 \ --category "Contract" --description "Vendor SLA breach" --json # Batch mode from risk register file python scripts/risk_scorer.py --input risks.json --json # Batch mode with human-readable output python scripts/risk_scorer.py --input risks.jsonInput JSON format (batch mode):
{ "risks": [ {"severity": 4, "likelihood": 3, "category": "Contract", "description": "Vendor SLA breach"}, {"severity": 2, "likelihood": 2, "category": "Regulatory", "description": "Minor filing delay"} ] }Output includes:
Generates a formatted risk assessment memo in markdown from a risk register JSON file.
# Generate memo from risk register python scripts/risk_report_generator.py --input risk_register.json # Save to file python scripts/risk_report_generator.py --input risk_register.json --output memo.md # JSON metadata output python scripts/risk_report_generator.py --input risk_register.json --jsonReport includes:
references/risk_framework.md
Complete Severity x Likelihood matrix reference:
references/escalation_guide.md
When to engage outside counsel:
Step 1: Identify risk category and description
→ Use references/risk_framework.md category definitions
Step 2: Score severity (1-5) and likelihood (1-5)
→ python scripts/risk_scorer.py --severity N --likelihood N \
--category "Category" --description "Description"
Step 3: Review risk level and recommended action
→ GREEN: Accept and document
→ YELLOW: Assign owner and monitor
→ ORANGE: Escalate to senior counsel
→ RED: Immediate escalation, crisis management
Step 4: Determine outside counsel need
→ Consult references/escalation_guide.md
Step 5: Document in risk register
→ Add entry to register JSON file
Step 1: Load current risk register
→ python scripts/risk_scorer.py --input register.json
Step 2: Generate assessment memo
→ python scripts/risk_report_generator.py --input register.json --output memo.md
Step 3: Review top risks and distribution
→ Focus on ORANGE and RED risks first
Step 4: Update severity/likelihood for changed risks
→ Re-score and regenerate report
Step 5: Distribute memo to stakeholders
Step 1: Score the risk → python scripts/risk_scorer.py --severity N --likelihood N \ --category "Category" --description "Description" Step 2: Check escalation triggers → Mandatory: active litigation, government investigation, criminal exposure → Strongly Recommended: novel issues, jurisdictional complexity, material exposure → Consider: complex disputes, employment matters, data incidents Step 3: Document escalation rationale → Include risk score, level, and specific trigger in memo Step 4: Select outside counsel if needed → See references/escalation_guide.md criteria
| Problem | Possible Cause | Resolution |
|---|---|---|
| Risk score seems too low for a serious matter | Severity or likelihood underestimated; qualitative factors not captured | Review severity descriptions in risk_framework.md; consider worst-case financial exposure; add contributing factors to description |
| Multiple risks in same category but different scores | Risks have different severity/likelihood combinations | This is expected; each risk is independent; review category-level trends in report |
| Batch mode fails on input file | Malformed JSON or missing required fields | Verify JSON structure matches expected format; ensure each risk has severity, likelihood, category, description |
| Report generator produces empty matrix | No risks in input file or all risks have invalid scores | Check that input JSON contains valid risks with severity 1-5 and likelihood 1-5 |
| Escalation guide suggests outside counsel but budget is constrained | Risk score indicates material exposure | Document the budget constraint and residual risk acceptance; consider limited-scope engagement |
| Risk register grows unwieldy | Risks not being closed or consolidated | Archive resolved risks; consolidate related risks; review register quarterly |
In Scope:
Out of Scope:
Calculates risk scores and assigns color-coded risk levels with recommended actions.
| Flag | Required | Description |
|---|---|---|
--severity <1-5> |
Yes (single mode) | Severity rating: 1=Negligible, 2=Minor, 3=Moderate, 4=Major, 5=Critical |
--likelihood <1-5> |
Yes (single mode) | Likelihood rating: 1=Remote, 2=Unlikely, 3=Possible, 4=Likely, 5=Almost Certain |
--category <text> |
Yes (single mode) | Risk category: Contract, Regulatory, Litigation, IP, Data Privacy, Employment, Corporate |
--description <text> |
Yes (single mode) | Risk description |
--input <file> |
Yes (batch mode) | Path to JSON file containing multiple risks |
--json |
No | Output results in JSON format |
Generates formatted risk assessment memo from a risk register JSON file.
| Flag | Required | Description |
|---|---|---|
--input <file> |
Yes | Path to risk register JSON file |
--output <file> |
No | Save memo to specified file path (markdown format) |
--json |
No | Output report metadata in JSON format |
npx clawhub@latest install legal-risk-assessmentnpx clawhub@latest install legal-risk-assessmentInicia sesión para escribir una reseña
Aún no hay reseñas. ¡Sé el primero en compartir tu experiencia!