event-run-of-showlisted

Write and run the day-of run of show for a technical event once the schedule is published - the minute-by-minute playbook staff execute from, day-of role assignment (MC, speaker introducers, room leads, the organizer on duty), cue sheets at every transition, an organizer-only comm channel kept separate from attendee-facing ones, the escalation path and live incident response, shift rotation with verified handoffs, and closeout. Use whenever the user mentions a day-of rundown, a cue sheet, MC or room-lead roles, organizer radios or Slack channels, shift handoffs, or deciding live what to cut when a session overruns - even if they never say "run of show". Do NOT use to build the grid itself - use samber/dev-event-organizer-skills@event-schedule-design instead.
samber/dev-event-organizer-skills · ★ 2 · Web & Frontend · score 76

Install: claude install-skill samber/dev-event-organizer-skills

# Event Run of Show You own the day itself. The grid arrives decided and you never reopen it: `samber/dev-event-organizer-skills@event-schedule-design` states the split from its own side - "You stop at the published grid: how staff execute it minute by minute on the day, and how they respond live to a no-show or an AV failure, is `samber/dev-event-organizer-skills@event-run-of-show`". It also hands you one more artifact besides the grid: a **disruption priority order** written into the schedule document. 1. Protect the plenary or keynote first. 2. Protect the headline commitment the audience showed up for next. 3. Minimize how many other sessions the fix disturbs. 4. Lock the revised grid for the rest of the block. Consume that order. Do not re-derive one under pressure. `samber/dev-event-organizer-skills@event-speaker-experience` states the same boundary from its side - "the minute-by-minute conduct of the day belongs to `samber/dev-event-organizer-skills@event-run-of-show`", and it lists this skill as owning "the day-of minute-by-minute document; hand it your speakers' timing needs." Green room, tech check and the on-site host who walks a speaker to their room stay there. You receive arrival and timing constraints as input, and you are where a speaker's live delay becomes a decision. Two more boundaries: - `samber/dev-event-organizer-skills@event-risk-management` authors the standing register and the printed emergency plan: which scenarios, which contacts. You never