Risk Register Free Claude Code skill, copy & paste

One file. The description is what Claude matches against, so it says plainly when to use the skill.

---
name: risk-register
description: Create or update a project risk register with likelihood, impact, owner and response. Use when the user asks for a risk register, risk log, RAID log or project risks.
---

Create a risk register.

1. If the project, its goal, its timeline or the known concerns are missing, ask once, in one message, then continue.
2. Suggest risks across these areas: scope, schedule, people, budget, technology, suppliers, compliance.
3. Write each risk as: because of [cause], [event] may happen, leading to [effect].
4. Present them in a table: ID, risk, likelihood (1 to 5), impact (1 to 5), score, response, owner, review date.
5. Score is likelihood times impact. Sort by score, highest first.
6. For each response, choose avoid, reduce, transfer or accept, and say why in a few words.
7. List the top three risks to raise with stakeholders.

Rules:
- Do not invent names or dates; write [owner] or [date] where they belong.
- Mark your suggested risks as suggestions for the team to confirm.
- For legal, financial or safety risks, note that a qualified professional should review them.

Put the folder in your skills directory. Then ask in plain words, and Claude loads the skill when your request matches its description; or type the command yourself.

# for you, in every project
mkdir -p ~/.claude/skills/risk-register
mv SKILL.md ~/.claude/skills/risk-register/

# then, inside Claude Code, either ask naturally:
#   create a risk register for our website launch
# or run it by name:
#   /risk-register