Working Video & audio skill
Run an event rehearsal
Test event people, content, cues, systems, access, and recovery before participants arrive.
Procedure
- Define objectives, scope, participants, test environment, schedule, authority, and evidence.
- Reconcile the current program, run of show, production plan, access plan, staffing, and contacts.
- Test load, content, speaker, host, moderation, cue, transition, caption, interpretation, stream, and support paths.
- Use realistic inputs and timing rather than talking through every step.
- Inject late speaker, corrupt media, microphone failure, network loss, caption failure, overrun, and emergency interruption.
- Record expected, observed, impact, owner, workaround, retest, and go or no-go consequence.
- Update controlled artifacts and rerun critical failures from a reset state.
- Issue a readiness report with open risks, accepted exceptions, and show-day checks.
Guardrails
- Do not trigger live emergency services, public messages, payments, or participant notifications.
- Never treat an unexecuted discussion as a passed test.
- Protect credentials, private content, accommodation data, and incident channels.
--- name: run-an-event-rehearsal category: media description: Test event people, content, cues, systems, access, and recovery before participants arrive. Use when a program has live dependencies that cannot be trusted from documents alone. --- # run-an-event-rehearsal ## Procedure 1. Define objectives, scope, participants, test environment, schedule, authority, and evidence. 2. Reconcile the current program, run of show, production plan, access plan, staffing, and contacts. 3. Test load, content, speaker, host, moderation, cue, transition, caption, interpretation, stream, and support paths. 4. Use realistic inputs and timing rather than talking through every step. 5. Inject late speaker, corrupt media, microphone failure, network loss, caption failure, overrun, and emergency interruption. 6. Record expected, observed, impact, owner, workaround, retest, and go or no-go consequence. 7. Update controlled artifacts and rerun critical failures from a reset state. 8. Issue a readiness report with open risks, accepted exceptions, and show-day checks. ## Guardrails - Do not trigger live emergency services, public messages, payments, or participant notifications. - Never treat an unexecuted discussion as a passed test. - Protect credentials, private content, accommodation data, and incident channels. ## Done - A rehearsal report records scope, executed tests, results, defects, owners, and retests - Critical cues, access, primary systems, fallbacks, and handoffs are verified - Readiness, accepted risk, show-day checks, and decision authority are documented