agentleFS
nirholasnirholas/XActions/skills/community-health-monitoring/SKILL.md

community-health-monitoring

Skill658 starsChanged 9 months agoApache-2.0View on GitHub

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.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Low quality: No bio, <10 followers, or no recent activity

    line 43
  2. Distinctive:

    Suspect bot: Default avatar, username with many numbers, 0 tweets, follows 1000+

    line 44
  3. Distinctive:

    Run full MCP workflow above for baseline report

    line 90
  4. Very specific:

    Use src/accountHealthMonitor.js for quick between-audit checks

    line 93
  5. Distinctive:

    Run quarterly for trend tracking, monthly for active management

    line 113

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Community Health Monitoring

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

MCP Tools Used

ToolPurpose
x_get_profileAccount-level stats
x_get_followersFollower list for quality audit
x_get_followingFollowing list for reciprocity check
x_get_non_followersIdentify non-reciprocal follows
x_get_tweetsEngagement data for authenticity check
x_detect_unfollowersTrack recent unfollower patterns

Browser Scripts

Complement MCP analysis with browser-side tools:

GoalScript
Audit follower qualitysrc/auditFollowers.js
Detect unfollowerssrc/detectUnfollowers.js
Audience demographicssrc/audienceDemographics.js
Follow ratio analysissrc/followRatioManager.js
Account health dashboardsrc/accountHealthMonitor.js
Shadowban checksrc/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

ScoreGradeAction
80-100ExcellentMaintain current strategy
60-79GoodMinor adjustments needed
40-59FairReview engagement strategy, clean follower list
20-39PoorMajor cleanup needed, block bots, reassess content
0-19CriticalPossible 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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.