community-health-monitoring

Audits follower quality, engagement authenticity, unfollower patterns, and network efficiency to produce a community health score. Use when monitoring account health or detecting bot/spam followers.

139 stars

Best use case

community-health-monitoring is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Audits follower quality, engagement authenticity, unfollower patterns, and network efficiency to produce a community health score. Use when monitoring account health or detecting bot/spam followers.

Teams using community-health-monitoring should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/community-health-monitoring/SKILL.md --create-dirs "https://raw.githubusercontent.com/nirholas/XActions/main/skills/community-health-monitoring/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/community-health-monitoring/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How community-health-monitoring Compares

Feature / Agentcommunity-health-monitoringStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Audits follower quality, engagement authenticity, unfollower patterns, and network efficiency to produce a community health score. Use when monitoring account health or detecting bot/spam followers.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Community Health Monitoring

MCP-powered workflow for auditing follower quality, engagement health, and network efficiency. Produces a scored health report.

## MCP Tools Used

| Tool | Purpose |
|------|---------|
| `x_get_profile` | Account-level stats |
| `x_get_followers` | Follower list for quality audit |
| `x_get_following` | Following list for reciprocity check |
| `x_get_non_followers` | Identify non-reciprocal follows |
| `x_get_tweets` | Engagement data for authenticity check |
| `x_detect_unfollowers` | Track recent unfollower patterns |

## Browser Scripts

Complement MCP analysis with browser-side tools:

| Goal | Script |
|------|--------|
| Audit follower quality | `src/auditFollowers.js` |
| Detect unfollowers | `src/detectUnfollowers.js` |
| Audience demographics | `src/audienceDemographics.js` |
| Follow ratio analysis | `src/followRatioManager.js` |
| Account health dashboard | `src/accountHealthMonitor.js` |
| Shadowban check | `src/shadowbanChecker.js` |

## Workflow

1. **Profile baseline** -- Call `x_get_profile` to get follower count, following count, and calculate follower-to-following ratio.
2. **Audit follower quality** -- Call `x_get_followers` with `limit: 200`. Classify each follower:
   - **Active**: Has bio, 50+ followers, posted in last 30 days
   - **Low quality**: No bio, <10 followers, or no recent activity
   - **Suspect bot**: Default avatar, username with many numbers, 0 tweets, follows 1000+
3. **Check engagement authenticity** -- Call `x_get_tweets` with `limit: 30`. For each tweet, compare engagement volume to follower count. Flag anomalies: likes/follower ratio > 10% (potential engagement pods) or < 0.1% (ghost followers).
4. **Analyze unfollower patterns** -- Call `x_detect_unfollowers`. Note churn rate and whether unfollowers correlate with specific content types or posting gaps.
5. **Assess reciprocity** -- Call `x_get_non_followers`. Calculate reciprocity rate: `mutual_follows / total_following * 100`. Identify high-value accounts not following back.
6. **Calculate health score** -- Weighted composite (0-100):
   - Follower quality: 30% (% active followers)
   - Engagement authenticity: 25% (normal engagement patterns)
   - Churn rate: 20% (low unfollower rate)
   - Reciprocity: 15% (healthy follower/following balance)
   - Growth trend: 10% (net positive follower change)
7. **Generate report** -- Compile into the template below with actionable recommendations.

## Output Template

```
## Community Health Report: @{username}
Date: {date} | Health Score: {score}/100

### Score Breakdown
| Category | Score | Weight | Weighted |
|----------|-------|--------|----------|
| Follower Quality | {n}/100 | 30% | {n} |
| Engagement Authenticity | {n}/100 | 25% | {n} |
| Churn Rate | {n}/100 | 20% | {n} |
| Reciprocity | {n}/100 | 15% | {n} |
| Growth Trend | {n}/100 | 10% | {n} |

### Follower Audit
- Total: {count} | Active: {n}% | Low quality: {n}% | Suspect bots: {n}%

### Engagement Health
- Avg engagement rate: {rate}%
- Anomalous posts: {count} flagged

### Reciprocity
- Following: {count} | Follow back: {n}% | Non-followers: {count}

### Recommendations
1. {actionable recommendation}
2. {actionable recommendation}
3. {actionable recommendation}
```

## Strategy Guide

### Monthly health audit routine
1. Run full MCP workflow above for baseline report
2. Compare against previous month's scores
3. Action items: block flagged bots, unfollow non-reciprocals above threshold
4. Use `src/accountHealthMonitor.js` for quick between-audit checks

### Score interpretation
| Score | Grade | Action |
|-------|-------|--------|
| 80-100 | Excellent | Maintain current strategy |
| 60-79 | Good | Minor adjustments needed |
| 40-59 | Fair | Review engagement strategy, clean follower list |
| 20-39 | Poor | Major cleanup needed, block bots, reassess content |
| 0-19 | Critical | Possible shadowban, mass bot followers, or inactive account |

### Improving a low health score
1. Block suspect bot followers with `src/blockBots.js`
2. Unfollow non-reciprocals with `src/unfollowback.js`
3. Increase posting consistency to reduce churn
4. Engage authentically to improve engagement rate

## Notes
- Health score is a heuristic -- use as directional guidance, not exact measurement
- Bot detection uses profile signals, not ML -- some false positives expected
- Run quarterly for trend tracking, monthly for active management

Related Skills

follower-monitoring

139
from nirholas/XActions

Monitors X/Twitter follower changes using browser console scripts. Detects who unfollowed, tracks new followers with welcome messages, monitors any public account, runs continuous monitoring with alerts, tracks follower growth over time, and analyzes follower demographics. Use when tracking follower changes, detecting unfollowers, or monitoring Twitter accounts.

community-notes

139
from nirholas/XActions

View, write, rate, and browse Community Notes on X/Twitter posts. Use when users want to interact with Community Notes — reading fact-checks, contributing notes, or rating existing notes as helpful or not.

community-management

139
from nirholas/XActions

Manages X/Twitter community memberships. Bulk-leave all communities, join communities by topic, and manage community interactions. Use when leaving all communities, joining niche communities, or managing community presence.

xactions-mcp-server

139
from nirholas/XActions

Free MCP server providing 68+ tools for AI agents to automate X/Twitter. Scrapes profiles, followers, tweets. Posts, follows, likes, retweets, downloads videos, analyzes sentiment, monitors brands, manages DMs, runs workflows, and more. Uses local Puppeteer -- no API keys or payments required. Compatible with Claude Desktop, Cursor, Windsurf, VS Code. Use when setting up or using AI agent Twitter automation via MCP.

xactions-cli

139
from nirholas/XActions

Command-line interface for scraping X/Twitter data, managing MCP server config, and running automation. Scrapes profiles, followers, tweets, search results, and more from terminal. Outputs text, JSON, or CSV. Uses Puppeteer stealth. Use when running Twitter operations from command line or automated pipelines.

x402-payments

139
from nirholas/XActions

Enable and integrate x402 crypto payment protocol for XActions API access. Supports multi-chain, multi-token payments for pay-per-use API calls. Use when users want to pay for XActions operations with crypto or integrate x402 into their own agent/app.

x-pro-management

139
from nirholas/XActions

Navigate to X Pro (TweetDeck), set up monitoring columns, and manage multi-column view. Use when users want to use X Pro / TweetDeck features or set up a multi-column dashboard.

webhooks

139
from nirholas/XActions

Create, manage, and test webhooks in XActions. Get notified via HTTP when automation jobs complete, followers change, or operations finish. Use when users want to integrate XActions events into external systems.

viral-thread-generation

139
from nirholas/XActions

Researches trending topics and competitor threads to generate high-engagement thread content with optimized hooks, value ladders, and calls to action. Use when creating threads or planning viral content.

video-downloading

139
from nirholas/XActions

Download videos and GIFs from X/Twitter posts in the browser or via API. Single video, batch download, and quality selection. Use when users want to save or download Twitter/X videos.

topic-management

139
from nirholas/XActions

Browse, follow, and unfollow X Topics. Manage your followed topics list and discover new ones by keyword. Use when users want to follow or unfollow topics on X, or manage their topic feed.

timeline-viewing

139
from nirholas/XActions

Switch between For You / Following timelines, auto-scroll and collect posts, scrape timeline data, and export as JSON. Use when users want to browse, collect, or export tweets from their X timeline.