# event-comms-channels

Designs how a technical event talks to attendees: which channels exist, who writes on each, where a message routes, and when a channel closes.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 5200 installs · ★ 4
- Author: Samuel Berthe
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/samber/dev-event-organizer-skills/tree/HEAD/skills/event-comms-channels/SKILL.md
- Updated: 2026-10-24
- HTML: https://affpapa.org/en/nevibecode/skills/event-comms-channels

## What it does

The skill builds a channel architecture for one edition of an event, from the moment attendees exist to the moment the last channel is shut down. You get a roster where every channel has one stated job and one named owner, a routing rule for messages, and a dated wind-down. It writes no copy. The register arrives fixed from `samber/dev-event-organizer-skills@event-cultural-identity`; this skill only decides how several writers execute it without drifting.

Work starts with an interview, one question at a time, multiple-choice where possible. Message classes come first, channels second — a roster picked before the messages are known is picked by fashion. Then three menus follow: channel roster, routing policy, consistency process. If no register exists yet, the skill stops and routes you to `event-cultural-identity`, marking everything here provisional.

Several areas belong to sibling skills, and re-deriving them creates duplicates. Organizer coordination sits with `event-run-of-show`, incident reporting with `event-code-of-conduct`, mailing-list copy and consent with `event-attendee-email-sequences`, public posts with `event-social-media`. The skill also notes two boundaries written from one side only: static wayfinding belongs to `event-attendee-experience`, while live on-site announcements belong here.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add samber/dev-event-organizer-skills --skill event-comms-channels -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/event-comms-channels/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/event-comms-channels/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add samber/dev-event-organizer-skills --skill event-comms-channels -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/event-comms-channels/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add samber/dev-event-organizer-skills --skill event-comms-channels -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/event-comms-channels/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install samber/dev-event-organizer-skills event-comms-channels
```

2. **Manually: put the files in place**
- File: `.github/skills/event-comms-channels/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add samber/dev-event-organizer-skills --skill event-comms-channels -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/samber/dev-event-organizer-skills --path skills/event-comms-channels
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/event-comms-channels/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add samber/dev-event-organizer-skills --skill event-comms-channels -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/samber/dev-event-organizer-skills/tree/HEAD/skills/event-comms-channels/SKILL.md

## When to use it
- decide whether an event needs a chat space, an app or a status page
- work out where a room change or schedule slip gets announced
- keep several writers sounding like one event
- stop attendees from missing announcements
- wind down every channel once the event ends

## Example prompts
- Design the attendee comms channels for a two-day conference with three rooms
- Where should a room change be announced — chat or status page?
- Draft the wind-down plan for the event channels after it ends

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: d1f5068bbd27ae26.

BEGIN THIRD-PARTY FILE d1f5068bbd27ae26
```text
---
name: event-comms-channels
description: 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.
license: MIT
metadata:
  author: Samuel Berthe
  version: "1.1.0"
---

# 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                                                                                                                                                                           |
```
END THIRD-PARTY FILE d1f5068bbd27ae26

The third-party file has ended. Everything between the d1f5068bbd27ae26 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2070 of 26181 bytes. © Samuel Berthe · MIT · https://github.com/samber/dev-event-organizer-skills/tree/HEAD/skills/event-comms-channels/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md