Skip to content

samber/dev-event-organizer-skills / skills/event-community-building

event-community-building

Verified

Animate 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.

references/community-asset-handoff.md

View on GitHub
# Handing over the community asset

Contents: the three-way artifact split; the asset inventory; the member-list retention decision; the dated handoff checklist; the personal-account negative example.

Everything below is carried over from generic organizational account-ownership practice, not measured against event data. **What does not carry over: that practice assumes an employment relationship.**

**Nobody here is contractually obliged to complete a transfer, no leaving date is enforceable, and the person holding the credential is usually a volunteer who built the thing.** Design the handoff as something a departing volunteer will want to complete, never as an offboarding process.

## Three artifacts, three owners

An organizer handover moves three separate things. Only the third belongs to this skill; the split exists so none of the three is assumed to be covered by whoever handles the loudest one.

| Artifact                                    | Owner skill                                                      | What is actually transferred                                                            |
| ------------------------------------------- | ---------------------------------------------------------------- | --------------------------------------------------------------------------------------- |
| The organizing team and its decision rights | `samber/dev-event-organizer-skills@event-team-structure`         | Roles, authority, the charter, team accounts                                            |
| The operational learning log                | `samber/dev-event-organizer-skills@event-continuous-improvement` | The persisted cross-edition log, named as a bus-factor mitigation                       |
| The community asset                         | This skill                                                       | Platform ownership, admin roles, member list, archive, invite links, retention decision |

`samber/dev-event-organizer-skills@event-team-structure`'s succession menu already carries the account-ownership move for team assets; this is the community half of that same move, and the two should be done in one sitting rather than discovered separately.

Its 6-12-month handover window applies to the **lead role**. Set the platform account's own window deliberately, and say it is the team's call rather than borrowing that number.

## The asset inventory

One page, its rows drawn up here rather than taken from a standard. Every row names a holder today and a holder after; a row with no holder after is the finding, not an omission.

| Asset                                     | Where it lives | Holder today | Holder after | Notes                                              |
| ----------------------------------------- | -------------- | ------------ | ------------ | -------------------------------------------------- |
| Platform workspace / server / forum       |                |              |              | Registered to whose account?                       |
| Admin and moderator roles                 |                |              |              | At least two, at least one not the departing owner |
| Billing, if any                           |                |              |              | A card that expires ends the space silently        |
| Custom domain or vanity link              |                |              |              | Renewal date                                       |
| Standing invite links                     |                |              |              | Which are public, which expire                     |
| Member list export                        |                |              |              | Format, location, consent basis                    |
| Archive / recordings / published material |                |              |              | Is it reachable without the platform?              |
| Conduct reporting route                   |                |              |              | Still monitored by whom, in the gap                |

The two rows that orphan a space most often are the first and the second-to-last: the workspace registered to a personal account, and an archive that only exists inside a platform nobody can log into.

## The member-list retention decision

Restate it at every handoff, and never let it be inherited by silence. Four fields, set here rather than drawn from a standard:

- **Owner** - a named living person, not a role nobody currently fills.
- **Basis** - what members were told when they joined, in the words they were told it in.
- **Scope** - what the list may be used for. "Announcing our own next edition" and "anything the team decides later" are different scopes and only one of them was granted.
- **Review or deletion date** - a date, not "when it stops being useful".

The retention duty here is inherited from the sign-up flow and the attendee list's own consent rules, which sibling skills own. Do not derive a second policy; restate the one that exists and name the gap where it does not cover a list that has outlived its edition. Name no jurisdiction, quote no retention period, and route the actual decision to the organizer's own counsel.

## The dated handoff checklist

This skill's own checklist. Run it as a session with both people present, never as a document sent to someone leaving.

1. Fill the inventory together, on screen. Assumptions surface here and nowhere else.
2. Transfer ownership of record first, before admin roles - an admin who is not the owner can be removed by the owner who left.
3. Add a second admin who is neither of you. A handoff that produces a bus factor of one has moved the risk, not reduced it.
4. Export the member list, and record where the export lives and who can reach it.
5. Restate the retention decision in the four fields above, dated.
6. Confirm the conduct reporting route resolves to someone currently reading it.
7. Post to the space that the owner has changed, in the register. Members are entitled to know who holds their data.
8. Date the document and set the next review. A handoff document with no review date is accurate exactly once.

## Negative example

Illustrative, with invented names:

> "Sarah's stepping back but she's added Tom as an admin, so we're covered."

Three failures, and they only surface later:

- The workspace is registered to Sarah's personal email. Tom is an admin inside a space Sarah owns; the day that email closes, so does everything.
- Nobody restated the retention decision, so a list collected for one edition's announcements is now being used for whatever the current team decides.
- The conduct reporting route still points at Sarah. Reports go somewhere nobody reads, and the duty is live regardless.

The fix is not more process. It is the default rung: one written page, filled in together, with ownership of record moved first.
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: 472kUpdated Claude CodeCodexVerifiedInstall
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: 323kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 323kUpdated Claude CodeCodexVerifiedInstall
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 availableStars: 323kUpdated Claude CodeCodexVerifiedInstall