agentleFS
nickmerichnickmerich/artist-led-events-skills/skills/permits-insurance-and-risk/SKILL.md

permits-insurance-and-risk

Skill0 starsChanged 25 days agoMITView on GitHub

Plans permits, venue approval, insurance and certificates of insurance, waivers, music licensing, medical coverage, emergency action plans, and written weather thresholds (lightning, heat, cold, air quality) for artist-led athletic events, and keeps a risk register. Use for "do we need a permit", "what insurance do we need", "write the waiver checklist", "what's our heat or lightning plan", "medical plan", "can we play music", or any go/no-go safety question. Tells you what to ask and who decides; not legal, medical, or insurance advice.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    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:

    Every participant signs before participating.

    line 35
  2. Distinctive:

    Lightning: stop when thunder is heard or lightning is seen.

    line 58
  3. Distinctive:

    Heat: use wet bulb globe temperature (WBGT), not air temperature.

    line 59
  4. Very specific:

    Keep assets/risk-register.md current.

    line 65
  5. Distinctive:

    Use a substance-related theme in a way that encourages impairment during physical activity.

    line 72

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “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

Permits, Insurance, and Risk

Safety is the product. The best event in the world is a bad event if someone gets hurt and nobody had a plan.

Step 1: Map the authorities

For the venue or route, find who owns each piece and what triggers their review. Use references/authority-questions.md.

  • Land or facility owner (park department, trail council, school district, private owner). Routes can cross several owners.
  • City or township special events office (often triggered by size, amplified sound, road use, food, sales, or alcohol).
  • Police or public works (road crossings, closures, traffic control).
  • Health department (food and beverage distribution).
  • Fire marshal (indoor capacity, tents, generators).

Write down each owner's lead time, fees, and requirements. Common requirements include a nonprofit requester, minimum lead time of two months or more, limits on events per month, bans on sales or giveaways, and specific water formats. Don't promote before the path is confirmed in writing.

Step 2: Insurance

  • General liability with participant (athletic) coverage. Ask your broker for limits the venue requires; $1M per occurrence and $2M or more aggregate is a common ask.
  • Certificate of insurance (COI) naming each owner as additional insured, issued before the event.
  • Accident medical coverage for participants is worth asking about.
  • Partners and vendors who staff or bring equipment should provide their own COI.
  • Club and sanctioning programs (for example, running club associations or cycling federations) may offer event coverage. Compare with your broker.

Step 3: Waivers and consent

  • Every participant signs before participating. Digital at registration plus a paper backup at check-in.
  • Minors: guardian signs, guardian present.
  • Separate, optional checkboxes for photo/video consent and partner marketing opt-in. Never bundled into the waiver.
  • Store waivers securely; limit who can see emergency contacts and health info.
  • Have a lawyer review the waiver for your state.

Step 4: Music licensing

Playing recorded music or live performance at a public event is a public performance. The event owner is responsible for licensing; it can't be shifted to the DJ or band. Options: venue's existing licenses (confirm they cover your event), direct licenses from the performing rights organizations, or a group program through a club association. Sync rights for music in published video are separate. See references/sources.md.

Step 5: Medical and emergency action plan

Fill assets/emergency-action-plan.md:

  • Named medical lead with appropriate credentials for the event size. For larger events, talk to local EMS early.
  • AED location and who is trained; first aid kit contents matched to the sport.
  • Exact address and access point for ambulances. Who calls 911 and who meets the ambulance.
  • Lost participant, lost child, and missing-runner procedures.
  • Incident log, filled even if nothing happens.

Step 6: Weather plan (written before the day)

Name one person who makes the call and write the thresholds down in advance. Use references/weather-thresholds.md.

  • Lightning: stop when thunder is heard or lightning is seen; everyone to a substantial building or hard-topped vehicle; resume only 30 minutes after the last thunder, resetting the clock with each new strike. Know the shelter and how long it takes to get there.
  • Heat: use wet bulb globe temperature (WBGT), not air temperature. Pre-set modify, shorten, and cancel thresholds. Published guidelines vary by organization and region and assume acclimatized participants; for unacclimatized community participants, set conservative thresholds and earlier start times.
  • Cold, ice, wind, and air quality: set thresholds too.
  • Announce the plan to participants before the day: where updates will be posted and how a delay works.

Step 7: Risk register

Keep assets/risk-register.md current. Each risk gets likelihood, impact, mitigation, owner, and trigger. Review it at every gate.

Never

  • Promote an event before the venue path is confirmed.
  • Let the artist, a sponsor, or the crowd override a safety call.
  • Hand out cups, food, or product where the venue bans it.
  • Use a substance-related theme in a way that encourages impairment during physical activity. Keep any adult or licensed component legal, separate, and after.

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.