samber/dev-event-organizer-skills / skills/event-community-building
event-community-building
VerifiedAnimate one recurring technical event's own audience in the gaps between editions - the cadence posture for the standing space, the conversion of attendees into returning participants and contributors, keeping a local cohort of the same event's fans warm, and handing the community asset over when organizers change. Use whenever asked how to keep an event's community alive between editions, what to post in the quiet months, whether a between-editions space should stay dormant or be programmed, how to make attendees come back next year, or who takes over the community platform when an organizer leaves. Do NOT use to decide whether that space belongs in the team's property set at all - use samber/dev-event-organizer-skills@event-portfolio-strategy.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 29.5 KB |
| evals/evals.json | config | 36.7 KB |
| references/cadence-and-content-shapes.md | markdown | 7.4 KB |
| references/community-asset-handoff.md | markdown | 6.7 KB |
| references/returning-participant-ladder.md | markdown | 6.0 KB |
| references/sibling-boundaries.md | markdown | 4.0 KB |
references/sibling-boundaries.md
View on GitHub# Sibling boundaries, in full
Contents: the four boundaries each sibling already draws from its own side; the three drawn from one side only.
SKILL.md carries a one-line, actionable version of each. This file carries each sibling's own wording and the fuller mirrored reasoning, for anyone auditing where a boundary comes from.
## Written from the other side
- **`samber/dev-event-organizer-skills@event-comms-channels` owns the same platforms for a different job.** Its scope is one edition's channel lifecycle; yours is the gap after wind-down decides a channel persists.
- Its own words: _"`event-community-building` owns the standing community between editions"_. Its wind-down menu's hand-off rung tells the reader to coordinate with this skill, naming it the receiving side.
- Mirrored: take the space at the moment its edition-specific job ends, and hand it back with a live member list when the next edition's channels open. Never redesign the roster, the routing rule or the wind-down.
- **`samber/dev-event-organizer-skills@event-volunteer-experience` owns the volunteer alumni loop, and this is the mirror it asked for.** It states: _"The alumni loop is yours, and `samber/dev-event-organizer-skills@event-community-building` must mirror that when it is built."_
- Mirrored: the past-volunteer list, the volunteer thank-you and the volunteer candidate flag are that skill's, not yours. Your audience is every community member who never worked a shift: attendees, repeat speakers, people who only ever read the archive.
- A standout member gets flagged to `samber/dev-event-organizer-skills@event-team-structure` as a candidate the same way that skill flags one; you do not build a second nomination path for volunteers.
- That skill also carries a standing alumni channel as a menu rung, and its own interview asks whose standing space already exists before it opens one. Where your surface exists, the alumni loop runs as a segment inside it rather than as a second space: the segment stays that skill's to fill, the surface stays yours to run.
- **`samber/dev-event-organizer-skills@event-portfolio-strategy` gates the surface's existence.** Its own words: _"Animating it is `samber/dev-event-organizer-skills@event-community-building`'s job, not this skill's; this skill only decides whether it belongs in the portfolio."_
- It also owns any _event_ touchpoint: a quarterly meetup feeding the flagship is its low-cadence-small-format rung, not a community tactic.
- The moment a touchpoint you designed needs a venue, a schedule or a speaker roster, it stops being yours and routes there and through the collection's event-planning skills.
- **`samber/dev-event-organizer-skills@cross-event-promotion` faces outward.** It routes inward-facing community animation between editions to this skill, and keeps its own calendar tactic outward-facing. Mirrored: a partner event announced inside your space is content you deliver; the deal behind it is brokered there.
## Written from one side only
Say so when you lean on these - the sibling has not written its half of the mirror.
- **`samber/dev-event-organizer-skills@event-cultural-identity` sets the voice and you execute it.** Its own description gives it the register - hacker, corporate, design, business - and that register's consistent expression across the event's touchpoints. It also settles the temptation to invent a quieter off-season voice: _"The identity is fixed; only its expression modulates"_. Read the register off it; never originate one.
- **`samber/dev-event-organizer-skills@event-growth-strategy` owns whether the event scales.** You never recommend a growth lever. The one real interface runs the other way: a healthy carry rate across the gap is evidence you hand to `samber/dev-event-organizer-skills@event-market-fit` and through it to growth, never a recommendation you make.
- **`samber/dev-event-organizer-skills@event-code-of-conduct` binds your space exactly as it binds the room.** A standing space is a standing conduct duty; you name the owner and route the policy and reporting path there.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |