How do I install the Risk Assessment skill?

Run npx skillmds add uukuguy/risk-assessment in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Risk Assessment skill do?

Risk identification and analysis frameworks for technology decisions It is listed under Coding & Dev Tools on SkillMD.

Is Risk Assessment safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Risk Assessment?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Risk Assessment free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Risk Assessment?

uukuguy (@uukuguy) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Risk Assessment by uukuguy — Agent Skill

Name: Risk Assessment
Rating: 4.2 (5 reviews)
Author: uukuguy

File contents

Risk Assessment Skill

Objectives

Provide structured methodology for identifying and analyzing risks:

Systematic risk identification
Impact and probability assessment
Mitigation strategy development

Risk Categories

Technical Risks

Risk Type	Examples	Indicators
Performance	Latency, throughput issues	Benchmark gaps, load test failures
Scalability	Growth limitations	Architecture constraints, bottlenecks
Reliability	System failures, data loss	SPOF, recovery gaps
Security	Vulnerabilities, breaches	CVEs, compliance gaps
Integration	API incompatibilities	Version conflicts, protocol mismatches

Implementation Risks

Risk Type	Examples	Indicators
Timeline	Delays, scope creep	Complexity underestimation
Resource	Skill gaps, turnover	Training needs, market scarcity
Quality	Technical debt, bugs	Code coverage gaps, review failures
Dependency	Third-party failures	Vendor instability, EOL products

Business Risks

Risk Type	Examples	Indicators
Financial	Budget overrun, hidden costs	Incomplete TCO analysis
Strategic	Lock-in, obsolescence	Single vendor dependency
Operational	Downtime, productivity loss	Change management gaps
Compliance	Regulatory violations	Certification requirements

Risk Assessment Matrix

Probability Scale

Level	Description	Likelihood
5	Almost Certain	>90%
4	Likely	60-90%
3	Possible	30-60%
2	Unlikely	10-30%
1	Rare	<10%

Impact Scale

Level	Description	Effect
5	Critical	Project failure, major loss
4	Major	Significant delay, budget overrun
3	Moderate	Notable impact, recoverable
2	Minor	Limited impact, easily managed
1	Negligible	Minimal impact

Risk Score = Probability × Impact

Score	Priority	Action
15-25	Critical	Immediate mitigation required
8-14	High	Mitigation plan essential
4-7	Medium	Monitor and plan contingency
1-3	Low	Accept and monitor

Mitigation Strategies

Strategy Types

Avoid: Eliminate the risk source
Transfer: Shift risk to third party (insurance, contracts)
Mitigate: Reduce probability or impact
Accept: Acknowledge and prepare contingency

Mitigation Plan Template

## Risk: [Risk Name]

**Category**: [Technical/Implementation/Business]
**Probability**: [1-5]
**Impact**: [1-5]
**Risk Score**: [P × I]

### Description
[Detailed risk description]

### Root Cause
[What causes this risk]

### Impact Analysis
- Best case: [Outcome]
- Most likely: [Outcome]
- Worst case: [Outcome]

### Mitigation Strategy
- Strategy type: [Avoid/Transfer/Mitigate/Accept]
- Actions:
  1. [Action 1]
  2. [Action 2]
- Cost: [Mitigation cost]

### Contingency Plan
[What to do if risk occurs]

### Monitoring
- Trigger indicators: [Warning signs]
- Review frequency: [Weekly/Monthly]

Output Specification

Risk assessments should include:

Risk register with all identified risks
Heat map visualization (probability vs impact)
Top risks with mitigation plans
Residual risk summary
Monitoring recommendations

---name: risk-assessmentdescription: Risk identification and analysis frameworks for technology decisions---# Risk Assessment Skill## ObjectivesProvide structured methodology for identifying and analyzing risks:- Systematic risk identification- Impact and probability assessment- Mitigation strategy development## Risk Categories### Technical Risks| Risk Type | Examples | Indicators ||-----------|----------|------------|| Performance | Latency, throughput issues | Benchmark gaps, load test failures || Scalability | Growth limitations | Architecture constraints, bottlenecks || Reliability | System failures, data loss | SPOF, recovery gaps || Security | Vulnerabilities, breaches | CVEs, compliance gaps || Integration | API incompatibilities | Version conflicts, protocol mismatches |### Implementation Risks| Risk Type | Examples | Indicators ||-----------|----------|------------|| Timeline | Delays, scope creep | Complexity underestimation || Resource | Skill gaps, turnover | Training needs, market scarcity || Quality | Technical debt, bugs | Code coverage gaps, review failures || Dependency | Third-party failures | Vendor instability, EOL products |### Business Risks| Risk Type | Examples | Indicators ||-----------|----------|------------|| Financial | Budget overrun, hidden costs | Incomplete TCO analysis || Strategic | Lock-in, obsolescence | Single vendor dependency || Operational | Downtime, productivity loss | Change management gaps || Compliance | Regulatory violations | Certification requirements |## Risk Assessment Matrix### Probability Scale| Level | Description | Likelihood ||-------|-------------|------------|| 5 | Almost Certain | >90% || 4 | Likely | 60-90% || 3 | Possible | 30-60% || 2 | Unlikely | 10-30% || 1 | Rare | <10% |### Impact Scale| Level | Description | Effect ||-------|-------------|--------|| 5 | Critical | Project failure, major loss || 4 | Major | Significant delay, budget overrun || 3 | Moderate | Notable impact, recoverable || 2 | Minor | Limited impact, easily managed || 1 | Negligible | Minimal impact |### Risk Score = Probability × Impact| Score | Priority | Action ||-------|----------|--------|| 15-25 | Critical | Immediate mitigation required || 8-14 | High | Mitigation plan essential || 4-7 | Medium | Monitor and plan contingency || 1-3 | Low | Accept and monitor |## Mitigation Strategies### Strategy Types1. **Avoid**: Eliminate the risk source2. **Transfer**: Shift risk to third party (insurance, contracts)3. **Mitigate**: Reduce probability or impact4. **Accept**: Acknowledge and prepare contingency### Mitigation Plan Template```markdown## Risk: [Risk Name]**Category**: [Technical/Implementation/Business]**Probability**: [1-5]**Impact**: [1-5]**Risk Score**: [P × I]### Description[Detailed risk description]### Root Cause[What causes this risk]### Impact Analysis- Best case: [Outcome]- Most likely: [Outcome]- Worst case: [Outcome]### Mitigation Strategy- Strategy type: [Avoid/Transfer/Mitigate/Accept]- Actions: 1. [Action 1] 2. [Action 2]- Cost: [Mitigation cost]### Contingency Plan[What to do if risk occurs]### Monitoring- Trigger indicators: [Warning signs]- Review frequency: [Weekly/Monthly]```## Output SpecificationRisk assessments should include:- Risk register with all identified risks- Heat map visualization (probability vs impact)- Top risks with mitigation plans- Residual risk summary- Monitoring recommendations

Frequently asked questions