PluginBench
Skill
Official
Review
Audit score 70

risk-assessment

anthropics/knowledge-work-plugins

Systematically identify, assess, and mitigate operational risks across projects, vendors, and decisions.

What is risk-assessment?

Identifies and evaluates operational risks using a structured matrix approach, categorizing them by likelihood and impact. Use this when assessing risks for projects, vendors, processes, or decisions, or when asked directly about potential problems.

  • Categorizes risks across six domains: operational, financial, compliance, strategic, reputational, and security
  • Applies a likelihood-impact matrix to determine risk level (Critical, High, Medium, Low)
  • Documents each risk with description, likelihood, impact, mitigation strategy, owner, and status
  • Prioritizes risks by severity to focus mitigation efforts
  • Produces a structured risk register for tracking and accountability

How to install risk-assessment

npx skills add https://github.com/anthropics/knowledge-work-plugins --skill risk-assessment
Claude Code
Cursor
Windsurf
Cline

How to use risk-assessment

  1. 1.Describe the project, process, vendor, or decision you want to assess for risks
  2. 2.Provide relevant context such as scope, timeline, dependencies, or stakeholders
  3. 3.Review the generated risk register organized by likelihood and impact
  4. 4.Prioritize risks marked as Critical or High for immediate mitigation planning
  5. 5.Assign owners to each risk and define specific mitigation actions
  6. 6.Track risk status (Open, Mitigated, Accepted, Closed) over time

Use cases

Good for
  • Evaluating risks before launching a new project or initiative
  • Assessing vendor or third-party risks during procurement or partnership decisions
  • Identifying process vulnerabilities in existing operations
  • Conducting risk reviews for compliance or audit purposes
  • Planning mitigation strategies for known threats
Who it's for
  • Project managers and program leads
  • Risk and compliance officers
  • Business analysts evaluating decisions
  • Operations and process owners
  • Executive stakeholders planning mitigation budgets

risk-assessment FAQ

What triggers this skill?

Use it when you ask 'what are the risks', 'risk assessment', 'risk register', 'what could go wrong', or when evaluating risks for a project, vendor, process, or decision.

How are risks prioritized?

Risks are prioritized using a likelihood-impact matrix. High likelihood + high impact = Critical; combinations are rated Critical, High, Medium, or Low.

What should I do with accepted risks?

Document them in the risk register with status 'Accepted' and ensure stakeholders understand the decision. Monitor them periodically for changes in likelihood or impact.

Who should own each risk?

Assign ownership to someone with authority and visibility over the risk area—typically a process owner, project lead, or functional manager.

How often should I update the risk register?

Review and update the register at project milestones, when circumstances change, or on a regular cadence (monthly/quarterly) depending on project duration and volatility.

Full instructions (SKILL.md)

Source of truth, from anthropics/knowledge-work-plugins.


name: risk-assessment description: Identify, assess, and mitigate operational risks. Trigger with "what are the risks", "risk assessment", "risk register", "what could go wrong", or when the user is evaluating risks associated with a project, vendor, process, or decision.

Risk Assessment

Systematically identify, assess, and plan mitigations for operational risks.

Risk Assessment Matrix

Low ImpactMedium ImpactHigh Impact
High LikelihoodMediumHighCritical
Medium LikelihoodLowMediumHigh
Low LikelihoodLowLowMedium

Risk Categories

  • Operational: Process failures, staffing gaps, system outages
  • Financial: Budget overruns, vendor cost increases, revenue impact
  • Compliance: Regulatory violations, audit findings, policy breaches
  • Strategic: Market changes, competitive threats, technology shifts
  • Reputational: Customer impact, public perception, partner relationships
  • Security: Data breaches, access control failures, third-party vulnerabilities

Risk Register Format

For each risk, document:

  • Description: What could happen
  • Likelihood: High / Medium / Low
  • Impact: High / Medium / Low
  • Risk Level: Critical / High / Medium / Low
  • Mitigation: What we're doing to reduce likelihood or impact
  • Owner: Who is responsible for managing this risk
  • Status: Open / Mitigated / Accepted / Closed

Output

Produce a prioritized risk register with specific, actionable mitigations. Focus on risks that are controllable and material.