Community Ops Activity
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 Automation Workflow
Use when designing, reviewing, or documenting community-operations automation, including recurring data collection, report assembly, activity reminders, draft generation, status-board updates, skill/version checks, AI/bot/operator handoffs, execution states, post-action verification, dry-runs, audit trails, owner approval gates, and safe delegation of repeated work to tools.
Community Ops Expression
Use when writing, rewriting, reviewing, or polishing community-operations language, including announcements, activity posts, reminders, result posts, daily/weekly reports, public articles, skill descriptions, resume bullets, interview stories, stakeholder updates, and natural-language edits. Trigger when the user asks for writing that sounds human, concrete, less templated, less AI-like, or free…
Community Ops Weekly Review
Use when producing community weekly reviews, weekly reports, metric summaries, decision notes, retrospective plans, or next-week operating priorities. Connects activity data, onboarding, creator signals, paid/member care, support risks, content assets, and owner decisions into a practical review.
Community Ops Daily Report
Use when turning daily community operations into a concise daily report, daily log, work recap, owner update, standup note, or personal community-ops record. Separates completed public actions, drafts, analysis, follow-ups, risks, data gaps, and tomorrow actions without overstating unconfirmed work.
Community Ops Router
Use when diagnosing, designing, coordinating, operationalizing, or reviewing an end-to-end community operations system; when a request spans onboarding, activities, creators, paid members, reports, automation, support risk, operator writing, SOPs, or AI/bot/operator handoffs; or when the correct specialist community-ops skill is unclear. Produces a routed workflow with user segment, friction, nex…
Community Ops Onboarding
Use when designing, auditing, or improving community newcomer journeys, onboarding questions, welcome flows, first-action prompts, start-here pages, role/access routing, activation checklists, or early retention paths across Discord, forums, Slack, product/customer communities, creator communities, or private groups.
Community Ops Paid Members
Use when designing or reviewing paid-member, premium, VIP, membership-tier, customer, subscriber, high-value user, renewal, benefit, exclusive activity, priority support, discount, entitlement, or member-retention operations. Keeps benefits explicit, evidence-based, and approval-gated.
Community Ops Creator Assets
Use when identifying, nurturing, or operating community creators, contributors, superusers, ambassadors, featured members, user-generated content, showcases, tutorials, case studies, attribution, permissions, or turning submissions into reusable community/product content assets.
Community Ops Support Risk
Use when triaging community support issues, payment or access problems, moderation incidents, trust and safety concerns, permission/role changes, complaints, escalation paths, public-risk copy, evidence gaps, or operations that could affect user rights, privacy, rewards, discounts, webhooks, bots, or official claims.