메뉴
Risk register management skill for systematic risk identification, assessment, and tracking
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/a5c-ai/babysitter --skill risk-register-manager명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
Reference for querying the Atlas knowledge graph through its MCP tools — the SECONDARY enrichment/comparison layer that adds best-practice context to systems you have ALREADY scanned from your real sources (`az`, repos, dirs). Use when you need to look up nodes, edges, kinds, clusters, stats, or wiki pages in Atlas to compare against your real inventory. (atlas graph, query atlas, atlas mcp, search the graph, graph neighbors, atlas record, atlas kinds, enrichment layer)
Atlas turns your STATED NEED into a real systems atlas by SCANNING your actual sources (Azure via `az`, git repos, local dirs) and process/data mining them, THEN enriching against the Atlas knowledge graph. Use this skill when asked to inventory/map your real systems, scan your cloud + repos + directories, mine the real processes or data they contain, or collect their real constraints/gotchas. (atlas, scan my systems, inventory our azure account, map my repos, real systems atlas, process mining, data mining, collect nuances, system discovery)
This skill should be used when the user asks to "find skills in the wild", "assimilate popular workflows", "discover SKILL.md files in repos", "research external skills", "find workflow patterns", "survey the skill landscape", "what skills exist out there", or wants to investigate public repositories for extractable processes, babysitter plugins, and reusable procedural insights. Searches GitHub for SKILL.md files, classifies repos by archetype, and maintains structured research under docs/reference-repos/.
SKILL.md 표시 중
SOC 직업 분류 기준
| name | risk-register-manager |
| description | Risk register management skill for systematic risk identification, assessment, and tracking |
| allowed-tools | ["Read","Write","Glob","Grep","Bash"] |
| metadata | {"specialization":"decision-intelligence","domain":"business","category":"risk","priority":"medium","tools-libraries":["pandas","numpy","jinja2"]} |
| graph | {"domains":["domain:business-intelligence"],"skillAreas":["skill-area:quantitative-modeling","skill-area:business-analysis","skill-area:strategic-analysis"],"roles":["role:risk-analyst","role:business-analyst","role:strategic-planner"]} |
The Risk Register Manager skill provides comprehensive capabilities for systematic risk identification, assessment, mitigation planning, and ongoing tracking. It supports the full risk management lifecycle from initial identification through monitoring and closure.
# Define a risk
risk_entry = {
"id": "RISK-001",
"title": "Key Supplier Bankruptcy",
"description": "Primary component supplier faces financial difficulties, risking supply continuity",
"category": "Supply Chain",
"subcategory": "Supplier Risk",
"identified_by": "Procurement Manager",
"identification_date": "2024-01-15",
"status": "Open",
"triggers": [
"Supplier credit rating downgrade",
"Delayed deliveries > 2 weeks",
"News of financial restructuring"
],
"affected_objectives": ["Production Continuity", "Cost Control"]
}
# Assess risk
risk_assessment = {
"risk_id": "RISK-001",
"probability": {
"score": 3, # 1-5 scale
"rationale": "Supplier shows signs of financial stress; industry downturn",
"confidence": "medium"
},
"impact": {
"financial": {"score": 4, "estimate": 2500000},
"schedule": {"score": 3, "estimate_days": 45},
"reputation": {"score": 2},
"overall": 4
},
"risk_score": 12, # P x I
"risk_level": "High",
"velocity": "Medium", # How quickly it could materialize
"assessment_date": "2024-01-20"
}
# Define mitigation strategies
mitigation_plan = {
"risk_id": "RISK-001",
"response_strategy": "Mitigate", # Accept, Mitigate, Transfer, Avoid
"actions": [
{
"id": "MIT-001-A",
"description": "Qualify secondary supplier",
"owner": "Procurement Director",
"due_date": "2024-03-01",
"status": "In Progress",
"cost": 50000,
"effectiveness": 0.6 # Expected risk reduction
},
{
"id": "MIT-001-B",
"description": "Increase safety stock to 8 weeks",
"owner": "Supply Chain Manager",
"due_date": "2024-02-15",
"status": "Not Started",
"cost": 200000,
"effectiveness": 0.3
}
],
"residual_probability": 2,
"residual_impact": 3,
"residual_score": 6
}
# Configure risk matrix
matrix_config = {
"probability_scale": {
1: {"label": "Rare", "range": "< 10%"},
2: {"label": "Unlikely", "range": "10-25%"},
3: {"label": "Possible", "range": "25-50%"},
4: {"label": "Likely", "range": "50-75%"},
5: {"label": "Almost Certain", "range": "> 75%"}
},
"impact_scale": {
1: {"label": "Negligible", "financial": "< $10K"},
2: {"label": "Minor", "financial": "$10K - $100K"},
3: {"label": "Moderate", "financial": "$100K - $1M"},
4: {"label": "Major", "financial": "$1M - $10M"},
5: {"label": "Severe", "financial": "> $10M"}
},
"risk_levels": {
"Low": {"range": [1, 4], "color": "green"},
"Medium": {"range": [5, 9], "color": "yellow"},
"High": {"range": [10, 16], "color": "orange"},
"Critical": {"range": [17, 25], "color": "red"}
}
}
{
"operation": "create|update|assess|report",
"risk": {
"id": "string",
"title": "string",
"description": "string",
"category": "string"
},
"assessment": {
"probability": "object",
"impact": "object"
},
"mitigation": {
"strategy": "string",
"actions": ["object"]
},
"report_options": {
"format": "matrix|list|dashboard",
"filters": "object"
}
}
{
"risk_register": [
{
"id": "string",
"title": "string",
"category": "string",
"inherent_score": "number",
"residual_score": "number",
"status": "string",
"owner": "string",
"next_review": "string"
}
],
"summary_statistics": {
"total_risks": "number",
"by_level": "object",
"by_category": "object",
"trend": "object"
},
"risk_matrix": "object",
"top_risks": ["object"],
"overdue_mitigations": ["object"],
"report_path": "string"
}
| Strategy | When to Use | Example |
|---|---|---|
| Avoid | High P, High I, feasible to eliminate | Cancel risky project phase |
| Mitigate | Reduce P or I is cost-effective | Add quality controls |
| Transfer | Impact can be shifted | Insurance, contracts |
| Accept | Low priority or unavoidable | Budget contingency |