risk-management
Skill0 starsChanged 6 days agoMITView on GitHub
Identify, analyse, respond to, and monitor project risks. Use when the task mentions risk, risk register, risk assessment, probability/impact, mitigation, contingency, issues that might arise, or "what could go wrong" — and for near-term risk reviews (what might crystallise in the next few weeks). PMI Knowledge Area: Risk.
17 other projects use a version of this.
Adopted by
Most recently taken up by
- grace-method/grace-plugintheir own version, first seen Oct 25, 2026
- peterbamuhigire/proposal-skillstheir own version, first seen Oct 17, 2026
- nimadorostkar/Claude-Skills-collectiontheir own version, first seen Oct 13, 2026
- IngAs8/ClaudeSkilltheir own version, first seen Sep 28, 2026
- aws-solutions/konductortheir own version, first seen Sep 23, 2026
- Serennity007/claude-trading-skills-67their own version, first seen Aug 25, 2026
Used with
Projects with it also use market-microstructure and sentiment-analysis.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
agiprolabsSkillmarket-microstructure
DEX orderflow analysis, trade classification, buyer/seller pressure, and microstructure signals for Solana tokens
Also in 3 projects that use this
MicrosoftSkillsentiment-analysis
Use when a director of product asks for the fictional sentiment split and recent excerpts.
Also in 3 projects that use this
Other versions17 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 17
- vivy-yi/xiaohongshu-skills★ 455same name
- agiprolabs/claude-trading-skills★ 366same name
- travisjneuman/.claude★ 106same name
- nimadorostkar/Claude-Skills-collection★ 37same name
- abinauv/business-consulting★ 28same name
- aws-solutions/konductor★ 12same name
- peterbamuhigire/proposal-skills★ 11same name
- Dragoon0x/product-skills★ 4same name
- gokulsvision/crewm8-cfo-skills★ 2same name
- lexbeam-software/eu-ai-governance-plugin★ 2same name
7 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository6 other files it gives its agents.
- .claude/CLAUDE.mdCLAUDE.md
- agile-deliverySkill
- change-controlSkill
- pmi-project-managementSkill
- stakeholder-managementSkill
- status-reportingSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 15 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Follow the four-step PMI cycle:
- Distinctive: line 16
Use one scale throughout a register.
- Very specific: line 21
Use the template at ${CLAUDE_PLUGIN_ROOT}/.claude/skills/pmi-project-management/templates/risk-register.md.
- Very specific: line 22
When a register already exists, update it in place: keep IDs, change status rather than deleting rows.
“Common” is measured: kept by at least 6 in 10 of the 15 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Risk Management
Follow the four-step PMI cycle:
- Identify across categories (technical, schedule, cost, resource, external, regulatory, organisational, stakeholder). Capture both threats and opportunities. Phrase each as cause → event → effect so it is testable.
- Analyse — Probability × Impact → Severity, using the Risk scoring scale in the project context or, if none is set, the 1–5 scale and severity bands in the template. Use one scale throughout a register. Note the objective threatened.
- Respond — Threats: Avoid/Mitigate/Transfer/Accept. Opportunities: Exploit/Enhance/Share/Accept. Give a concrete action and an owner.
- Monitor — an early-warning indicator per top risk and a review cadence.
Use the template at ${CLAUDE_PLUGIN_ROOT}/.claude/skills/pmi-project-management/templates/risk-register.md.
When a register already exists, update it in place: keep IDs, change status rather than
deleting rows. A risk that has occurred becomes Realised and moves to the issue log
(docs/issue-log.md). After the first pass, actively hunt
for risks commonly missed for the project's sector/technology and list them as "Candidate
risks to confirm". Never present estimated probabilities as if measured. Draft inline; for
a fresh-eyes challenge of a saved register, use the risk-manager agent and pass it the
file path. End with "Open questions for the PM".
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

