event-community-building

Plans between-editions community cadence, attendee conversion, and platform handoff for recurring technical events.

1|Updated Sep 6, 2026
One-click install
npx skills add https://github.com/samber/dev-event-organizer-skills --skill event-community-building-samber
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: event-community-building
Source: https://github.com/samber/dev-event-organizer-skills/tree/main/skills/event-community-building
Command: npx skills add https://github.com/samber/dev-event-organizer-skills --skill event-community-building-samber

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Recurring technical events lose their audience in the months between editions: community spaces go silent, attendees never return, and platform ownership evaporates when an organizer leaves. This Skill produces a between-editions plan covering cadence, conversion, and handoff so the audience survives the gap. ## Core Features & Use Cases - Cadence posture selection: Chooses among dormant-but-open, occasional pulse, continuous light, or continuous heavy based on who actually has quiet-months hours, with a named owner and a dated dormancy notice. - Attendee-to-participant conversion: Designs re-engagement touchpoints and participation ladders re-scoped to an annual edition cycle, with asynchronously climbable rungs and consent gates on public naming. - Community asset handoff: Produces a dated ownership-transfer document covering platform accounts, admin roles, member list, archive, invite links, and the member-list retention decision. - Use Case: Your annual conference Discord is dead eleven months a year and the founding organizer who owns the Slack workspace is stepping down. The Skill recommends a dormant-but-open posture with a dated notice, a single re-engagement touchpoint timed to next edition's opening, and a one-page access-transfer document executed before she leaves. ## Quick Start Ask the assistant to write a between-editions community plan for your annual conference, including cadence posture, conversion mechanism, and platform handoff.

Frequently Asked Questions about event-community-building

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I keep my conference community active between editions?

Choose a cadence posture matched to who has recurring quiet-months hours: dormant-but-open with a dated notice, an occasional pulse, or continuous programming. Name a single owner, since a cadence with no owner lapses by month three.

How do I get last year's attendees to come back next edition?

Send one re-engagement touchpoint timed to the next edition's opening that references the past edition, makes one cheap ask that is not buying, and is signed by a person. For deeper commitment, build a participation ladder whose rungs are climbable asynchronously.

What should a community platform handoff include when an organizer leaves?

Transfer ownership of record first, add a second admin who is neither party, and write a one-page inventory of accounts, roles, invite links, and the member list with holder-today and holder-after per row. Restate the member-list retention decision and date the document with a review date.

Should our event's Discord go dormant or stay programmed year-round?

Dormant-but-open is the default: freeze programming, keep the archive and member list intact, and post one dated notice with a named owner and working conduct route. Continuous programming is only viable with a funded moderation roster and compounding editions.

Can we let local groups run chapters under our event's brand?

Keeping local cohorts warm on your own surface is in scope: per-city threads, a named local member, the same content feed. Licensing the brand to independently-run teams is a governance gap this Skill explicitly declines and routes elsewhere.

Why is auto-enrolling ticket buyers into the community a bad idea?

Ticketing consent covers a different purpose than community membership, so auto-enrollment manufactures the membership number and misuses the consent basis. Offer an opt-in path instead and report only genuinely opted-in members to sponsors.