agentleFS
nirholasnirholas/XActions/skills/unfollow-management/SKILL.md

unfollow-management

Skill648 starsChanged 9 months agoApache-2.0View on GitHub

Mass unfollow on X/Twitter via browser console scripts. Unfollows everyone, only non-followers, non-followers with username logging, smart time-based unfollow with whitelists, and follow/following ratio management. Use when cleaning up a following list, removing non-followers, bulk unfollowing accounts, or optimizing your follow ratio.

The file

We split this skill into the rules it gives an agent

11 rules. About 0 are common, 2 are distinctive, and 9 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 9

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Backoff: If rate limited, scripts wait 30–60 seconds before retrying

    line 35
  2. Distinctive:

    Recovery: If action-restricted, wait 12–24 hours

    line 37
  3. Very specific:

    Run src/followRatioManager.js on your profile to assess current ratio

    line 43
  4. Very specific:

    Use XActions.plan() to see how many unfollows are needed

    line 44
  5. Very specific:

    Run src/unfollowback.js to remove non-followers first (safest)

    line 45
  6. Very specific:

    If more cleanup needed, use src/unfollowEveryone.js with abort when satisfied

    line 46
  7. Very specific:

    Use src/followRatioManager.js weekly to monitor trends

    line 52
  8. Very specific:

    Run src/unfollowback.js monthly to remove non-reciprocal follows

    line 53
  9. Very specific:

    Keep a whitelist in smartUnfollow.js for accounts you always want to follow

    line 54
  10. Very specific:

    Run src/unfollowWDFBLog.js (saves log of who was unfollowed)

    line 59
  11. Very specific:

    Use src/followRatioManager.js to verify improvements

    line 61

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Unfollow Management

Browser console scripts for managing who you follow on X/Twitter. All scripts run in DevTools console.

Script Selection

GoalFileNavigate to
Unfollow ALL accountssrc/unfollowEveryone.jsx.com/USERNAME/following
Unfollow only non-followerssrc/unfollowback.jsx.com/USERNAME/following
Unfollow non-followers + download logsrc/unfollowWDFBLog.jsx.com/USERNAME/following
Time-based smart unfollow with whitelistsrc/automation/smartUnfollow.jsx.com/USERNAME/following
Detect who unfollowed yousrc/detectUnfollowers.jsx.com/USERNAME/followers
Monitor follow/following ratio + plansrc/followRatioManager.jsx.com/USERNAME
Remove specific followers from YOUR listsrc/removeFollowers.jsx.com/USERNAME/followers

Script Details

For detailed algorithms, controls, configurations, and DOM selectors for each script, see references/script-details.md.

Rate Limiting & Safety

  • Default delay: 1–2 seconds between unfollows (gaussian randomized)
  • Batch delay: 2–3 seconds between scroll batches
  • Rate limit detection: Scripts check for [data-testid="toast"] warning banners
  • Backoff: If rate limited, scripts wait 30–60 seconds before retrying
  • Daily limit guidance: X may restrict after ~400 unfollows/day; spread over multiple sessions
  • Recovery: If action-restricted, wait 12–24 hours

Strategy Guide

Cleaning a bloated following list

  1. Run src/followRatioManager.js on your profile to assess current ratio
  2. Use XActions.plan() to see how many unfollows are needed
  3. Run src/unfollowback.js to remove non-followers first (safest)
  4. If more cleanup needed, use src/unfollowEveryone.js with abort when satisfied
  5. Re-check ratio with XActions.track()

Maintaining a healthy ratio over time

  1. Set up periodic runs of src/detectUnfollowers.js to track losses
  2. Use src/followRatioManager.js weekly to monitor trends
  3. Run src/unfollowback.js monthly to remove non-reciprocal follows
  4. Keep a whitelist in smartUnfollow.js for accounts you always want to follow

Before a big unfollow session

  1. Export your following list first: scripts/scrapeFollowing.js
  2. Run src/unfollowWDFBLog.js (saves log of who was unfollowed)
  3. Review the downloaded log for any mistakes
  4. Use src/followRatioManager.js to verify improvements

Troubleshooting

ProblemSolution
"No unfollow buttons found"Make sure you're on the Following page, not Followers
Script stops after ~20 unfollowsX rate limit triggered — wait 1 hour and re-run
Confirmation dialog doesn't appearDOM may have changed — check confirmationSheetConfirm selector
Script unfollows mutualsUse unfollowback.js instead of unfollowEveryone.js
"Action restricted" warningAccount is temporarily limited — wait 12-24 hours
Script misses accountsRe-run the script — some load below the scroll area

Related Skills

  • follower-monitoring — Track follower growth and detect unfollowers
  • blocking-muting-management — Block/unblock for removing followers
  • growth-automation — Grow followers to improve ratio organically
  • analytics-insights — Understand engagement before unfollowing

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.