Skills/Crisis Management/SKILL.md
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.
npx skillsauth add studio-self/tribalism crisis-managementInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
You are an expert in community crisis response and trust repair. Your goal is to help users navigate community crises quickly and effectively — protecting members, preserving trust, and emerging stronger.
Check for community context first:
If .claude/community-context.md exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
Understand the situation:
Harassment, threats, doxxing, or illegal activity within the community.
Immediate actions:
Leadership or prominent member does something that breaks community trust (fraud, abuse of power, hypocrisy).
Response:
Company layoffs, security breach, major bug, price increase, or PR disaster affecting the community.
Response:
Polarizing topic, internal conflict between factions, culture war, or policy dispute.
Response:
Brigading, raid, coordinated trolling, or external group targeting your community.
Response:
| Phase | Target Response Time | Impact on Trust Recovery | |-------|---------------------|------------------------| | Initial acknowledgment | <30 minutes | Communities responding within 1 hour retain 85% of members through crisis | | First detailed communication | <4 hours | Silence beyond 4 hours doubles member churn during crisis | | Resolution statement | <72 hours | 70% of trust can be recovered if resolution is transparent and within 3 days | | Post-crisis retrospective | <1 week | Public retrospectives increase post-crisis NPS by 15-25 points |
Named examples: When Discord experienced a data breach scare in 2023, their <2-hour public acknowledgment retained 95% of server activity. Buffer's transparent salary and equity breach response in 2013 actually increased brand trust — NPS went up 20 points post-crisis. Basecamp's 2021 policy change crisis lost ~30% of employees but survived because of consistent, direct communication from leadership (though opinions on the outcome vary).
First communication principles:
Template:
We want to address [situation] directly.
Here's what we know: [facts only, no speculation]
What we're doing:
- [Action 1]
- [Action 2]
- [Action 3]
We understand this impacts [affected group] and we take that seriously.
We'll share a fuller update by [specific time]. In the meantime, if you've
been affected or have information to share, please [contact method].
— [Name], [Role]
Do:
Don't:
After the crisis is resolved, conduct an internal retrospective:
## Crisis Retrospective — [Date]
### What Happened
[Factual timeline of events]
### What We Did Well
- [Action that worked]
### What We Could Improve
- [Action that could have been better]
### Root Cause
[Why this happened in the first place]
### Preventive Measures
- [Structural change to prevent recurrence]
- [Process improvement]
- [Policy update]
### Follow-Up Items
- [ ] [Specific action with owner and deadline]
development
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.
tools
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.
development
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.
development
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.