risk-assessment
Skill1 starsChanged 7 months agoMITView on GitHub
Identify, assess, and plan mitigations for operational risks using a risk register with likelihood and impact scoring. Use when evaluating risks for a project, vendor, process, or decision. Trigger with "risk assessment", "what are the risks", "risk register", "what could go wrong", or "evaluate risks".
19 other projects use a version of this.
Adopted by
Most recently taken up by
- staskh/trading_skillstheir own version, first seen Nov 8, 2026
- s977043/PlanGatetheir own version, first seen Nov 2, 2026
- Big-LAORE/Biblioth-que-de-skillstheir own version, first seen Nov 1, 2026
- PaulDanielYoung/internal-audit-skillstheir own version, first seen Nov 1, 2026
- artherahq/skillstheir own version, first seen Oct 31, 2026
- artheras/skillstheir own version, first seen Oct 31, 2026
Other versions19 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 19
- anthropics/knowledge-work-plugins★ 36ksame name
- staskh/trading_skills★ 411same name
- GAJETOso/financeskills★ 47same name
- DefiLlama/defillama-skills★ 32same name
- ishenli/investment-agent★ 10same name
- microsoft/aibast-agents-library★ 8same name
- RiskResponse/ciso-security-skills★ 8same name
- artherahq/skills★ 3same name
- artheras/skills★ 3same name
- s977043/PlanGate★ 3same name
9 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 repository164 other files it gives its agents.
- instrument-data-to-allotropeSkill
- literature-reviewSkill
- nextflow-developmentSkill
- scientific-problem-selectionSkill
- scvi-toolsSkill
- single-cell-rna-qcSkill
- discover-brandSkill
- enforce-voiceSkill
- generate-guidelinesSkill
- csat-reportSkill
- customer-escalationSkill
- customer-researchSkill
- draft-responseSkill
- kb-articleSkill
- sentiment-analysisSkill
- ticket-triageSkill
- analyzeSkill
- build-dashboardSkill
- create-vizSkill
- data-context-extractorSkill
- data-modelingSkill
- data-pipelineSkill
- etl-designSkill
- explore-dataSkill
- sql-queriesSkill
- statistical-analysisSkill
- validate-dataSkill
- write-querySkill
- accessibility-reviewSkill
- component-librarySkill
- design-critiqueSkill
- design-handoffSkill
- design-systemSkill
- frontend-designSkill
- research-synthesisSkill
- user-researchSkill
- ux-copySkill
- wireframingSkill
- Agent DevelopmentSkill
- CLAUDE.md ManagementSkill
- MCP Server BuilderSkill
- Plugin DevelopmentSkill
- Prompt EngineeringSkill
- Skill CreatorSkill
- curriculum-designSkill
- lesson-planningSkill
- quiz-generatorSkill
- study-guideSkill
- tutoringSkill
- api-designSkill
- architectureSkill
- ci-cd-pipelineSkill
- code-reviewSkill
- database-migrationSkill
- debugSkill
- dependency-auditSkill
- deploy-checklistSkill
- documentationSkill
- error-handlingSkill
- git-workflowSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 13 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 92
Do not score all risks as medium -- if every risk is the same score, the assessment is not useful.
- Distinctive: line 94
When presenting to leadership, focus on critical and high risks with specific recommendations.
“Common” is measured: kept by at least 6 in 10 of the 13 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
Operational Risk Assessment
Identify, score, and mitigate operational risks. Maintain a risk register with likelihood/impact scoring.
Workflow
Step 1: Identify Risks
Enumerate across categories: operational (process failures, supplier disruptions), financial (budget, revenue), technical (system failures, scalability), people (key person, attrition, skill gaps), compliance (regulatory, audit), reputational (customer/media impact), external (market, competitor, economic). Use brainstorming, historical incidents, assumption analysis, and industry benchmarks.
Step 2: Score
- Likelihood: 1 (Rare <10%) to 5 (Almost certain >75%)
- Impact: 1 (Negligible) to 5 (Catastrophic)
- Risk score = Likelihood x Impact (1-25)
Step 3: Classify
- Critical (16-25): Immediate executive attention.
- High (10-15): Mitigation plan with assigned owner.
- Medium (5-9): Monitor and mitigate where cost-effective.
- Low (1-4): Accept and review periodically.
Step 4: Plan Mitigations
For each Medium+: avoid (eliminate), mitigate (reduce likelihood/impact), transfer (insurance, contract), or accept (monitor). Document action, owner, deadline, expected reduction, and residual risk.
Step 5: Build Risk Register
Output Format
## Risk Assessment
**Subject**: [Project/process/vendor] | **Date**: [YYYY-MM-DD]
**Overall Posture**: [LOW / MEDIUM / HIGH / CRITICAL]
### Risk Heat Map
| | Impact 1 | Impact 2 | Impact 3 | Impact 4 | Impact 5 |
|Likelihood 5 | | | | R-003 | |
|Likelihood 3 | | | R-002 | | |
|Likelihood 1 | R-006 | | | | |
### Risk Register
| ID | Risk | Category | L | I | Score | Rating | Response | Owner |
|----|------|----------|---|---|-------|--------|----------|-------|
| R-001 | [Risk] | Operational | 4 | 4 | 16 | CRITICAL | Mitigate | [Name] |
### Mitigation Plans
**R-001**: [Risk name] -- CRITICAL
- Mitigation: [Action] | Owner: [Name] | Deadline: [Date]
- Residual risk: L=[X] I=[X] Score=[X]
### Monitoring
| Risk ID | Indicator | Trigger Level | Review Frequency |
|---------|-----------|---------------|------------------|Examples
User: "What are the risks of migrating to the new CRM?" Action: Identify risks across technical, operational, financial, and schedule categories. Score each, build mitigation plan.
User: "Assess our single-vendor dependency on CloudCo" Action: Evaluate outage impact, price exposure, data portability, financial stability, and lock-in. Recommend diversification or contract protections.
Best Practices
- Include diverse stakeholders in risk identification to cover blind spots.
- Score based on impact if the risk occurs, not expectation of occurrence.
- Review monthly for active projects, quarterly for ongoing operations.
- Do not score all risks as medium -- if every risk is the same score, the assessment is not useful.
- Assign owners who have authority and resources to act.
- When presenting to leadership, focus on critical and high risks with specific recommendations.
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.

