risk-register
Skill2 starsChanged 8 months agoMITView on GitHub
Creates and maintains risk registers with impact/probability matrices, mitigation plans, and risk owner assignments for startup operations.
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
1
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 103
Create structured risk registers
“Common” is measured: kept by at least 6 in 10 of the 6 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 Register - Startup Risk Management
Overview
Identifies, assesses, and tracks risks before they become crises. Startups that manage risk proactively survive longer.
1. When to Apply
| Trigger | Behavior |
| Quarterly review | Full risk assessment |
| "risk", "리스크" | Risk register creation/update |
| Major decision | Decision-specific risk analysis |
| Incident occurred | Add to risk register with lessons |
2. Risk Register Template
# Risk Register — [Date]
| ID | Risk | Category | Probability | Impact | Score | Owner | Status |
|----|------|----------|-------------|--------|-------|-------|--------|
| R1 | [Description] | [Cat] | H/M/L | H/M/L | [N] | @name | Open |
| R2 | [Description] | [Cat] | H/M/L | H/M/L | [N] | @name | Mitigated |
## Risk Detail: R1 — [Risk Name]
- **Description**: [What could go wrong]
- **Trigger**: [What would cause this to happen]
- **Probability**: High (>70%) / Medium (30-70%) / Low (<30%)
- **Impact**: High (existential) / Medium (significant) / Low (manageable)
- **Mitigation Plan**: [What we're doing to reduce probability/impact]
- **Contingency Plan**: [What we'll do IF it happens]
- **Owner**: @[name]
- **Review Date**: [When to reassess]3. Common Startup Risks
| Category | Risk | Typical Probability |
| Financial | Runway runs out before next raise | High |
| Financial | Key customer churns | Medium |
| Technical | Major security breach | Low but catastrophic |
| Technical | Key infrastructure failure | Medium |
| People | Co-founder departure | Medium |
| People | Key engineer leaves | Medium |
| Market | Competitor launches similar product | High |
| Market | Market shifts (regulation, trends) | Medium |
| Legal | IP dispute | Low |
| Legal | Compliance violation | Medium |
| Operational | Vendor/partner dependency fails | Medium |
4. Risk Matrix
Impact → Low Medium High
Probability
High | 🟡 Medium | 🟠 High | 🔴 Critical |
Medium | 🟢 Low | 🟡 Medium | 🟠 High |
Low | 🟢 Low | 🟢 Low | 🟡 Medium |Scoring: H=3, M=2, L=1 → Score = Probability × Impact (1-9)
5. Tool Coordination
| Tool | Purpose |
| Write | Generate risk register |
| Read | Reference previous risk assessments |
6. Boundaries
Will:
- Create structured risk registers
- Assess probability and impact
- Suggest mitigation and contingency plans
- Track risk status over time
Will Not:
- Predict the future with certainty
- Make risk acceptance decisions for you
- Provide insurance or legal advice
- Replace professional risk consultants for regulated industries
Other versions8 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 8
- microsoft/hve-core★ 1.6ksame name
- MRCalderon3D/everything-game-dev-code★ 91same name
- zbruhnke/claude-code-starter★ 16same name
- Vaibhavkkm/vkkm-aegis-plugin★ 2same name
- kaandgnsh/Claude-Blue★ 1same name
- aakash-dhar/claude-skills★ 0same name
- kenmulford/PMSkills★ 0same name
- lzx-Bill/Project-Factory-Core★ 0same name
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 repository28 other files it gives its agents.
- brand-voiceSkill
- community-builderSkill
- email-sequenceSkill
- growth-experimentSkill
- landing-page-genSkill
- pitch-deckSkill
- referral-programSkill
- budget-plannerSkill
- fundraising-prepSkill
- legal-checklistSkill
- meeting-notesSkill
- okr-builderSkill
- postmortem-writerSkill
- retrospective-guideSkill
- sop-writerSkill
- experiment-designerSkill
- metrics-trackerSkill
- prd-writerSkill
- scope-cutterSkill
- user-interview-guideSkill
- ai-integrationSkill
- api-first-designSkill
- db-schema-designerSkill
- deploy-pipelineSkill
- infra-as-codeSkill
- monitoring-setupSkill
- mvp-scaffoldSkill
- test-generatorSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.

