risk

Manage risk registers with YAML frontmatter in a directory structure.

Updated May 7, 2026
One-click install
npx skills add https://github.com/ChazzCoin/claude-orchestrator --skill risk-chazzcoin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: risk
Source: https://github.com/ChazzCoin/claude-orchestrator/tree/main/kit/skills/risk
Command: npx skills add https://github.com/ChazzCoin/claude-orchestrator --skill risk-chazzcoin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of identifying, managing, and tracking risks within your software stack, providing a centralized way to maintain visibility and control over potential issues.

Core Features & Use Cases

  • File New Risks: Record new risks with detailed descriptions, severity, likelihood, and owner.
  • Update Existing Risks: Update the status and details of existing risks.
  • List Open Risks: View a list of all open risks, sorted by severity and likelihood.
  • Mitigate Risks: Move risks from open to mitigated status.
  • Accept Risks: Document and accept risks without mitigation.
  • Use Case: Keep track of potential vulnerabilities in your system, prioritize them, and ensure they are addressed promptly.

Quick Start

File a new risk using the risk skill: "risk file a risk -description 'Potential security breach' -severity high -likelihood medium -affects stack-wide -owner unassigned".

Frequently Asked Questions about risk

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I track software engineering risks in a centralized register?

To track software engineering risks, you can file new entries with severity, likelihood, and owner details, list open risks sorted by priority, and update their status to mitigated or accepted within a defined directory structure.

What is the best way to document and accept a software risk without mitigation?

Documenting and accepting a software risk involves logging the issue with its description and severity, then explicitly updating its status to accepted to maintain visibility without applying immediate mitigation.

How do I file a new risk assessment for a potential security vulnerability?

You file a new risk assessment by providing a description, severity, likelihood, affected component, and owner, which creates a tracked entry to maintain control over potential system vulnerabilities.

Can I use YAML frontmatter for risk management configuration in my development environment?

Yes, risk management configuration uses YAML frontmatter within a defined directory structure, enabling software development environments to maintain stable and secure systems through tracked risk registers.

How do I list open risks sorted by severity and likelihood?

You list open risks by requesting a view of all active entries, which automatically sorts the potential issues by their assigned severity and likelihood to help prioritize mitigation efforts.