agentleFS
elvismuslielvismusli/business-validator/skills/risk-assessment/SKILL.md

risk-assessment

Skill1 starsChanged 9 months agoMITView on GitHub

Use after all research skills to synthesize SWOT analysis, risk evaluation, and mitigation strategies — requires run_id and all prior sections

19 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 13 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If any file is missing, stop and inform the user which skill needs to run first.

    line 19
  2. Distinctive:

    All four files listed above

    line 25
  3. Distinctive:

    Read all files using the exact run_id.

    line 54
  4. Very specific:

    Ensure the output directory exists: mkdir -p docs/reports/<run_id>

    line 76

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Risk Assessment

Overview

Synthesize all prior research (market, competitors, financials) into a SWOT analysis and detailed risk assessment with mitigation strategies.

<HARD-GATE> You MUST read ALL prior sections before writing the risk assessment. This skill synthesizes — it does not research independently. Required inputs (all using exact run_id): - `docs/business-briefs/<run_id>.md` - `docs/reports/<run_id>/01-market-research.md` - `docs/reports/<run_id>/02-competitor-analysis.md` - `docs/reports/<run_id>/03-financial-model.md`

If any file is missing, stop and inform the user which skill needs to run first. </HARD-GATE>

Inputs

  • run_id: From idea-intake (format: YYYY-MM-DD-<slug>-<hhmm>)
  • All four files listed above

Output

  • File: docs/reports/<run_id>/04-risk-assessment.md

Process

digraph risk_assessment {
    "Verify run_id and all inputs exist" [shape=box];
    "Read all prior sections" [shape=box];
    "Build SWOT matrix" [shape=box];
    "Identify key risks" [shape=box];
    "Score probability and impact" [shape=box];
    "Develop mitigation strategies" [shape=box];
    "Write 04-risk-assessment.md" [shape=box, style=filled, fillcolor="#e8f5e9"];

    "Verify run_id and all inputs exist" -> "Read all prior sections";
    "Read all prior sections" -> "Build SWOT matrix";
    "Build SWOT matrix" -> "Identify key risks";
    "Identify key risks" -> "Score probability and impact";
    "Score probability and impact" -> "Develop mitigation strategies";
    "Develop mitigation strategies" -> "Write 04-risk-assessment.md";
}

Step 1: Read All Prior Sections

Read all files using the exact run_id. Synthesize key findings from each.

Step 2: Build SWOT Matrix

Draw from all sources:

  • Strengths: What advantages does this idea have? (unique features, team, timing)
  • Weaknesses: What internal factors work against it? (resources, experience, gaps)
  • Opportunities: What external factors favor it? (trends, gaps, regulation changes)
  • Threats: What external factors endanger it? (competitors, regulation, market shifts)

Step 3: Identify and Score Risks

For each risk:

  • Category: Market / Technical / Financial / Operational / Legal
  • Probability: High / Medium / Low
  • Impact: High / Medium / Low
  • Severity: Critical / High / Medium / Low (derived from probability x impact)
  • Mitigation strategy
  • Contingency plan

Step 4: Write Output

Ensure the output directory exists: mkdir -p docs/reports/<run_id>

Save to docs/reports/<run_id>/04-risk-assessment.md:

## SWOT Analysis

**Run ID:** <run_id>

| | Helpful | Harmful |
|---|---------|---------|
| **Internal** | **Strengths** | **Weaknesses** |
| | - [S1] | - [W1] |
| | - [S2] | - [W2] |
| **External** | **Opportunities** | **Threats** |
| | - [O1] | - [T1] |
| | - [O2] | - [T2] |

## Risk Assessment

### Risk Matrix

| # | Risk | Category | Probability | Impact | Severity |
|---|------|----------|-------------|--------|----------|
| 1 | [description] | Market | High/Med/Low | High/Med/Low | Critical/High/Med/Low |
| 2 | [description] | Financial | High/Med/Low | High/Med/Low | Critical/High/Med/Low |

### Detailed Risk Analysis

#### Risk 1: [Name]
- **Description:** [what could go wrong]
- **Trigger:** [what would cause this]
- **Impact:** [consequences if it happens]
- **Mitigation:** [how to prevent or reduce]
- **Contingency:** [what to do if it happens anyway]

### Risk Summary
- **Critical risks:** X
- **High risks:** X
- **Medium risks:** X
- **Low risks:** X
- **Overall risk profile:** [Low / Moderate / High / Very High]

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.