community-ops-activity

name	community-ops-activity
description	Use when designing, reviewing, or packaging community activities, campaigns, challenges, contests, AMAs, events, reminders, submissions, voting, rewards, result announcements, or activity retrospectives for any community platform. Produces operator-ready activity mechanics with user segment, rules, submission proof, feedback loop, reward boundary, reminder plan, and review metrics.

Community Ops Activity

Use this skill for community activities and campaigns. The job is to turn an idea into a repeatable participation loop, not just an announcement.

Project Inputs

The skill provides the activity-design method, not a ready-made community's rules. For an operator-ready activity, get these values from the user or an approved project source:

• goal, target segment, and eligibility;
• one participation action or theme;
• start, deadline, and timezone;
• entry surface, submission surface, and valid proof format;
• feedback, review, or voting method;
• reward or showcase status: confirmed, pending, or none;
• reminder timing and delivery surfaces;
• relevant content, safety, age, regional, or product constraints;
• owner and approval boundary.

The user may provide only part of this list during ideation. Keep missing values as [owner to confirm] and explain which ones block launch. Do not copy dates, rewards, channels, eligibility, rules, or tools from repository examples or another community. Do not ask for credentials or raw private messages.

First Move

Classify the activity:

1. Activation: get new or quiet users to make a first action.
2. Creation: collect works, posts, screenshots, demos, tutorials, or examples.
3. Discussion: prompt opinions, AMAs, office hours, polls, or topic threads.
4. Recognition: showcase creators, winners, members, or helpful answers.
5. Conversion: bring users back to product, paid value, website, event page, or support flow.

If the user names a project, platform, reward, role, or public channel, inspect the source context before drafting. Keep public posts, DMs, mentions, rewards, discounts, winner lists, channel/role/permission changes, bot/webhook actions, and official claims owner-confirmed.

Activity Loop

Design every activity as:

segment -> hook -> action -> proof/submission -> feedback/vote -> reward/showcase -> follow-up -> review

For each step, define:

• target segment;
• one user action;
• where the action happens;
• exact submission/proof format;
• timing and reminder points;
• feedback, vote, review, or support path;
• reward/showcase boundary;
• success evidence.

Output Pattern

**Activity Goal**
[One concrete outcome.]

**Target Segment**
[New users / creators / paid members / inactive users / product users / etc.]

**Participation Loop**
entry -> action -> proof -> feedback/vote -> reward/showcase -> next action

**Mechanics**
| Item | Decision |
|---|---|
| Theme | ... |
| Who can join | ... |
| Submission format | ... |
| Deadline | ... |
| Feedback/vote | ... |
| Reward/showcase | ... |
| Owner gate | ... |

**Draft Copy Blocks**
- Launch: ...
- Reminder: ...
- Last call: ...
- Result/showcase: ...

**Review Metrics**
- valid submissions;
- first-time participants;
- repeat participants;
- showcase-ready works;
- product/website/account signals;
- support or rule issues.

Quality Bar

Reject activity ideas that only say "increase engagement". Tie the activity to a user action and proof. If rewards, eligibility, safety rules, or target channels are missing, mark them as owner confirmation needed instead of inventing them.

Write direct copy. Avoid repeated not X but Y style contrast. Use specific actions: join, create, submit, vote, react, comment, claim, review, showcase. Keep every copy block in draft status until the owner confirms the target and send.