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 Run Of Show

by mohitagw15856 in mohitagw15856/pm-claude-skills

Build the minute-by-minute run of show that lets an event run without the planner being asked anything — every cue, who owns it, what happens if it slips, and the version each supplier actually needs.

MITAuto-check passed

Install Event Run Of Show

skills CLI
$ npx skills add mohitagw15856/pm-claude-skills --skill event-run-of-show -a claude-code

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

GitHub CLI
$ gh skill install mohitagw15856/pm-claude-skills event-run-of-show --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-run-of-show .claude/skills/event-run-of-show && 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-run-of-show
GitHub stars
1.4k
Token cost
~1.4k tokens
SKILL.md length
760 words
Files
1
Skills in repo
1,348
Repo updated
First seen
Licence
MIT

At a glance

Build the minute-by-minute run of show that lets an event run without the planner being asked anything — every cue, who owns it, what happens if it slips, and the version each supplier actually needs.

  • Works in 7 steps: Place the immovable points first. Doors,… → Build load-in backwards from the first… → Give every cue an owner and a trigger.… → …
  • Asked to write a run of show
  • SKILL.md covers What This Skill Produces, Required Inputs, Framework: Fixed Points,… and Output Format, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Event Run Of Show is an agent skill from mohitagw15856/pm-claude-skills. Build the minute-by-minute run of show that lets an event run without the planner being asked anything — every cue, who owns it, what happens if it slips, and the version each supplier actually needs. Use when asked to write a run of show, event schedule, show flow, or production schedule, or to prepare the day-of timeline for a conference, wedding, launch, or gala. Produces the master timeline with owners and cues, the load-in and load-out schedule, the supplier-specific extracts, the contingency triggers, and…

Its SKILL.md is about 1.4k 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 a run of show
  • Production schedule
  • Prepare the day-of timeline for a conference

Example prompts

  • “/event-run-of-show”

Workflow steps

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

  1. Place the immovable points first. Doors, the broadcast window, the ceremony, the curfew. Everything else is scheduled around them, not the…
  2. Build load-in backwards from the first fixed point. Rig before lighting focus, focus before sound check, sound check before doors…
  3. Give every cue an owner and a trigger. Not 'music starts' but 'DJ starts walk-in music on Sarah's cue from the back of house'. A cue with…
  4. Build in float where it is cheap. Ten minutes before a fixed point is worth an hour anywhere else.
  5. Write the contingencies before the day. Speaker late, rain, AV failure, over-running speeches — decision rule and decider, agreed in…
  6. Publish extracts. Each supplier gets their own rows plus the fixed points. The full document is for the core team only.
  7. Name one decider. Two people empowered to make calls on the day is worse than none.

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 Run Of Show loads about 1.4k tokens when it runs. Until then it costs about 141 tokens; SKILL.md has 760 words of instructions outside code blocks.

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

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). 760 words, ~1,434 tokens.

Download SKILL.mdSave it as .claude/skills/event-run-of-show/SKILL.md (or your agent's skills folder).
name
event-run-of-show
description
Build the minute-by-minute run of show that lets an event run without the planner being asked anything — every cue, who owns it, what happens if it slips, and the version each supplier actually needs. Use when asked to write a run of show, event schedule, show flow, or production schedule, or to prepare the day-of timeline for a conference, wedding, launch, or gala. Produces the master timeline with owners and cues, the load-in and load-out schedule, the supplier-specific extracts, the contingency triggers, and the on-the-day contact sheet.

Event Run of Show

On the day, the planner becomes a bottleneck the moment anyone has to ask a question. The run of show exists to make the answers findable without you: every cue timed, every cue owned by a named person, and the recovery written for the three things most likely to slip. It is also the document nobody reads in full — so it ships in extracts, one per supplier.

What This Skill Produces

  • The master timeline — cue by cue, with clock time, duration, owner, and the trigger that starts it
  • Load-in and load-out schedule — sequenced by dependency, which is where most overruns are actually born
  • Supplier extracts — the same timeline filtered to what each supplier needs, because nobody reads 14 pages
  • Contingency triggers — the three or four most likely slips, with the decision rule and who makes the call
  • The contact sheet — every supplier's on-the-day person and number, not the account manager
  • The cut list — what gets dropped, in order, if the schedule runs long

Required Inputs

Ask for these if not provided:

  • The event — type, date, venue, headcount, and the format
  • The fixed points — what cannot move: doors, speeches, a broadcast slot, a licence end time, sunset
  • The suppliers — who is involved, when they need access, and how long they need
  • The venue constraints — access times, noise curfew, lift capacity, licence hours, security requirements
  • Who decides on the day — the single person who makes the call when something slips

Framework: Fixed Points, Dependencies, Then Everything Else

  1. Place the immovable points first. Doors, the broadcast window, the ceremony, the curfew. Everything else is scheduled around them, not the reverse.
  2. Build load-in backwards from the first fixed point. Rig before lighting focus, focus before sound check, sound check before doors. Sequencing by dependency, not by supplier convenience.
  3. Give every cue an owner and a trigger. Not 'music starts' but 'DJ starts walk-in music on Sarah's cue from the back of house'. A cue with no named owner does not happen.
  4. Build in float where it is cheap. Ten minutes before a fixed point is worth an hour anywhere else.
  5. Write the contingencies before the day. Speaker late, rain, AV failure, over-running speeches — decision rule and decider, agreed in advance.
  6. Publish extracts. Each supplier gets their own rows plus the fixed points. The full document is for the core team only.
  7. Name one decider. Two people empowered to make calls on the day is worse than none.

Output Format

Show full SKILL.md (344 more words)Show less
Run of show: [event] · [date] · [venue] · v[n]

Fixed points: [time — what] · [time — what] · Curfew: [time] · Decider on the day: [name, number]

Load-in

TimeActivitySupplierOwnerDepends onDone

Show

TimeDurCueTriggerOwnerNotes
[18:30][30m]Doors, walk-in music[Venue confirms room clear][name]

Load-out

TimeActivitySupplierOwnerDepends on

Contingencies

If this happensTrigger pointWe do thisDecider
[speaker late][5 min before slot][swap to next segment][name]

Cut list — if running long, drop in this order: 1. [item] 2. [item] 3. [item]

Contacts — [role · name · mobile], on-the-day people only

Supplier extracts issued: [supplier — rows — sent date]

Venue licensing, capacity, curfew and safety requirements are set by the venue and local authority — confirm them directly rather than relying on a schedule. Where an event involves crowd safety, temporary structures, or licensed activity, competent safety advice is required.

Quality Checks

  • Fixed and immovable points are placed before anything else
  • Load-in is sequenced by dependency, not by supplier preference
  • Every cue has a named owner and an explicit trigger
  • Float exists immediately before each fixed point
  • Contingencies name the decision rule and the decider in advance
  • Supplier extracts have been issued, not just the master document
  • Exactly one person is empowered to make calls on the day

Anti-Patterns

  • Cues with no owner. 'The music starts' describes a hope.
  • Scheduling load-in by supplier convenience. Produces four vans and one lift at 8am.
  • Sending 14 pages to every supplier. Nobody reads it, so nobody follows it.
  • No float before fixed points. One small slip cascades into the ceremony.
  • Inventing contingencies on the day. The worst decisions are made under time pressure by whoever is nearest.
  • Two deciders. Guarantees a stalled decision at the moment one is needed.
  • Account-manager numbers on the contact sheet. They are not at the venue on a Saturday.

Example Trigger Phrases

  • "Write a run of show for a 200-person launch event"
  • "Build the day-of timeline for this conference"
  • "What order should load-in happen in?"
  • "Write contingency plans for our outdoor event"
  • "Create a production schedule for the gala"

© 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-run-of-show of mohitagw15856/pm-claude-skills.

Open the folder on GitHubat commit 1cbf1f0

Compare with similar skills

Event Run Of Show 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 Run Of Show compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Event Run Of Show this skillmohitagw15856/pm-claude-skills1.4k—~1.4kAutomated 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
Event Staffing Orderingsickn33/agentic-awesome-skills47k1 repos~1.5kAutomated safety check: PassMIT
Const Letthedaviddias/Front-End-Checklist74k—~469Automated 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

  • Event Staffing Ordering

    sickn33/agentic-awesome-skills

    Order W-2 compliant temporary event staff for conventions, trade shows, festivals, concerts, sporting events, and brand activations across 300+ US and Canadian markets via TempGuru.

    47k GitHub starsUsed in 1 repo~1.5k tokens
    Agent WorkflowsAuto-check passed

  • Const Let

    thedaviddias/Front-End-Checklist

    A skill your agent uses when reviewing scripts, client components, bundles, or runtime behavior related to Prefer const and let over var.

    74k GitHub stars~469 tokensUpdated 4 days ago
    Auto-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 Run Of Show

What does Event Run Of Show do?

Build the minute-by-minute run of show that lets an event run without the planner being asked anything — every cue, who owns it, what happens if it slips, and the version each supplier actually needs. Event Run Of Show is an agent skill from mohitagw15856/pm-claude-skills. Build the minute-by-minute run of show that lets an event run without the planner being asked anything — every cue, who owns it, what happens if it slips, and the version each supplier actually needs.

When should I use Event Run Of Show?

Event Run Of Show fits situations like: asked to write a run of show; production schedule; prepare the day-of timeline for a conference.

How do I install Event Run Of Show in Claude Code?

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

How do I install Event Run Of Show in Codex?

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

Can I use Event Run Of Show 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-run-of-show -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-run-of-show, .gemini/skills/event-run-of-show, .github/skills/event-run-of-show and .opencode/skills/event-run-of-show in your project.

What does Event Run Of Show need to run?

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

Does Event Run Of Show 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 Run Of Show 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 Run Of Show use?

Event Run Of Show 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 Run Of Show use?

About 1.4k tokens (SKILL.md is roughly 5.7k 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 Run Of Show?

Skills that share tags, products or a category with Event Run Of Show: Events (coreyhaines31/marketingskills, 54k stars), Event Sourcing Architect (davila7/claude-code-templates, 33k stars), Event Store Design (wshobson/agents, 40k stars) and Event Staffing Ordering (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 Run Of Show?

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.