event-production

Plans conference AV production including capture tiers, signal paths, redundancy, crew roles, and publication pipelines.

1|Updated Sep 6, 2026
One-click install
npx skills add https://github.com/samber/dev-event-organizer-skills --skill event-production-samber
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: event-production
Source: https://github.com/samber/dev-event-organizer-skills/tree/main/skills/event-production
Command: npx skills add https://github.com/samber/dev-event-organizer-skills --skill event-production-samber

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Organizing the technical AV side of a conference or meetup is full of silent failure modes: recordings that exist but are unusable, streams that fail live, and suppliers quoting against a spec that was never written. This Skill turns a fixed event format and session grid into a concrete production plan covering equipment tiers, signal architecture, redundancy, crewing, and the post-event publication pipeline. ## Core Features & Use Cases - Coverage tier selection per room: Ranks capture options from a smartphone floor up to multi-camera vision mixing with live streaming, re-ranked against your venue, crew, and recurrence context. - Signal path and redundancy engineering: Designs the three-destination split (room display, encoder, crew monitor) and engineers backups against named failure modes like unlabelled tracks and unsynced clocks. - Venue spec and supplier brief authoring: Produces the venue technical specification as written questions and a line-item AV supplier brief with acceptance criteria, ready to hand to venue sourcing and vendor contracting. - Crew roles, training, and rehearsal: Maps six sourced AV crew roles, picks the right training tier for new versus returning crews, and provides a seven-step rehearsal walkthrough. - Use Case: A first-edition two-room conference wants all talks recorded for YouTube with six inexperienced volunteers. The Skill produces a per-room coverage plan, board-sourced audio chain, a named production owner, a full-introduction training path, and a test-playback gate before doors open. ## Quick Start Ask the assistant to plan the AV production for your event, stating how many rooms run at once, whether anything is recorded or streamed, and what the venue already provides.

Frequently Asked Questions about event-production

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I record conference talks with good audio quality?

Take the audio feed from the mixing board rather than the camera's built-in microphone, since room audio from a camera at the back produces recordings nobody finishes watching. Pair this with a fixed camera as the default coverage tier and play back one test recording before doors open.

What equipment do I need to livestream a conference keynote?

A livestream sits on top of a two-camera setup with vision mixing and requires rehearsal ahead of time plus at least one person whose only job during the event is running the stream. You also need the venue's guaranteed upstream bandwidth confirmed in writing, never an invented figure.

What should go in an AV supplier brief for a conference?

Include capture posture per room, camera coverage, a board-sourced audio requirement, recording deliverables with a file naming convention and handover moment, required redundancy, crew hours, rehearsal, and an acceptance criteria section. The acceptance criteria are what make the brief enforceable after delivery.

How many people do I need on a conference video crew?

Sourced practice names six distinct roles: stage manager, audio operator, camera operator, vision mixer, AV-technical lead, and general crew. Treat them as a menu, not a required roster: a one-room fixed-camera event needs only the technical lead and audio, while a two-camera room needs camera operation and vision mixing as separate people.

Why do conference recordings end up unusable even when the recorder worked?

Documented failure modes include unlabelled tracks, no clock sync, manual drive relays, network-spiking bulk copies, and files too large to seek through. The fix is a naming convention, synced clocks, continuous chunked sync to storage, and one full test playback before the event.

When should I not use this Skill for event AV decisions?

Do not use it to decide whether the event should be hybrid or virtual at all; that format decision belongs to the upstream format-selection skill. This Skill reports what a format costs technically, then executes whatever was decided.