Skills/Community Metrics/SKILL.md
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.
npx skillsauth add studio-self/tribalism community-metricsInstall 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 analytics and measurement. Your goal is to help users track the metrics that matter, avoid vanity metrics, and build reporting that connects community activity to business outcomes.
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.
Gather this context (ask if not provided):
Most community managers track vanity metrics (total members, total posts) that don't tell you if the community is healthy.
Vanity metrics: Make you feel good but don't drive decisions. Health metrics: Tell you if the community is working. Business metrics: Connect community to organizational value.
| Metric | Formula | Healthy Range | |--------|---------|--------------| | DAU/MAU ratio | Daily active / Monthly active | 15-30% | | Posts per active member | Total posts / Active members | 2-5/month | | Reply rate | Threads with replies / Total threads | >60% | | Average replies per thread | Total replies / Total threads | >3 | | Content creation ratio | Members who post / Total active | >10% |
| Metric | Formula | Healthy Range | |--------|---------|--------------| | Net member growth | New members - Churned members | Positive | | Activation rate | Active in week 1 / Joined | >50% | | 30-day retention | Active at day 30 / Joined | >40% | | 90-day retention | Active at day 90 / Joined | >25% | | Referral rate | Members who invited / Total active | >5% |
| Metric | What It Measures | |--------|-----------------| | Time to first response | How quickly questions get answered | | Member-to-member ratio | % of engagement that's peer-to-peer vs. team-initiated | | Unique contributors/week | How many distinct people are contributing | | Lurker-to-participant conversion | % of readers who become posters over time | | Returning member rate | % of active members from last period who are active again |
These connect community to outcomes stakeholders care about.
| Metric | How to Measure | |--------|---------------| | Support deflection | Questions answered in community vs. support tickets | | Product feedback generated | Ideas/bugs surfaced through community | | Feature adoption | Community members vs. non-members using new features | | NPS lift | NPS of community members vs. non-members |
| Metric | How to Measure | |--------|---------------| | Community-influenced signups | Signups attributed to community content or referrals | | Content generated | External content created from community discussions | | Brand awareness | Community mentions, external shares, earned media | | SEO value | Traffic to public community content |
| Metric | How to Measure | |--------|---------------| | Retention lift | Churn rate of community members vs. non-members | | Expansion revenue | Upsell rate of community members vs. non-members | | Time to value | Onboarding speed of community members vs. non-members | | Customer satisfaction | CSAT of community members vs. non-members |
Community ROI = (Value Generated - Community Cost) / Community Cost
Value Generated =
Support deflection savings ($X per ticket deflected)
+ Revenue from community-influenced conversions
+ Retention lift (reduced churn * avg revenue per customer)
+ Content value (equivalent ad spend or production cost)
+ Product improvement value (features shipped from community feedback)
Community Cost =
Team salaries + Platform costs + Event costs + Tool costs
Named ROI examples:
Typical cost benchmarks:
Quick check on community health. 5 minutes to review.
## Weekly Community Pulse — Week of [date]
### Key Numbers
- Active members: [X] (vs. [X] last week)
- New members: [X]
- Posts/messages: [X]
- Events held: [X] (attendance: [X])
### Highlights
- [Notable discussion or achievement]
- [Member win or contribution]
### Concerns
- [Any issues needing attention]
### This Week's Focus
- [Priority for the coming week]
Connects community metrics to business outcomes.
## Monthly Community Report — [Month Year]
### Summary
[2-3 sentence overview of community health and trends]
### Growth
| Metric | This Month | Last Month | Trend |
|--------|-----------|------------|-------|
| Total members | | | |
| New members | | | |
| Activation rate | | | |
| 30-day retention | | | |
### Engagement
| Metric | This Month | Last Month | Trend |
|--------|-----------|------------|-------|
| DAU/MAU | | | |
| Posts | | | |
| Active contributors | | | |
| Avg response time | | | |
### Business Impact
| Metric | This Month | Last Month | Trend |
|--------|-----------|------------|-------|
| Support tickets deflected | | | |
| Community-sourced feedback | | | |
| Community-attributed signups | | | |
### Top Wins
1. [Win with business context]
2. [Win with business context]
### Challenges & Plans
- [Challenge and what you're doing about it]
### Next Month Priorities
1. [Priority]
2. [Priority]
Deep dive connecting community to business strategy.
Objective: What you want to achieve (qualitative) Key Results: How you'll measure it (quantitative)
Objective: Build an active, self-sustaining community
Objective: Drive measurable business impact through community
| Tool | Best For | Works With | |------|----------|-----------| | Platform native analytics | Basic engagement data | Your platform | | Common Room | Unified community analytics | Multi-platform | | Orbit | Member journey tracking | Developer communities | | Google Analytics | Website/public community traffic | Web-based communities | | Custom dashboards (Looker, Metabase) | Advanced cross-platform analysis | API-accessible platforms |
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.