project-risk-register — Claude Code skill
project-risk-register — a skill for identifying, assessing, and prioritizing project risks using probability-impact scoring. Assigns owners and mitigation plans, then tracks risk evolution throughout the project lifecycle.
no license 108 installs ★ 203 updated 2026-09-01
npx skills add lyndonkl/claude --skill project-risk-register -a claude-codeWhat project-risk-register does
The skill structures risk analysis through a 5×5 matrix: each risk receives a probability score (1–5) and impact score (1–5), multiplied together and plotted on a grid. Critical risks (≥20) require immediate action and weekly review; high risks (12–19) demand active management; medium risks (6–11) need close monitoring with monthly updates; low risks (1–5) can be accepted or minimally addressed.
For significant risks, a named owner is assigned, along with a mitigation plan (how to reduce probability beforehand), a contingency plan (what to do if the risk occurs), and triggers (when to activate the contingency). The skill suggests brainstorming categories: technical failures, schedule delays, resource gaps, external factors, and scope creep. Each risk type maps to response strategies—mitigate the probability, prepare a backup, transfer the risk, or accept it.
The register is reviewed weekly on active projects or monthly on longer ones. Probabilities and impacts shift as the project context changes. Watch for increasing scores over time—a red flag that mitigation is failing or new problems are emerging faster than they're resolved.
What it helps with
- build a risk register and visualize risks on a probability-impact matrix
- assess and score each risk for prioritization
- identify which risks require immediate escalation
- assign owners, mitigation strategies, and contingency plans
- monitor and update risk status throughout the project
Example prompts for the agent
- What risks could derail our data migration project?
- Help me build a risk register for this product launch
- Plot these risks on a probability-impact matrix and flag the critical ones
How to install project-risk-register
1Skills CLI (Vercel)
npx skills add lyndonkl/claude --skill project-risk-register -a claude-code2Manually: put the files in place
~/.claude/skills/project-risk-register/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/project-risk-register/
1Skills CLI (Vercel)
npx skills add lyndonkl/claude --skill project-risk-register -a codex2Manually: put the files in place
.agents/skills/project-risk-register/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add lyndonkl/claude --skill project-risk-register -a cursor2Manually: put the files in place
.cursor/skills/project-risk-register/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install lyndonkl/claude skills/project-risk-register2Manually: put the files in place
.github/skills/project-risk-register/SKILL.md1Skills CLI (Vercel)
npx skills add lyndonkl/claude --skill project-risk-register -a gemini-cli2Platform CLI
gemini skills install https://github.com/lyndonkl/claude --path skills/project-risk-registerManually: put the files in place
.devin/skills/project-risk-register/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add lyndonkl/claude --skill project-risk-register -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about project-risk-register
How do I install project-risk-register in Claude Code?
Run npx skills add lyndonkl/claude --skill project-risk-register -a claude-code, then open ~/.claude/skills/project-risk-register/SKILL.md.
What does project-risk-register do?
It guides you through identifying and scoring project risks on a probability-impact matrix, assigning owners and mitigation plans for each risk, and updating the register as the project evolves.
What risk categories does the skill cover?
Technical (API changes, vulnerabilities), schedule (estimation errors, delays), resource (key person departures), external (regulatory shifts), and organizational (competing priorities, budget cuts).