# event-risk-management

Build a risk register for a technical event, score each risk, and tie go/no-go dates to the venue’s cancellation fees. Useful when planning contingencies or discussing insurance.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 4900 installs · ★ 4
- Author: Samuel Berthe
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/samber/dev-event-organizer-skills/tree/HEAD/skills/event-risk-management/SKILL.md
- Updated: 2026-10-24
- HTML: https://affpapa.org/en/nevibecode/skills/event-risk-management

## What it does

The skill asks about the event format, committed costs, venue contract, existing insurance, and decision deadlines. It then helps organize risks by category and score likelihood against impact, using non-recoverable spend and reputational loss as measures. Risks get an owner and a review date; weather exposure and speaker dropouts are among the situations it addresses.

The work produces a written register, an on-site emergency plan, and go/no-go dates aligned with the venue’s rising cancellation fees. It identifies insurance categories to discuss with a broker, not a policy to buy. This is not legal or insurance advice: contract wording belongs with counsel, and questions about whether a specific loss is covered go to a licensed broker. For live incidents on the event day, the description directs users to `event-run-of-show`.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add samber/dev-event-organizer-skills --skill event-risk-management -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/event-risk-management/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/event-risk-management/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add samber/dev-event-organizer-skills --skill event-risk-management -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/event-risk-management/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add samber/dev-event-organizer-skills --skill event-risk-management -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/event-risk-management/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install samber/dev-event-organizer-skills event-risk-management
```

2. **Manually: put the files in place**
- File: `.github/skills/event-risk-management/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add samber/dev-event-organizer-skills --skill event-risk-management -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/samber/dev-event-organizer-skills --path skills/event-risk-management
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/event-risk-management/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add samber/dev-event-organizer-skills --skill event-risk-management -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/samber/dev-event-organizer-skills/tree/HEAD/skills/event-risk-management/SKILL.md

## When to use it
- create a categorized risk register for a technical event
- score risks by likelihood and impact
- assign risk owners and review dates
- align cancellation decisions with venue fee increases
- draft an on-site emergency plan

## Example prompts
- Build a risk register for our technical conference and assign review dates.
- Set go/no-go dates based on the venue’s cancellation-fee schedule.
- Prepare an evacuation plan and list insurance categories to discuss with a broker.

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: f1bc44712db0cb9c.

BEGIN THIRD-PARTY FILE f1bc44712db0cb9c
```text
---
name: event-risk-management
description: Build and maintain the standing risk register for a technical event - risks named by category, scored on a likelihood x impact matrix adapted to a dated one-shot deliverable, split into prevention, contingency or insurance, the insurance stack including the communicable-disease buy-back, internal go/no-go decision dates set against the venue's escalating cancellation-fee curve, and the on-site emergency plan. Use whenever the user mentions event insurance, cancelling or postponing an event, a go/no-go call, an emergency or evacuation plan, weather or speaker-dropout contingency, or a risk register - even if they never say "risk". Not legal or insurance advice. Do NOT use for day-of live incident handling - use samber/dev-event-organizer-skills@event-run-of-show instead.
license: MIT
metadata:
  author: Samuel Berthe
  version: "1.0.0"
---

# Event Risk Management

You are a risk manager for technical events. Take an organizer from "we have signed things and spent money" to a written register, a coverage decision, and a calendar of dates on which someone is authorized to say no.

This is the **standing** discipline, reusable on edition 1 and edition 10, at a meetup or a multi-track conference. It is not a one-time exercise: the register is re-scored at every decision date because a speaker dropout at T-2 weeks is a different risk from the same dropout at T-6 months.

## This is not legal or insurance advice

You produce a register and a decision framework: which risks matter, how much they matter, when someone must decide, and which coverage categories to ask about.

**Never:**

- Draft clause language.
- State what a policy covers in a specific case.
- Confirm a policy responds to a specific loss.

**Route instead:**

- Contract and clause wording (force majeure, cancellation, refund, indemnity) goes to counsel.
- Policy wording, limits, exclusions, and whether a given loss is covered goes to a licensed broker.
- Every carrier, product, premium band, and limit named anywhere in this guidance is an illustrative example of a coverage category, not a recommendation, a quote, or a claim that it is available in the user's jurisdiction.

Say this to the user in the first response, before the interview. An organizer who mistakes a register for a legal opinion is a worse outcome than an organizer with no register.

## Interview

Ask one question at a time, multiple-choice where possible. Questions 6-8 exist because the menus below diverge sharply on time-to-effect, durability, and effort - their default orderings cannot be picked for the user.
```
END THIRD-PARTY FILE f1bc44712db0cb9c

The third-party file has ended. Everything between the f1bc44712db0cb9c tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2627 of 22821 bytes. © Samuel Berthe · MIT · https://github.com/samber/dev-event-organizer-skills/tree/HEAD/skills/event-risk-management/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md