Community Manager
Your community director who builds thriving, engaged communities that turn members into advocates and customers.
What This Agent Does
The Problem: You launched a Discord server. Or a Slack community. You’ve got 200 members. Most are lurkers. A few power users dominate conversations. New members join and never say a word. You’re not sure if the community is healthy or dying slowly.
Communities feel like work. Moderating, engaging, answering the same questions repeatedly, dealing with spam and negativity. You wanted a thriving community. You got a ghost town with occasional drama.
The Solution: Community Manager is your experienced community director who analyzes sentiment, drafts engagement strategies, creates moderation systems, surfaces insights, generates FAQs from common questions, and builds programs that turn lurkers into active, valuable members.
Think of it as having a dedicated community professional who understands what makes online communities thrive.
Quick Start
30-second example - analyze community health:
You: "Analyze our Discord community health"
community-manager: Running community audit...
[Analyzing: Last 30 days of Discord activity]
COMMUNITY HEALTH REPORT
Overview:
→ Total members: 487
→ Active members (30d): 87 (18% activity rate)
→ Messages sent: 2,340
→ Average response time: 4.2 hours
→ Sentiment score: 6.8/10 (Positive)
HEALTH METRICS:
Engagement (FAIR):
→ Daily active users: 12-18 (target: 40+)
→ Messages per active user: 26.9 (good)
→ New member retention (7d): 22% (target: 40%+)
→ Power user concentration: 68% (too high - 5 users dominate)
Sentiment (POSITIVE):
→ Positive mentions: 62%
→ Neutral mentions: 31%
→ Negative mentions: 7%
→ Trending positive: Product features, support quality
→ Trending negative: Missing features, bugs
Response Quality (GOOD):
→ Questions answered: 91%
→ Average response time: 4.2 hours
→ Resolution rate: 78%
→ Community-answered: 64% (good peer support)
Growth (SLOW):
→ New members (30d): 34
→ Invited by members: 8 (23%)
→ Retention rate: 22% (target: 40%+)
→ Churn (30d): 12 members left
CHANNEL ACTIVITY:
Most active:
1. #general: 847 messages (36%)
2. #support: 623 messages (27%)
3. #feature-requests: 312 messages (13%)
Least active:
1. #off-topic: 18 messages (<1%)
2. #showcase: 24 messages (1%)
3. #job-board: 31 messages (1%)
ISSUES IDENTIFIED:
🔴 High Priority:
1. New member onboarding broken
→ 78% of new members never send first message
→ No welcome flow or intro prompt
→ New members don't know where to start
2. Power user dominance
→ 5 users send 68% of messages
→ New voices drowned out
→ Creates "insider club" feeling
3. Support response gap
→ Questions between 10pm-8am go unanswered
→ Creates 8-12 hour response delays
→ Frustration builds when issues urgent
🟡 Medium Priority:
4. Dead channels dilute engagement
→ 3 channels have < 5 messages per week
→ Makes community feel inactive
→ Recommend archiving or merging
5. Missing FAQ reduces efficiency
→ Same 8 questions asked repeatedly
→ Team answering same things daily
→ Wastes time, creates documentation gap
6. No community events
→ Zero scheduled events last 30 days
→ No office hours, AMAs, or meetups
→ Reduces engagement opportunities
SENTIMENT ANALYSIS:
Top Concerns (from members):
1. "Missing X feature" (47 mentions)
→ Feature requests: Dark mode, API docs, webhooks
→ Response: Acknowledge, add to roadmap visibility
2. "Bug in Y" (28 mentions)
→ Known issues being discussed repeatedly
→ Response: Create known-issues channel with status
3. "When will Z ship?" (19 mentions)
→ Roadmap visibility poor
→ Response: Share quarterly roadmap updates
Positive Feedback Themes:
1. "Support team is amazing" (31 mentions)
→ Team responsiveness praised
→ Opportunity: Highlight support team members
2. "Love the product" (24 mentions)
→ Strong product-market fit signals
→ Opportunity: Gather testimonials
3. "Community is helpful" (18 mentions)
→ Peer support working well
→ Opportunity: Recognize helpful members
POWER USERS (Top Contributors):
1. @sarah_dev (412 messages)
→ Helpful, answers questions, positive tone
→ Recommendation: Make moderator, recognize publicly
2. @mike_tech (287 messages)
→ Shares tips, creates tutorials, engaged
→ Recommendation: Feature in newsletter, offer swag
3. @alex_founder (198 messages)
→ Provides feedback, helps others, advocates
→ Recommendation: Early access to features, advisory role
4. @jamie_coder (156 messages)
→ Active but sometimes negative tone
→ Recommendation: 1-on-1 conversation, address concerns
5. @chris_pm (134 messages)
→ Asks good questions, provides use cases
→ Recommendation: Product beta tester, case study candidate
LURKER ANALYSIS:
Why members don't engage:
→ 47% never introduced themselves
→ 38% intimidated by active users
→ 31% don't know what to say
→ 22% just browsing for information
RECOMMENDED ACTIONS:
Immediate (This Week):
1. Implement welcome flow for new membersWelcome message: “Hey @new_member! 👋
Welcome to the [Product] community!
Quick intro prompts: → What brings you here? → What are you building? → How can we help?
Not sure where to start? Drop a 👋 in #introductions!”
2. Create #faqs channel with top 10 questions
(Auto-generated from common questions - see below)
3. Archive inactive channels (#off-topic, #job-board)
→ Reduces visual clutter
→ Concentrates activity
4. Set up auto-response for common questions
→ "Check #faqs for answers to common questions"
→ Reduces repetitive support
Short-Term (Next 30 Days):
5. Launch monthly community events:
→ Week 1: Office hours (live Q&A)
→ Week 3: Show & tell (members share projects)
→ Increases engagement, creates routine
6. Create member recognition program:
→ Highlight "Member of the Month"
→ Feature helpful members in newsletter
→ Send swag to top contributors
7. Implement tiered roles system:
→ New member → Active member → Power user → Moderator
→ Gamification encourages progression
8. Share monthly roadmap update:
→ What shipped last month
→ What's coming next month
→ Reduces "when will X ship?" questions
Long-Term (Next Quarter):
9. Build community-led initiatives:
→ Member-created tutorials
→ Community-driven feature voting
→ Peer mentorship program
10. Expand to other platforms:
→ Consider GitHub Discussions (for developers)
→ Consider Circle/Discourse (for knowledge base)
EXPECTED IMPROVEMENTS:
After implementing recommendations:
→ Activity rate: 18% → 35% (+94%)
→ New member retention: 22% → 45% (+105%)
→ Response time: 4.2h → 2.1h (-50%)
→ Power user concentration: 68% → 40% (-41%)
→ Sentiment score: 6.8 → 8.2 (+20%)
Timeline: 60-90 days to see full impact
Want me to help implement these recommendations?Capabilities
1. Sentiment Analysis
Monitor community mood and identify issues early.
Example - Weekly Sentiment Report:
community-manager: Weekly sentiment analysis...
SENTIMENT TRENDS (Dec 20-27)
Overall Sentiment: 7.2/10 (↑ +0.6 from last week)
Positive Signals:
✓ Product launch well-received (42 positive mentions)
✓ Support response time improved (praised 18 times)
✓ New feature adoption high (67 users trying it)
Negative Signals:
⚠ Pricing confusion (12 complaints)
⚠ Bug reports increasing (8 new issues)
⚠ Documentation gaps mentioned (6 times)
SENTIMENT BY TOPIC:
Product Features: 8.5/10 (Very Positive)
→ "Love the new dashboard" (14 mentions)
→ "AI features are game-changing" (9 mentions)
→ "Export functionality finally works" (7 mentions)
Support Experience: 8.1/10 (Positive)
→ "Team responded in 10 minutes" (8 mentions)
→ "Support went above and beyond" (5 mentions)
→ "Best support I've experienced" (4 mentions)
Pricing: 4.2/10 (Negative)
→ "Confused about plan differences" (6 mentions)
→ "Price increase not communicated" (4 mentions)
→ "Too expensive for small teams" (2 mentions)
Documentation: 5.8/10 (Mixed)
→ "Can't find API docs" (3 mentions)
→ "Tutorial helped a lot" (3 mentions)
→ "Need more examples" (2 mentions)
CONCERNING CONVERSATIONS:
Thread #1: Pricing change frustration
→ Location: #general
→ Sentiment: Angry
→ Participants: 8 members
→ Issue: Price increase not announced in advance
→ Action needed: Public response acknowledging mistake
Thread #2: Critical bug affecting production
→ Location: #support
→ Sentiment: Urgent/frustrated
→ Participants: 3 users affected
→ Issue: Export failing for large datasets
→ Action needed: Engineering escalation, status update
Thread #3: Feature request gaining traction
→ Location: #feature-requests
→ Sentiment: Hopeful
→ Participants: 12 members +1'ing
→ Issue: Want dark mode
→ Action needed: Add to roadmap, communicate timeline
MEMBER MOOD SHIFTS:
Members becoming negative:
→ @user123: Was positive advocate, now frustrated (pricing)
→ @user456: Active contributor, went silent (unresolved bug)
→ @user789: New member, confused (poor onboarding)
Members becoming positive:
→ @user321: Was struggling, now advocating (support helped)
→ @user654: Lurker became active (featured in newsletter)
→ @user987: Skeptical → converted (saw product update)
RECOMMENDED ACTIONS:
High Priority:
1. Address pricing confusion publicly
→ Post clarification in #announcements
→ DM affected users with explanation
2. Update on export bug
→ Share engineering progress
→ Provide workaround if available
→ Set expectations on fix timeline
Medium Priority:
3. Acknowledge dark mode requests
→ Add to public roadmap
→ Share timeline if possible
→ Thank community for input
4. Improve documentation
→ Add missing API examples
→ Create video tutorials for common tasks
5. Re-engage members going silent
→ DM to ask if everything okay
→ Offer help or 1-on-1 support call
SENTIMENT FORECAST:
If issues addressed: 7.2 → 8.5/10 (positive momentum)
If ignored: 7.2 → 5.8/10 (declining community health)
Next review: January 3, 20252. Response Drafting
Create helpful, on-brand responses to common situations.
Example - Response Templates:
community-manager: Generating response templates...
TEMPLATE LIBRARY:
1. Welcome New Member:Hey @new_member! 👋
Welcome to the [Product] community!
Great to have you here. To help us get to know you: → What brings you to [Product]? → What are you hoping to build? → Any questions to get started?
If you need help, drop a message in #support. Our team typically responds within 2 hours.
Looking forward to seeing what you create! 🚀
2. Acknowledge Bug Report:Thanks for reporting this, @user!
I’ve created a ticket and flagged it to engineering: [TICKET-123]
What we know so far: → Affects: [describe scope] → Workaround: [if available] → ETA: [timeline or “investigating”]
We’ll update you here as soon as we have more info.
In the meantime, if this is blocking you, DM me and we’ll figure out a solution. 👍
3. Handle Feature Request:Love this idea, @user!
I can see this being really useful for [use case].
I’ve added it to our feature request board: [LINK] The team reviews these quarterly when planning roadmap.
A few questions to help us prioritize: → How often would you use this? → What’s your current workaround? → How critical is this for your workflow?
If others want this too, react with 👍 to show demand!
4. Respond to Complaint:@user I hear your frustration, and I apologize for [issue].
You’re absolutely right that [acknowledge their point].
Here’s what we’re doing about it: → [Action 1] → [Action 2] → [Action 3]
This should be resolved by [timeline].
Want to jump on a quick call to discuss further? We’re here to help make this right. 🙏
5. Moderate Negative Behavior:Hey @user, quick note:
Our community guidelines ask that we keep conversations: → Respectful (even when disagreeing) → Constructive (focus on solutions) → On-topic (relevant to [Product])
I noticed [specific behavior] doesn’t align with this.
Can we reset and keep things constructive? Thanks for understanding. 🙏
[If needed: “If this continues, I’ll need to issue a warning per our moderation policy.”]
6. Celebrate Member Win:This is awesome, @user! 🎉
Love seeing what you built with [Product].
Would you be open to us: → Featuring this in our newsletter? → Sharing on our social media? → Writing a case study together?
Either way, really impressive work. Keep it up! 🚀
7. Answer Repeat Question:Great question, @user!
This comes up often, so we created a guide: [LINK]
TLDR: → [Key point 1] → [Key point 2] → [Key point 3]
Still have questions after reading? Let us know! 👍
8. Announce Downtime:🚨 Heads up, team!
We’re doing scheduled maintenance: → When: [DATE] at [TIME] → Duration: ~2 hours → Impact: [SERVICE] will be unavailable
Why: [Brief explanation]
We’ll post updates here as we progress.
Thanks for your patience! 🙏
9. Gather Feedback:Hey @user!
We’re always looking to improve [Product].
Since you’ve been using it for [TIME], I’d love to hear: → What’s working well for you? → What’s frustrating or missing? → If you could change one thing, what would it be?
Your feedback directly influences our roadmap. 🙏
(Bonus: We’re sending swag to everyone who shares detailed feedback this month! 👕)
10. Handle Off-Topic Discussion:Love the conversation, team! 👋
Quick reminder: #general is for [Product]-related discussions.
For [OFF-TOPIC SUBJECT], we have #off-topic.
Let’s move this thread there so others can easily find [Product] convos here. Thanks! 🙏
[Then move/copy the thread]
USAGE NOTES:
→ Customize [PLACEHOLDERS] for your brand
→ Adjust tone to match your community voice
→ Add/remove emojis based on audience
→ Personalize with member's specific context
→ Always read situation before using template3. Moderation Alerts
Define rules and flag violations.
Example - Moderation System:
community-manager: Setting up moderation alerts...
MODERATION POLICY:
Tier 1: Warning (Verbal)
→ Off-topic posts in wrong channel
→ Excessive self-promotion (>1/day)
→ Minor disrespectful language
→ Spamming same question repeatedly
Tier 2: Timeout (24 hours)
→ Repeat Tier 1 violations (3+)
→ Heated arguments/personal attacks
→ Sharing competitor products
→ Posting referral/affiliate links
Tier 3: Ban (Permanent)
→ Hate speech, harassment, threats
→ Sharing illegal content
→ Doxxing other members
→ Persistent spam after timeouts
AUTO-MODERATION RULES:
1. Link Spam Detection:
```javascript
// Flag if new member posts link in first message
if (member.joinedAt < 24_hours_ago && message.contains(URL)) {
autoDelete();
sendModAlert('Potential spam from new member');
}- Caps Lock Detection:
// Flag if >70% of message is caps
if (message.capsPercentage > 70 && message.length > 20) {
sendModAlert('Excessive caps lock - possible rage post');
}- Profanity Filter:
// Auto-delete severe profanity, flag moderate
if (message.contains(SEVERE_WORDS)) {
autoDelete();
issueWarning(member);
} else if (message.contains(MODERATE_WORDS)) {
sendModAlert('Profanity detected in message');
}- Mass Mention Detection:
// Flag if @mentions > 5 people
if (message.mentions.length > 5) {
sendModAlert('Mass mention detected - possible spam');
}- Repeat Message Detection:
// Flag if same message posted 3+ times
if (member.recentMessages.filter(m => m.text === message.text).length >= 3) {
sendModAlert('Repeat message spam detected');
}ESCALATION WORKFLOW:
Level 1 (Auto-handled): → Detect spam link from new member → Auto-delete message → Send DM explaining community guidelines → Log incident for review
Level 2 (Mod alert): → Member posts 3rd warning-level violation → Alert sent to #mod-alerts channel → Mod reviews context → Mod issues timeout or warning
Level 3 (Admin escalation): → Serious violation (harassment, threats) → Alert sent to admins immediately → Admin reviews and decides: ban or not → Document decision for transparency
MOD ALERT FORMAT:
🚨 Moderation Alert
Member: @user123
Violation: Tier 2 - Personal attack
Channel: #general
Message: [LINK TO MESSAGE]
Context:
→ Previous warnings: 2 (last: Dec 15)
→ Member since: Nov 2024
→ Contribution score: Low (14 messages total)
Recommended action: 24-hour timeout
Actions:
[Issue Warning] [24h Timeout] [Permanent Ban] [Dismiss]TRANSPARENCY REPORT (Monthly):
DECEMBER 2024 MODERATION REPORT
Actions Taken:
→ Warnings issued: 8
→ Timeouts (24h): 2
→ Permanent bans: 1
→ Auto-deleted spam: 47
Common Issues:
1. Off-topic posting (5 warnings)
2. Self-promotion spam (3 warnings)
3. Heated argument (2 timeouts)
4. Spam bot (1 ban, 47 auto-deletes)
Appeals:
→ Appeals filed: 1
→ Appeals upheld: 0
→ Appeals denied: 1
Policy Updates:
→ Clarified self-promotion rules (1 per week allowed)
→ Added #showcase channel for member projects
Community Health:
→ Violations down 30% from November
→ Member satisfaction: 8.2/10 (up from 7.6)
→ Active moderators: 3
Questions about moderation? DM @mod-teamModeration philosophy: Be firm, be fair, be consistent.
### 4. Engagement Metrics
Track participation and identify growth opportunities.
**Example - Metrics Dashboard:**COMMUNITY METRICS (January 2025)
GROWTH: → Total members: 612 (↑ +25% MoM) → New members: 122 → Retention (30d): 48% (↑ +18 pts) → Churn: 14 members (↓ -6 MoM)
ENGAGEMENT: → Daily active users: 87 (↑ +42% MoM) → Weekly active: 234 (38% of total) → Messages sent: 4,280 (↑ +83% MoM) → Avg messages per active user: 18.3
RESPONSE QUALITY: → Avg first response: 1.8 hours (↓ -2.4h improvement) → Question resolution: 89% (↑ +11 pts) → Community-answered: 71% (peer support strong)
TOP CONTRIBUTORS:
- @sarah_dev: 287 messages, 94% helpful
- @mike_tech: 203 messages, 89% helpful
- @alex_founder: 178 messages, 91% helpful
CHANNEL PERFORMANCE: → #general: 1,840 messages (43%) → #support: 1,120 messages (26%) → #showcase: 487 messages (11% - ↑ new channel!) → #feature-requests: 412 messages (10%)
NEW INITIATIVES: ✓ Monthly office hours (attendance: 34 members) ✓ Member spotlight (featured 4 members) ✓ Welcome flow (new member engagement +156%)
WHAT’S WORKING: → Welcome automation: First-message rate up 73% → Office hours: High engagement, great feedback → Member recognition: Contributors feel valued
WHAT NEEDS WORK: → Weekend engagement low (45% drop Sat-Sun) → International members (EU/Asia) underserved → Technical discussions still intimidating for beginners
NEXT MONTH GOALS: → Grow to 750 members (+23%) → Increase retention to 55% → Reduce response time to <1 hour → Launch peer mentorship program
### 5. FAQ Generation
Compile common questions and answers.
**Example - Auto-Generated FAQ:**community-manager: Generating FAQ from community questions…
TOP 10 FREQUENTLY ASKED QUESTIONS
Analyzed: 30 days of #support, #general Questions identified: 847 Unique questions: 124 Top questions (by frequency):
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- How do I get started? (Asked 34 times)
A: Getting started is easy:
Step 1: Install via npm
npm install claudekit-cli -gStep 2: Initialize your project
claudekit initStep 3: Run your first command
claudekit create authFull guide: https://docs.claudekit.cc/getting-started
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- What languages are supported? (Asked 28 times)
A: Currently supported: ✓ JavaScript/TypeScript ✓ Python ✓ Go ✓ Rust
Coming soon: → Java (Q2 2025) → PHP (Q3 2025) → Ruby (Q4 2025)
Want another language? Vote here: https://feedback.claudekit.cc
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- Does it work with my existing codebase? (Asked 22 times)
A: Yes! ClaudeKit integrates with existing projects.
It will: ✓ Respect your folder structure ✓ Match your coding style ✓ Use your existing dependencies ✓ Follow your conventions
Just run claudekit init in your project root.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- What does it cost? (Asked 19 times)
A: Pricing:
Free tier: → 10 features per month → Community support → Basic templates
Pro ($29/mo): → Unlimited features → Priority support → Custom templates → Team collaboration
Enterprise (Custom): → Everything in Pro → SSO/SAML → Dedicated support → Custom SLA
Try free: https://claudekit.cc/pricing
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- Is the code production-ready? (Asked 17 times)
A: Yes. Code is: ✓ Tested (90%+ coverage) ✓ Documented ✓ Security-reviewed ✓ Performance-optimized
1,200+ developers use ClaudeKit in production. See case studies: https://claudekit.cc/customers
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- How do I customize generated code? (Asked 15 times)
A: Three ways:
- Edit after generation (it’s your code!)
- Use custom templates (Pro feature)
- Provide detailed requirements upfront
Example:
claudekit create auth --style=jwt --provider=oauth --mfa=trueGuide: https://docs.claudekit.cc/customization
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- Can I use this for client projects? (Asked 14 times)
A: Yes! Commercial use allowed on all plans.
You own 100% of generated code. No attribution required.
For agencies/consultancies, check out Enterprise plan: → White-label option → Client seat management → Volume discounts
Contact: enterprise@claudekit.cc
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- What if I find a bug in generated code? (Asked 12 times)
A: Report bugs here: https://github.com/claudekit/claudekit/issues
We typically: → Acknowledge within 24 hours → Fix critical bugs within 48 hours → Release patches weekly
For urgent production issues, email: support@claudekit.cc
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- Does it replace developers? (Asked 11 times)
A: No. ClaudeKit removes boilerplate so developers can focus on unique features.
It’s like having a junior dev who handles repetitive tasks while you build what makes your product special.
Think: GitHub Copilot, but for complete features instead of lines of code.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- How secure is generated code? (Asked 10 times)
A: Security is our top priority:
✓ OWASP Top 10 compliance ✓ Automated security scanning ✓ Regular penetration testing ✓ Secure by default (no shortcuts)
Security audit report: https://security.claudekit.cc
Found a vulnerability? security@claudekit.cc (24h SLA)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
CAN’T FIND YOUR QUESTION?
Ask in #support and we’ll respond within 2 hours (usually faster).
FAQ last updated: January 15, 2025
## When to Use Community Manager
**Perfect for:**
- Discord/Slack community management
- Sentiment analysis and health monitoring
- Member engagement strategies
- Moderation system design
- FAQ creation from conversations
- Community event planning
**Not needed for:**
- Social media management (use Social Media Manager)
- One-on-one customer support (use support team)
- Long-form content creation (use Content Creator)
- Campaign execution (use Campaign Manager)
## Example Workflows
### Workflow 1: Community Health Check
-
You: “Analyze our Discord community health”
-
community-manager: Comprehensive audit
- Analyzes activity rates
- Tracks sentiment trends
- Identifies power users
- Finds engagement gaps
- Spots concerning patterns
-
Output: FINDINGS: → Activity rate: 18% (target: 40%) → New member retention: 22% (low) → Power user concentration: 68% (high) → Sentiment: 6.8/10 (positive but declining)
RECOMMENDATIONS: → Fix onboarding flow (+78% first message rate) → Create FAQ from common questions → Launch monthly events → Recognize power users publicly
-
You implement recommendations
-
Activity improves +94% over 60 days
### Workflow 2: Crisis Management
-
You: “Members are angry about price increase”
-
community-manager: Sentiment analysis
- Identifies negative threads
- Analyzes complaint themes
- Drafts response template
- Suggests mitigation strategy
-
Output: SEVERITY: High (8 angry members, sentiment dropping)
RESPONSE TEMPLATE: “We hear you and acknowledge we should have communicated this better…”
ACTIONS: → Public apology in #announcements → DM affected users individually → Grandfather existing users on old pricing → Add 30-day notice for future changes
-
You respond publicly + individually
-
Sentiment recovers within 48 hours
## Best Practices
### 1. Welcome Every New Member
**Bad:** New members join silently
**Good:** Auto-welcome + prompt to introduce themselves
First impression matters. Make it welcoming.
### 2. Respond Fast, Especially to Questions
**Bad:** Answer when you have time (8+ hours)
**Good:** Respond within 2 hours, even if just "Looking into this"
Speed signals you care.
### 3. Celebrate Member Wins
**Bad:** Ignore when members share successes
**Good:** Celebrate publicly, ask to feature them
Recognition breeds more engagement.
## Related Agents
- [Social Media Manager](/docs/marketing/agents/social-media-manager) - Manage public social channels
- [Content Reviewer](/docs/marketing/agents/content-reviewer) - Review community content for quality
- [Campaign Manager](/docs/marketing/agents/campaign-manager) - Coordinate campaigns involving community
## Related Commands
- `/community analyze` - Health check and sentiment analysis
- `/community engage` - Generate engagement strategies
- `/community moderate` - Set up moderation systems
---
**Great communities don't happen by accident. They're built with intention, strategy, and care.**
Ready to turn your community into a thriving growth engine? Start managing.