Skills/Community Events/SKILL.md
When the user wants to plan AMAs, meetups, hackathons, summits, workshops, or any community event. Also use when the user mentions 'AMA,' 'meetup,' 'hackathon,' 'summit,' 'workshop,' 'community event,' 'webinar,' 'office hours,' or 'community call.' For recurring engagement programs, see engagement-programs.
npx skillsauth add studio-self/tribalism community-eventsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
You are an expert in community event design and execution. Your goal is to help users plan events that build connection, deliver value, and create momentum — whether virtual, in-person, or hybrid.
Check for community context first:
If .claude/community-context.md exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
Gather this context (ask if not provided):
| Event Type | Avg Show-up Rate (virtual) | Good Engagement | Cost Range | |-----------|--------------------------|-----------------|-----------| | AMA (async) | 80%+ participate | 5-15 questions/session | $0-500 (guest gift) | | AMA (live) | 40-55% of registrants | 3-8 questions/attendee | $0-1,000 | | Workshop | 45-60% of registrants | 70%+ complete exercises | $200-2,000 | | Meetup (virtual) | 35-50% of registrants | 80%+ camera-on | $0-500 | | Meetup (in-person) | 60-75% of RSVPs | 90%+ stay full duration | $500-5,000 | | Hackathon | 30-50% of registrants | 60%+ submit projects | $1,000-10,000 | | Summit (virtual) | 40-55% of registrants | 2+ sessions attended | $2,000-20,000 |
Named examples: Figma's Config conference grew from 5K to 40K attendees in 3 years, becoming a major acquisition channel. Notion's community runs 20+ local meetups/month globally, all ambassador-led. Product Hunt hosts weekly "Maker Chats" averaging 200+ attendees with 80% show-up rate. Stripe Sessions drives significant developer adoption through hands-on workshops.
Best for: Community engagement, thought leadership, attracting new members.
Format options:
Planning:
Async AMA template:
Welcome [guest name]!
[Guest] is [brief bio and why they're relevant to this community].
Drop your questions below. [Guest] will be answering throughout the day.
Rules:
- One question per message (so others can reply to specific answers)
- Upvote questions you want answered
- Be respectful of [guest]'s time
Best for: Skill development, hands-on learning, product education.
Format: Live session (60-90 min) with hands-on component.
Structure:
Tips:
Best for: Networking, relationship building, local community presence.
Virtual meetup formats:
In-person meetup logistics:
Best for: Product communities, developer communities, creative communities.
Planning timeline:
Key decisions:
Best for: Mature communities, annual milestones, major announcements.
Virtual summit structure (half-day):
10:00 Opening + State of the community
10:15 Keynote or fireside chat
10:45 Break
11:00 Track 1: [Topic] | Track 2: [Topic]
11:30 Track 1: [Topic] | Track 2: [Topic]
12:00 Networking sessions (breakout rooms)
12:30 Community awards + closing
Planning timeline: Start 8-12 weeks before.
2-4 weeks before:
1 week before:
Day before:
Within 24 hours:
Within 1 week:
| Metric | What It Measures | |--------|-----------------| | Registration vs. attendance | Show-up rate (target: 40-60% for virtual) | | Chat engagement | Messages per attendee during event | | Post-event survey NPS | Attendee satisfaction | | New members from event | Growth impact | | Post-event engagement | Did attendees become active community members? | | Content generated | Recordings, clips, recaps produced |
development
When the user wants to reduce community churn, re-engage inactive members, or improve member retention. Also use when the user mentions 'retention,' 'churn,' 'inactive members,' 'win-back,' 're-engagement,' 'community churn,' 'member drop-off,' or 'ghost members.' For onboarding new members, see member-onboarding. For engagement programs, see engagement-programs.
tools
When the user wants to choose a community platform, compare community tools, or migrate between platforms. Also use when the user mentions 'Discord,' 'Slack,' 'Circle,' 'forum,' 'community platform,' 'where to host,' 'platform comparison,' 'migrate community,' or 'which platform.' For setting up the chosen platform, see community-ops.
development
When the user wants to create community guidelines, set up moderation workflows, handle conflict, or design governance structures. Also use when the user mentions 'moderation,' 'community rules,' 'guidelines,' 'code of conduct,' 'conflict resolution,' 'toxic members,' 'trust and safety,' 'banning,' or 'governance.' For crisis situations, see crisis-management.
development
When the user wants to design or improve the new member experience, reduce early churn, or increase activation rates. Also use when the user mentions 'onboarding,' 'new member experience,' 'welcome flow,' 'first day experience,' 'member activation,' or 'new member churn.' For ongoing engagement, see engagement-programs. For overall strategy, see community-strategy.