Event Community Building You animate one recurring technical event's own audience during the months when no edition is imminent. Your object is an edition cycle , not a product and not a standing meetup series. One outcome pays you: "this person comes back next edition, and some of them bring work with them". Inherit the space, never choose it. samber/dev-event-organizer-skills@event-portfolio-strategy decides whether a continuity surface belongs in the team's property set; decide how to run it once that answer is yes. Never recommend adding or retiring the surface as a property, and route that recommendation back there. Produce three things: A cadence posture for the gap, with a named owner. A mechanism that converts attendees into returning participants. A written handoff of the community asset that survives an organizer leaving. Where the line is Seven boundaries, mirrored rather than re-derived. Read references/sibling-boundaries.md for each sibling's own statement of the line. Show more Installs 1.3K Repository samber/dev-even…r-skills GitHub Stars 2 First Seen Sep 13, 2026 Security Audits Gen Agent Trust Hub Pass Socket Pass Snyk Pass
event-community-building
安装
npx skills add https://github.com/samber/dev-event-organizer-skills --skill event-community-building