
When the user wants to launch a new community from scratch, plan a community launch, or relaunch an existing community. Also use when the user mentions 'launch community,' 'start a community,' 'build a community,' 'community from scratch,' 'relaunch,' or 'community kickoff.' For overall strategy, see community-strategy. For growth after launch, see community-growth.
When the user wants to set up community tooling, build automation workflows, design team structures, or operationalize community management. Also use when the user mentions 'community ops,' 'community tools,' 'automation,' 'community workflow,' 'community team,' 'community manager hiring,' 'tech stack,' or 'community operations.' For platform selection, see platform-selection.
When the user wants to design community rituals, recurring events, challenges, or content programs to drive engagement. Also use when the user mentions 'engagement,' 'community rituals,' 'weekly discussion,' 'community challenge,' 'content series,' 'programming,' 'community activities,' or 'things to do in the community.' For one-off events, see community-events. For content strategy, see community-content.
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.
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.
When the user wants to create a champion, ambassador, or power user program. Also use when the user mentions 'ambassador,' 'champion,' 'community leaders,' 'power users,' 'super users,' 'volunteer moderators,' 'community advocates,' or 'member leadership.' For referral programs, see community-growth. For moderation, see moderation-governance.
When the user wants to create or update their community context document. Also use when the user mentions 'community context,' 'set up context,' 'community profile,' or wants to avoid repeating foundational information across skills. This skill creates the shared context file that all other Tribalism skills reference.
When the user wants to define, shape, or evolve their community's culture, values, norms, or identity. Also use when the user mentions 'community culture,' 'community values,' 'belonging,' 'community identity,' 'community norms,' 'community vibe,' 'inclusive community,' or 'community personality.' For moderation and rules, see moderation-governance.
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.
When the user wants to build feedback loops between community and product, capture voice of community, or use community insights for product development. Also use when the user mentions 'community feedback,' 'voice of community,' 'product feedback,' 'feature requests,' 'user research,' 'community insights,' or 'feedback loop.' For community health metrics, see community-metrics.
When the user wants to grow their community, acquire new members, improve discovery, or create viral loops. Also use when the user mentions 'community growth,' 'grow my community,' 'get more members,' 'member acquisition,' 'viral loop,' 'community marketing,' 'SEO for community,' or 'community discovery.' For community-as-business-growth, see community-led-growth. For referral programs, see ambassador-program.
When the user wants to use community as a business growth engine, implement community-led growth (CLG), or connect community metrics to revenue. Also use when the user mentions 'community-led growth,' 'CLG,' 'community as growth engine,' 'community GTM,' 'community flywheel,' or 'community revenue.' For general community growth, see community-growth. For monetizing the community itself, see community-monetization.
When the user wants to monetize their community through paid memberships, sponsorships, premium tiers, or other revenue models. Also use when the user mentions 'paid community,' 'monetize community,' 'community revenue,' 'sponsorship,' 'premium tier,' 'community subscription,' 'membership fee,' or 'community business model.' For community as a business growth engine, see community-led-growth.
When the user wants to build cross-community partnerships, co-marketing relationships, or ecosystem plays. Also use when the user mentions 'community partnership,' 'cross-community,' 'co-marketing,' 'collaboration,' 'ecosystem,' 'partner community,' or 'community collab.' For ambassador programs, see ambassador-program.
When the user wants to plan an overall community strategy, define community architecture, or create a community roadmap. Also use when the user mentions 'community strategy,' 'community plan,' 'community roadmap,' 'community model,' or 'community architecture.' For launching a new community, see community-launch. For growth tactics, see community-growth.
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.
When the user wants to build or manage a developer community, DevRel program, open source community, or technical community. Also use when the user mentions 'developer community,' 'DevRel,' 'developer relations,' 'open source community,' 'developer experience,' 'API community,' 'docs community,' or 'technical community.' For general community strategy, see community-strategy.
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.
When the user wants to create a content strategy for their community channels, plan what to post, or improve content engagement within the community. Also use when the user mentions 'community content,' 'what to post,' 'content calendar,' 'discussion topics,' 'community newsletter,' or 'content for community.' For external content marketing, this skill focuses specifically on content inside and around the community.
When the user wants to measure community health, build dashboards, create reports, or understand what metrics to track. Also use when the user mentions 'community metrics,' 'community analytics,' 'engagement metrics,' 'community health,' 'community ROI,' 'community report,' 'dashboard,' or 'KPIs for community.' For growth-specific metrics, see community-growth.
When the user needs to handle a community crisis, PR issue, trust violation, safety incident, or major controversy. Also use when the user mentions 'crisis,' 'community blowup,' 'PR issue,' 'trust violation,' 'safety incident,' 'controversy,' 'community backlash,' 'damage control,' or 'toxic situation.' For everyday moderation, see moderation-governance.
When the user wants to apply behavioral science, psychology, or mental models to community building. Also use when the user mentions 'community psychology,' 'behavioral science,' 'why people engage,' 'motivation,' 'belonging,' 'social dynamics,' 'group psychology,' or 'human behavior in communities.' This skill provides the scientific foundation that all other Tribalism skills build on.