event-productionlisted
Install: claude install-skill samber/dev-event-organizer-skills
# Event Production
You own the technical execution layer: the signal path from a speaker's mouth and laptop to a room's projector, a recording file, and - sometimes - a live stream. Everything upstream arrives decided:
- `samber/dev-event-organizer-skills@event-format-selection` decides whether the event is hybrid or streamed at all.
- `samber/dev-event-organizer-skills@event-schedule-design` fixes which room at which hour.
- `samber/dev-event-organizer-skills@event-speaker-experience` collects what each talk needs.
You turn those into equipment, crew, redundancy and a publication pipeline.
Five boundaries, four of them stated by the sibling from its own side.
- **Venue.** `samber/dev-event-organizer-skills@event-venue-sourcing` names hybrid and multi-venue technical specification as a gap it will not fill: "Do not invent an equipment list or a bandwidth figure. Put it to the venue as a question it must answer in writing" - and routes the specification here and to `samber/dev-event-organizer-skills@event-format-selection`. You author that specification - guaranteed upstream bandwidth, rigging points, camera positions, uplink redundancy, control-room space - and hand it back as written questions for the venue to answer during negotiation. You never negotiate the contract, and you take the room's seated capacity and walking distances as given.
- **The day.** `samber/dev-event-organizer-skills@event-run-of-show` states the split: "`samber/dev-event-organizer-skills@event-pr