Event Comms Channels

samber/dev-event-organizer-skills/skills/event-comms-channels

by samberaf0a7c0dcec0MIT3 starsListed Oct 9, 2026Updated Oct 9, 2026Repository updated 10 days ago

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.

Only the file list is public. File contents are available once the skill is installed in a workspace.

PathSizeType
evals/evals.json34.4 KBapplication/json
references/channel-roster-and-platform-notes.md7.5 KBtext/markdown
references/menu-ranking-rationale.md3.5 KBtext/markdown
references/message-class-matrix-and-message-bank.md9.8 KBtext/markdown
references/wind-down-and-status-page.md5.9 KBtext/markdown
SKILL.md25 KBtext/markdown

Source and attribution

Source:samber/dev-event-organizer-skillsinskills/event-comms-channelsat commitaf0a7c0

License: MIT

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal