New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Event Safety Plan

by mohitagw15856 in mohitagw15856/pm-claude-skills

Produce the event safety documentation that satisfies a venue or licensing authority and actually works on the day — the risk assessment, crowd and capacity plan, emergency procedures, and the roles…

MITAuto-check passed

Install Event Safety Plan

skills CLI
$ npx skills add mohitagw15856/pm-claude-skills --skill event-safety-plan -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mohitagw15856/pm-claude-skills event-safety-plan --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/event-safety-plan .claude/skills/event-safety-plan && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
event-safety-plan
GitHub stars
1.4k
Token cost
~1.7k tokens
SKILL.md length
837 words
Files
1
Skills in repo
1,348
Repo updated
First seen
Licence
MIT

At a glance

Produce the event safety documentation that satisfies a venue or licensing authority and actually works on the day — the risk assessment, crowd and capacity plan, emergency procedures, and the roles…

  • Works in 7 steps: Assess this event, not events in… → Every control gets a named owner and a… → Establish capacity and its basis. Not a… → …
  • Asked to write an event risk assessment
  • SKILL.md covers What This Skill Produces, Required Inputs, Framework: Specific Hazards,… and Output Format, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Event Safety Plan is an agent skill from mohitagw15856/pm-claude-skills. Produce the event safety documentation that satisfies a venue or licensing authority and actually works on the day — the risk assessment, crowd and capacity plan, emergency procedures, and the roles that must be filled. Use when asked to write an event risk assessment, safety plan, event management plan, or emergency procedure, or when a venue or authority has requested safety documentation. Produces the risk assessment, the crowd and capacity position, emergency and evacuation procedures, the medical and welfare…

Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.

When your agent uses it

  • Asked to write an event risk assessment
  • Event management plan
  • Emergency procedure
  • Authority has requested safety documentation

Example prompts

  • “/event-safety-plan”

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. Assess this event, not events in general. A downloaded template with 'slips, trips and falls' is evidence of nothing. The hazards that…
  2. Every control gets a named owner and a check time. A control nobody owns is a sentence in a document.
  3. Establish capacity and its basis. Not a number you were told — the basis: exit capacity, floor area, or the venue's certificate. Then…
  4. Write the emergency procedure for a frightened person. Short, numbered, plain. Who calls, what they say, where people go, who confirms it…
  5. Define the stop-the-event trigger and decider in advance. Weather, crowd density, an incident — one named person, decided before the day.
  6. Match medical provision to a stated basis. Attendance, audience profile, alcohol, and activity, with the reasoning recorded.
  7. Brief it. An unbriefed plan protects nobody; record who was briefed and when.

What it can do on your machine

Read from SKILL.md and the folder at commit 1cbf1f0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Event Safety Plan loads about 1.7k tokens when it runs. Until then it costs about 166 tokens; SKILL.md has 837 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~166
When it runs · the whole SKILL.md, loaded when a task matches
~1.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 837 words, ~1,697 tokens.

Download SKILL.mdSave it as .claude/skills/event-safety-plan/SKILL.md (or your agent's skills folder).
name
event-safety-plan
description
Produce the event safety documentation that satisfies a venue or licensing authority and actually works on the day — the risk assessment, crowd and capacity plan, emergency procedures, and the roles that must be filled. Use when asked to write an event risk assessment, safety plan, event management plan, or emergency procedure, or when a venue or authority has requested safety documentation. Produces the risk assessment, the crowd and capacity position, emergency and evacuation procedures, the medical and welfare plan, and the roles-and-competence schedule. Not a substitute for competent safety advice, which many events legally require.

Event Safety Plan

Safety documentation gets written twice: once to satisfy the venue's paperwork request, and once — rarely — so that it would actually help if something happened. This writes the second kind. Hazards specific to this event rather than a generic list, controls that are assigned to a named person, and emergency procedures short enough to be followed by someone frightened.

What This Skill Produces

  • A risk assessment — hazards specific to this event, with controls, owners, and residual risk
  • Crowd and capacity — the capacity figure, its basis, and how flow and density are managed
  • Emergency procedures — evacuation, medical, fire, weather, and the stop-the-event decision
  • Medical and welfare provision — what level, on what basis, and where it is positioned
  • Roles and competence — who holds each safety role and what qualifies them
  • The communications plan — how the message reaches staff, suppliers, and attendees when something goes wrong

Required Inputs

Ask for these if not provided:

  • The event — type, date, venue, expected and maximum attendance, indoor or outdoor, timings
  • The audience — age profile, whether alcohol is served, mobility and accessibility needs, whether children attend
  • The activities — anything raising risk: temporary structures, pyrotechnics, vehicles, water, height, cooking, crowds standing
  • The venue's own arrangements — existing evacuation plan, capacity certificate, house safety staff, and what they require from you
  • The regulatory position — licensing conditions, local authority requirements, and any statutory duty that applies to you

Framework: Specific Hazards, Named Owners, Procedures People Can Follow

  1. Assess this event, not events in general. A downloaded template with 'slips, trips and falls' is evidence of nothing. The hazards that matter come from these activities, this venue, this audience.
  2. Every control gets a named owner and a check time. A control nobody owns is a sentence in a document.
  3. Establish capacity and its basis. Not a number you were told — the basis: exit capacity, floor area, or the venue's certificate. Then decide how you count people.
  4. Write the emergency procedure for a frightened person. Short, numbered, plain. Who calls, what they say, where people go, who confirms it is clear.
  5. Define the stop-the-event trigger and decider in advance. Weather, crowd density, an incident — one named person, decided before the day.
  6. Match medical provision to a stated basis. Attendance, audience profile, alcohol, and activity, with the reasoning recorded.
  7. Brief it. An unbriefed plan protects nobody; record who was briefed and when.

Output Format

Show full SKILL.md (438 more words)Show less
Event safety plan: [event] · [date] · [venue] · v[n]

Event: [type, date, times, indoor/outdoor] · Attendance: expected [n], maximum [n] · Audience: [profile, alcohol, children, accessibility needs]

Capacity: [figure] · Basis: [exit capacity / floor area / venue certificate] · Counting method: [how numbers are tracked] · Action at capacity: [what happens]

Risk assessment

HazardWho is at riskControlOwnerChecked atResidual

Emergency procedures

  • Evacuation: trigger [what] → [who announces, wording] → routes [where] → assembly [where] → roll call [who] → all-clear [who]
  • Medical: [who is called, where they are, how they are reached, access route for an ambulance]
  • Fire: [detection, alarm, who is responsible, equipment location]
  • Adverse weather: [thresholds — wind speed, rain, heat — and the action at each]
  • Stop the event: trigger [what] · decider [named person] · how it is communicated

Medical & welfare: provision [level] · basis: [attendance, profile, activity] · location [where] · welfare [water, quiet space, lost persons, vulnerable attendees]

Roles & competence

RoleNameCompetence/qualificationContact

Communications: staff [method] · suppliers [method] · attendees [method] · failure fallback: [what if radios fail]

Briefed: [who, when] · Documents shared with: [venue, authority, suppliers]

Not a substitute for competent safety advice. Many events are subject to statutory duties, licensing conditions, and capacity limits, and some require a qualified safety adviser, structural sign-off, or a specific medical provision standard. Confirm requirements with the venue and the relevant authority, and obtain professional advice where the event involves crowds, temporary structures, or licensed activity.

Quality Checks

  • Hazards are specific to this event's activities, venue and audience
  • Every control has a named owner and a time it is checked
  • The capacity figure states its basis and how people are counted
  • Emergency procedures are short, numbered, and name who does what
  • The stop-the-event trigger and decider are agreed in advance
  • Medical provision states the basis it was decided on
  • The plan has been briefed and the briefing recorded

Anti-Patterns

  • A downloaded generic risk assessment. Satisfies a filing requirement and nothing else.
  • Controls with no owner. Nobody checks them, and the document says they were checked.
  • A capacity number with no basis. Indefensible to a licensing officer and dangerous on the day.
  • Emergency procedures written in prose. Nobody reads a paragraph during an evacuation.
  • No pre-agreed stop trigger. The decision then gets made late, by whoever feels able to.
  • Medical provision by guesswork. It needs a stated basis.
  • Writing the plan and not briefing it. The most common failure, and the most complete one.

Example Trigger Phrases

  • "Write a risk assessment for our outdoor event"
  • "The venue is asking for an event safety plan"
  • "What emergency procedures do we need for a 500-person conference?"
  • "How do I work out how much medical cover we need?"
  • "Write an evacuation procedure for our event"

© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/event-safety-plan of mohitagw15856/pm-claude-skills.

Open the folder on GitHubat commit 1cbf1f0

Compare with similar skills

Event Safety Plan next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Event Safety Plan compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Event Safety Plan this skillmohitagw15856/pm-claude-skills1.4k—~1.7kAutomated safety check: PassMIT
Eventscoreyhaines31/marketingskills54k—~3kAutomated safety check: PassMIT
Event Sourcing Architectdavila7/claude-code-templates33k4 repos~659Automated safety check: PassMIT
Event Store Designwshobson/agents40k9 repos~828Automated safety check: PassMIT
Events Activitiessickn33/agentic-awesome-skills47k1 repos~3.9kAutomated safety check: PassMIT
Python Type Safetywshobson/agents40k—~1.4kAutomated safety check: PassMIT

Similar skills

  • Events

    coreyhaines31/marketingskills

    When the user wants to plan, run, sponsor, speak at, or get pipeline from events — webinars, conferences, trade shows, meetups, dinners, workshops, virtual summits, or user conferences.

    54k GitHub stars~3k tokensUpdated 2 days ago
    Marketing & SEOAuto-check passed

  • Event Sourcing Architect

    davila7/claude-code-templates

    Expert in event sourcing, CQRS, and event-driven architecture patterns.

    33k GitHub starsUsed in 4 repos~659 tokens
    Backend & APIsAuto-check passed

  • Event Store Design

    wshobson/agents

    Designs event stores for event-sourced systems: requirements, a comparison of EventStoreDB, PostgreSQL, Kafka, DynamoDB and Marten, and stream and versioning practices.

    40k GitHub starsUsed in 9 repos~828 tokens
    Backend & APIsAuto-check passed

  • Events Activities

    sickn33/agentic-awesome-skills

    Event register: type, date and time, venue, organizer, audience, budget against actual cost, RSVP and attendance counts and feedback score.

    47k GitHub starsUsed in 1 repo~3.9k tokens
    Data & AnalyticsAuto-check passed

  • Python Type Safety

    wshobson/agents

    Python type safety with type hints, generics, protocols, and strict type checking.

    40k GitHub stars~1.4k tokensUpdated 6 days ago
    DevelopmentAuto-check passed

  • Event Delegation

    thedaviddias/Front-End-Checklist

    A skill your agent uses when reviewing scripts, client components, bundles, or runtime behavior related to Use event delegation for dynamic content.

    74k GitHub stars~500 tokensUpdated 4 days ago
    Auto-check passed

More from mohitagw15856/pm-claude-skills

All 1,348 skills in this repo

  • Car Tco

    mohitagw15856/pm-claude-skills

    Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…

    1.4k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed

  • Cs Health Scorecard

    mohitagw15856/pm-claude-skills

    Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.

    1.4k GitHub stars~2.4k tokensUpdated yesterday
    Auto-check passed

  • Exit Waterfall

    mohitagw15856/pm-claude-skills

    Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.

    1.4k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed

  • Feature Prioritisation

    mohitagw15856/pm-claude-skills

    Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.

    1.4k GitHub stars~2k tokensUpdated yesterday
    Auto-check passed

  • Fire Number

    mohitagw15856/pm-claude-skills

    Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.

    1.4k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed

  • Freelance Rate

    mohitagw15856/pm-claude-skills

    Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.

    1.4k GitHub stars~1.2k tokensUpdated yesterday
    Auto-check passed

Questions about Event Safety Plan

What does Event Safety Plan do?

Produce the event safety documentation that satisfies a venue or licensing authority and actually works on the day — the risk assessment, crowd and capacity plan, emergency procedures, and the roles…. Event Safety Plan is an agent skill from mohitagw15856/pm-claude-skills. Produce the event safety documentation that satisfies a venue or licensing authority and actually works on the day — the risk assessment, crowd and capacity plan, emergency procedures, and the roles that must be filled.

When should I use Event Safety Plan?

Event Safety Plan fits situations like: asked to write an event risk assessment; event management plan; emergency procedure; authority has requested safety documentation.

How do I install Event Safety Plan in Claude Code?

Run `npx skills add mohitagw15856/pm-claude-skills --skill event-safety-plan -a claude-code`. Or copy the skill folder (skills/event-safety-plan in mohitagw15856/pm-claude-skills) into .claude/skills/event-safety-plan in your project. Claude Code loads it when a task matches its description.

How do I install Event Safety Plan in Codex?

Run `npx skills add mohitagw15856/pm-claude-skills --skill event-safety-plan -a codex`. Or copy the skill folder (skills/event-safety-plan in mohitagw15856/pm-claude-skills) into .agents/skills/event-safety-plan in your project. Codex loads it when a task matches its description.

Can I use Event Safety Plan in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mohitagw15856/pm-claude-skills --skill event-safety-plan -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/event-safety-plan, .gemini/skills/event-safety-plan, .github/skills/event-safety-plan and .opencode/skills/event-safety-plan in your project.

What does Event Safety Plan need to run?

SKILL.md names no scripts, command-line tools or credentials: Event Safety Plan is instructions for the agent only.

Does Event Safety Plan access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Event Safety Plan safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Event Safety Plan use?

Event Safety Plan is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Event Safety Plan use?

About 1.7k tokens (SKILL.md is roughly 6.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Event Safety Plan?

Skills that share tags, products or a category with Event Safety Plan: Events (coreyhaines31/marketingskills, 54k stars), Event Sourcing Architect (davila7/claude-code-templates, 33k stars), Event Store Design (wshobson/agents, 40k stars) and Events Activities (sickn33/agentic-awesome-skills, 47k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Event Safety Plan?

mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.

Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.