event-production SKILL.md skillA
event-production from samber/dev-event-organizer-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add samber/dev-event-organizer-skills/event-production@v1.0.0Pins v1.0.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- samber/dev-event-organizer-skills
- Path
skills/event-production/SKILL.md- Versions recorded
- 2
- Latest version
- v1.0.0, committed Aug 27, 2026
- First version recorded
- Aug 27, 2026
- Size
- 32,114 bytes
- Repository stars
- 4
- License
- MIT
Engineer the technical AV production of a technical event once the format and session grid are fixed - capture tiers from a single smartphone to multi-camera vision mixing, signal-path architecture separating room display from recorded output and crew monitor, redundancy against named recorded-audio failure modes, AV crew roles, the written technical spec handed to venue sourcing, the Media budget line, rehearsal, and the publication pipeline. Use whenever the user mentions conference AV…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# 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… …
Read the whole file at its exact version.
How to install
mdr add samber/dev-event-organizer-skills/event-production@sha256:da6baab1112c7c0cThe line at the top of this page pins the label v1.0.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_lsx6nvun4zlfacdb)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, all committed on Aug 27, 2026.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0.0 latest | 2026-08-27 | f735237 | 32,114 B | A | view · diff |
| v1.0.0 | 2026-08-27 | 12e132b | 32,113 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (32114 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
samber/dev-event-organizer-skills · 4 stars · license MIT · pushed 2026-11-01 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_lsx6nvun4zlfacdb GET https://markdownregistry.com/api/v1/resolve?ref=samber/dev-event-organizer-skills/event-production GET https://markdownregistry.com/api/v1/blob/da6baab1112c7c0c1be92e15e91c45afb75b2b51786a920f90724a307bb61307
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.