legal-risk-assessment-1-risk-description
Sub-skill of legal-risk-assessment: 1. Risk Description (+10).
Best use case
legal-risk-assessment-1-risk-description is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Sub-skill of legal-risk-assessment: 1. Risk Description (+10).
Teams using legal-risk-assessment-1-risk-description should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/1-risk-description/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How legal-risk-assessment-1-risk-description Compares
| Feature / Agent | legal-risk-assessment-1-risk-description | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Sub-skill of legal-risk-assessment: 1. Risk Description (+10).
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 1. Risk Description (+10) ## 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 |
Related Skills
hse-risk-analyzer
Analyze BSEE HSE (Health, Safety, Environment) incident data for risk assessment. Use for operator safety scoring, incident trend analysis, compliance tracking, and ESG-integrated economic evaluation.
risk-and-redundancy
Use when populating the Watch-outs section of a trip plan. Encodes failure modes (closures, weather, motion sickness, altitude, kid logistics) and the rule that every trip needs a Plan B for load-bearing legs. Invoked by trip-planner.
ai-tool-assessment
Assess and report on AI tool subscriptions, usage patterns, and cost-effectiveness. Use for reviewing AI subscriptions, analyzing tool usage, optimizing AI spend.
maritime-legal
AI-assisted maritime legal and casualty consulting — engineering-technical interface with admiralty proceedings
risk-assessment
Perform probabilistic risk assessment with Monte Carlo simulations for offshore marine operations
multi-tool-architecture-assessment
Systematic comparison of competing tools/approaches before committing to a multi-account, multi-tool architecture. Uses parallel subagents for research, system-state audit, and data quality analysis. Produces a decision matrix with explicit trade-offs.
legal-sanity-scan
Mandatory legal compliance gate for document intelligence, data catalogs, and code porting — scans for client names, proprietary references, and sensitive paths
legal-risk-assessment
Assess and classify legal risks using a severity-by-likelihood framework with escalation criteria
legal-sanity-review
Legal Sanity Review Workflow — mandatory pre-gate in the cross-review cycle
hardware-assessment-workflow-multi-machine-inventory
Sub-skill of hardware-assessment: Workflow: Multi-Machine Inventory.
hardware-assessment-scripts
Sub-skill of hardware-assessment: Scripts.
hardware-assessment-output-schema-v10
Sub-skill of hardware-assessment: Output Schema (v1.0).