mcpField
C
community-launch-ops-review

community-launch-ops-review

github.com/sylphxaiMarketing & growth146 installsUpdated today
Repository

About community-launch-ops-review

A skill for teams planning and reviewing community launches. It turns community goals and constraints into an operations plan, channel map, moderation ladder, content calendar, and feedback loop.

Key features

  1. 01Community purpose and audience review
  2. 02Onboarding, roles, and channel planning
  3. 03Support and feedback routing
  4. 04Moderation and safety planning
  5. 05Launch plan and health metrics

Use cases

  1. 01Preparing a product community launch
  2. 02Planning channels and member roles
  3. 03Defining moderation coverage and escalation
  4. 04Separating community feedback from support

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/sylphxai/skills --skill community-launch-ops-review

After installing, type/community-launch-ops-reviewin Claude Code to confirm it loaded.

Bundled filesagents/openai.yamlreferences/community-launch-patterns.md

Details

From the project README

Community Launch Ops Review

Use this skill to convert a high-stakes product decision into a concrete, measurable, reviewable operating artifact.

Workflow

  1. Identify community purpose, audience, platform, membership model, moderation risk, launch moment, and owner capacity.
  2. Read references/community-launch-patterns.md.
  3. Map onboarding, roles, channels, announcements, support routing, feedback capture, moderation, events, and health metrics.
  4. Separate community, support, marketing, creator, and beta-test jobs so one channel does not become chaos.
  5. Produce launch ops plan, channel IA, moderation ladder, content calendar, and feedback 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 launch a community without active owner coverage and moderation policy.
  • Do not use community as a substitute for support SLAs unless expectations are explicit.
  • Avoid vanity metrics that ignore retention, helpfulness, safety, and signal quality.
  • Protect members from harassment, spam, scams, spoilers, and private-data exposure.

Output format

Community context:
Purpose / audience / platform:

Ops plan:
| Area | Design | Owner | Cadence | Risk | Metric |
| --- | --- | --- | --- | --- | --- |

Channel and role map:
- <channel/role> -> <job/rule/escalation>

Launch calendar and feedback loop:
- <date/content/event/learning>

Comments

Markdown supported