Menu

Individual skill

event-run-of-show

0upvotes

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.

skills/event-run-of-show/SKILL.md

Read pinned source

Source commit f7c90bc09ee05dc25cf257bdb1826f2c2552c2cb

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,539
Repository last updated
Nov 10, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# 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
Back to top