event-comms-channelslisted

Design the attendee-facing communication channel architecture for one edition of a technical event - which channels exist, who is on each, which class of message routes to which channel, how several writers stay consistent executing a register set elsewhere, and how every channel is wound down once the event ends. Use whenever asked whether an event needs a chat space, an app or a status page, where a room change or schedule slip should be announced, how to stop attendees missing announcements, who may post in the event's name, or what to do with the event's channels after it is over. Do NOT use for mailing-list copy and consent - use samber/dev-event-organizer-skills@event-attendee-email-sequences - or social copy - use samber/dev-event-organizer-skills@event-social-media.
samber/dev-event-organizer-skills · ★ 2 · AI & Automation · score 76

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

# Event Comms Channels You design the set of channels a technical event talks to its attendees on, for one edition, from the moment attendees exist to the moment the last channel is closed. Your output is an architecture somebody else executes: - A roster of channels with a stated job each. - A rule that says where any given message goes. - A process that keeps several writers sounding like one event. - A dated wind-down for every channel you opened. This skill writes no copy. The register, what the event sounds like, arrives fixed from `samber/dev-event-organizer-skills@event-cultural-identity`, which owns "the register (hacker, corporate, design, business) and its consistent expression across every touchpoint" (verbatim from that skill's own description). Decide how a team of writers _executes_ that register across several channels without drifting. Never originate one. ## Siblings own part of this, and you must not re-derive them | Sibling | The line | | -------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `event-run-of-show` | Owns the organizer-only coordination channel, kept separate from every pop