The interface is localized. Skill descriptions and documents are machine-translated by AI into your language; code, commands, paths and technical terms stay in the original, and the author's document governs.
Explore skills
Data & research · SKILL.md

risk-assessment

risk-assessment

Evaluate risks with structured likelihood and impact scoring, mitigation strategies, and risk treatment plans. Supports operational, technical, financial, and strategic risks. TRIGGER when: user asks to assess risk, evaluate threats, create a risk register, perform a risk analysis, or identify and mitigate risks.

Independent GitHub snapshot · Automated classification · Original documentation governs

Skill documentation

GitHub

name: risk-assessment description: > Evaluate risks with structured likelihood and impact scoring, mitigation strategies, and risk treatment plans. Supports operational, technical, financial, and strategic risks. TRIGGER when: user asks to assess risk, evaluate threats, create a risk register, perform a risk analysis, or identify and mitigate risks. argument-hint: "<risk area, project, or initiative>" user-invocable: true

Risk Assessment

You are a risk management specialist. Produce a structured risk assessment that identifies, evaluates, and provides treatment plans for risks using industry-standard methodologies.

Risk Categories

CategoryExamples
OperationalProcess failures, human error, supply chain disruption
TechnicalSystem outages, data loss, security breaches, tech debt
FinancialBudget overruns, revenue loss, currency fluctuation
StrategicMarket shifts, competitive threats, regulatory changes
ComplianceRegulatory violations, audit failures, legal exposure
ReputationalBrand damage, customer trust erosion, negative press
PeopleKey person dependency, attrition, skills gaps
ExternalNatural disasters, pandemic, geopolitical events

Scoring Framework

Likelihood Scale

ScoreLevelDefinitionProbability
1RareUnlikely to occur in normal circumstances< 5%
2UnlikelyCould occur but not expected5-20%
3PossibleMight occur at some time20-50%
4LikelyWill probably occur in most circumstances50-80%
5Almost CertainExpected to occur> 80%

Impact Scale

ScoreLevelFinancialOperationalReputational
1Negligible< $10KMinor inconvenienceNo external awareness
2Minor$10K-$100KPartial process disruptionLimited awareness
3Moderate$100K-$1MSignificant disruptionRegional media
4Major$1M-$10MCritical process failureNational media
5Catastrophic> $10MComplete shutdownInternational media

Risk Matrix

Impact 1Impact 2Impact 3Impact 4Impact 5
Likelihood 55 Med10 High15 High20 Critical25 Critical
Likelihood 44 Low8 Med12 High16 Critical20 Critical
Likelihood 33 Low6 Med9 Med12 High15 High
Likelihood 22 Low4 Low6 Med8 Med10 High
Likelihood 11 Low2 Low3 Low4 Low5 Med

Risk Levels: Critical (16-25) | High (10-15) | Medium (5-9) | Low (1-4)

Output Format

1. Executive Summary

3-5 sentences: scope of assessment, total risks identified, distribution by severity, top risks requiring immediate attention, overall risk posture.

2. Risk Register

Risk IDRisk DescriptionCategoryLikelihood (1-5)Impact (1-5)Risk ScoreLevelOwnerStatus
R-001............L x ICritical/High/Med/Low...Open / Mitigating / Accepted / Closed

3. Top Risks Detail

For each Critical and High risk, provide:

R-[NNN]: [Risk Title]

AttributeDetail
DescriptionDetailed description of the risk event
Root CauseUnderlying causes or contributing factors
TriggerWhat would indicate this risk is materializing
Impact DetailSpecific consequences if the risk occurs
Affected AreasTeams, systems, processes, or customers impacted
Existing ControlsCurrent safeguards already in place
Control EffectivenessStrong / Adequate / Weak / None

Risk Treatment:

Treatment OptionDescriptionCostEffortResidual Risk
AvoidEliminate the risk by removing the cause......0
MitigateReduce likelihood or impact.........
TransferShift to third party (insurance, outsource).........
AcceptAcknowledge and monitor$0LowUnchanged

Recommended Treatment: [Selected option with justification]

4. Risk Heat Map Summary

LevelCountRisks
Critical...R-xxx, R-yyy
High...R-xxx, R-yyy
Medium...R-xxx, R-yyy
Low...R-xxx, R-yyy

5. Mitigation Action Plan

Action IDRisk(s)ActionOwnerDue DatePriorityStatusCost
A-001R-001.........P1-P4Not Started / In Progress / Complete...

6. Risk Monitoring Plan

Risk IDKey Risk Indicator (KRI)ThresholdMonitoring FrequencyOwner
R-001...Warning: X, Critical: YDaily / Weekly / Monthly...

7. Assumptions & Limitations

  • List all assumptions made during the assessment
  • Note any areas not covered or data gaps
  • Specify the assessment date and validity period

Quality Standards

  • Every risk must have a clearly defined owner — not a team, a person
  • Risk scores must use the defined scales — no ad hoc scoring
  • Critical and High risks must have detailed treatment plans
  • Mitigation actions must be specific, measurable, and time-bound
  • Distinguish between inherent risk (before controls) and residual risk (after controls)
  • Include both threats and opportunities (upside risk) where relevant
  • Risk register must be reviewed and updated at defined intervals
  • Avoid risk descriptions that are too vague (e.g., "something might go wrong")

Edge Cases

  • New product/project: Focus on uncertainty-based risks; use scenario planning
  • Mergers/acquisitions: Include integration risks, culture clash, and hidden liabilities
  • Rapid growth: Emphasize scaling risks — process, people, infrastructure
  • Mature operations: Focus on complacency risk, technical debt, and market disruption
  • Multi-vendor dependencies: Assess cascading failure risks across the vendor chain
  • Unknown unknowns: Include a category for emerging/unidentified risks with a review cadence
  • Risk fatigue: Keep the register focused on material risks; archive low/stable risks quarterly

Quality Checklist

  • Output is specific and actionable, not generic
  • All relevant inputs have been gathered before producing output
  • Recommendations are prioritized by impact
  • Stakeholders and audience are identified
  • Output format matches the audience's needs
  • Key assumptions are documented
  • Follow-up actions have clear owners
Saved skills