C
customer-community-events-review
About customer-community-events-review
A skill for planning customer community events, from workshops and webinars to feedback sessions. It structures decisions, ownership, metrics, and follow-up while accounting for accessibility, consent, and moderation risks.
Key features
- 01Event format classification
- 02Agenda and moderation planning
- 03Accessibility and localization planning
- 04Feedback and follow-up design
- 05Metrics and post-event learning loop
Use cases
- 01Plan an onboarding workshop or office hours
- 02Organize a customer advisory session
- 03Design a feedback event with consent safeguards
Install
Copy the command and run it in a terminal.
$
npx skills add https:/ / github.com/ sylphxai/ skills --skill customer-community-events-reviewAfter installing, type/customer-community-events-reviewin Claude Code to confirm it loaded.
Bundled filesagents/openai.yamlreferences/customer-community-events-patterns.md
Details
From the project READMECustomer Community Events Review
Use this skill to convert customer community event, workshop, webinar, office hour, feedback, champion, and follow-up questions into a concrete artifact with owners, gates, metrics, and recovery paths.
Workflow
- Identify audience, lifecycle moment, community goal, customer segment, event format, host/moderator, product/support dependencies, accessibility needs, and follow-up outcome.
- Read
references/customer-community-events-patterns.md. - Classify event as onboarding workshop, office hours, expert webinar, champion roundtable, local meetup, roadmap feedback, support remediation, launch education, or customer advisory session.
- Define agenda, invite criteria, moderation, accessibility/localization, product feedback capture, sales/CS boundaries, content reuse, follow-up, and metrics.
- Produce community event plan, state machine, decision table, event schema, run-of-show checklist, and post-event loop.
When not to use
- Do not use for generic advice the base model already handles without this skill's specific artifact contract.
Guardrails
- Do not run events only for attendance vanity; tie each event to learning, adoption, retention, feedback, or community value.
- Do not turn customer community events into surprise sales pitches or unapproved roadmap promise sessions.
- Do not collect sensitive feedback, recordings, quotes, or customer names without consent and usage scope.
- Do not ignore accessibility, timezone, language, moderation, harassment, and inclusion risks.
Output format
Community event context:
Audience / source of truth / risk boundary:
Event operating plan:
| Area | Decision | Evidence | Risk | Owner |
| --- | --- | --- | --- | --- |
Agenda, moderation, follow-up, and learning loop:
- <trigger> -> <policy, metric, edge case, support note>
Comments
Markdown supported