home / skills / lycfyi / community-agent-plugin / community-patterns

This skill applies community management patterns to monitor health, identify risks, and guide actions across Discord and Telegram communities.

npx playbooks add skill lycfyi/community-agent-plugin --skill community-patterns

Review the files below or copy the command above to add this skill to your agents.

Files (2)
SKILL.md
3.3 KB
---
name: community-patterns
description: >
  Community management best practices and patterns. Automatically loaded
  when handling community-related tasks to provide domain expertise.
---

# Community Management Patterns

Domain knowledge for effective community management across platforms.

## Healthy Community Indicators

### Engagement Metrics
- **Activity Level**: Regular posting from diverse members (not just a few)
- **Response Rate**: Questions get answered within 24 hours
- **Conversation Depth**: Threads with multiple replies, not just one-off posts
- **New Member Participation**: New members feel comfortable contributing

### Quality Signals
- **Positive Sentiment**: Supportive, constructive discussions
- **On-Topic Focus**: Conversations stay relevant to community purpose
- **Knowledge Sharing**: Members help each other, share resources
- **Organic Growth**: Steady new members through word-of-mouth

## Warning Signs

### Activity Issues
- **Declining Volume**: Week-over-week decrease in messages
- **Concentration**: 80%+ of messages from <5% of members
- **Ghost Town Hours**: Long periods with no activity
- **Unanswered Questions**: Help requests going ignored

### Quality Issues
- **Negativity Trends**: Increasing complaints, frustration
- **Off-Topic Drift**: Conversations veering from community purpose
- **Conflict Patterns**: Repeated disagreements between same members
- **Spam/Low-Quality**: Bot posts, memes dominating discussion

## Response Guidelines

### When Engaging Community
- Acknowledge questions within 24 hours (even if just "looking into it")
- Use inclusive language ("we", "our community")
- Tag relevant members who might help with specific questions
- Celebrate community wins and member contributions

### When Moderating
- Address issues privately first when possible
- Be consistent in applying community guidelines
- Explain reasoning behind moderation decisions
- Focus on behavior, not personal attacks

### When Growing Community
- Welcome new members personally
- Create low-barrier entry points (intro threads, simple questions)
- Highlight valuable contributions to encourage more
- Connect members with shared interests

## Metric Benchmarks

| Metric | Healthy | Warning | Critical |
|--------|---------|---------|----------|
| Weekly Active % | >25% | 10-25% | <10% |
| Response Time | <24h | 24-72h | >72h |
| Unanswered Rate | <10% | 10-30% | >30% |
| Member Concentration | <50% | 50-80% | >80% |
| Week-over-Week Growth | Positive | Flat | Negative 3+ weeks |

## Platform-Specific Notes

### Discord
- Use threads to organize long discussions
- Leverage roles for permissions and recognition
- Pin important messages in channels
- Use Discord Events for community activities

### Telegram
- Use topics in groups for organization
- Schedule messages for optimal timezone coverage
- Use polls for quick community feedback
- Pin announcements in group description

## Report Interpretation

When reviewing health reports:

1. **Look at trends, not just snapshots** - A declining healthy score is worse than a stable warning score
2. **Consider context** - Holiday weeks, platform changes affect metrics
3. **Prioritize actionable items** - Focus on recommendations you can actually implement
4. **Track over time** - Compare reports week-over-week to measure improvement

Overview

This skill provides community management best practices and operational patterns for healthy, sustainable communities across Discord and Telegram. It supplies indicators, warning signs, response guidelines, platform-specific tactics, and metric benchmarks to support monitoring, moderation, and growth. The skill loads automatically for community-related tasks to provide domain expertise and actionable recommendations.

How this skill works

The skill inspects engagement metrics, sentiment signals, message concentration, response times, and growth trends to assess community health. It maps observed data to benchmarks (healthy, warning, critical) and recommends targeted actions for engagement, moderation, and onboarding. Platform-specific guidance for Discord and Telegram helps adapt tactics to each environment.

When to use it

  • When analyzing weekly or monthly community health reports
  • When investigating declines in activity, growth, or sentiment
  • When designing onboarding flows, welcome messages, or intro threads
  • When responding to conflicts, spam, or repeated moderation issues
  • When planning community events, polls, or timezone-aware schedules

Best practices

  • Acknowledge questions within 24 hours, even if only to say you’re investigating
  • Favor inclusive language and celebrate member contributions publicly
  • Address moderation privately first, explain decisions, and stay consistent
  • Create low-barrier entry points for new members (intro threads, simple prompts)
  • Use threads/topics and pins to keep long discussions organized and discoverable
  • Track trends over time; prioritize actionable fixes that can be implemented quickly

Example use cases

  • Detect rising member concentration and recommend outreach to quieter members
  • Flag increasing unanswered rate and suggest volunteer responder rotations
  • Recommend using Discord threads and roles to structure a high-traffic channel
  • Advise scheduling Telegram announcements for target timezones and using polls
  • Interpret a health report showing flat growth and propose onboarding improvements

FAQ

What core metrics should I monitor first?

Start with weekly active percentage, response time, unanswered rate, and member concentration to get a quick sense of health.

How do I prioritize interventions from a health report?

Focus on trends and high-impact, low-effort actions: improve response times, welcome new members, and reduce message concentration before large structural changes.