skills.rest
Xquik-dev
Xquik-devOFFICIAL
Explore all skills by this author →
WebsiteGitHub

follow-unfollow

Automate follow and unfollow actions on X via authenticated API endpoints.

177|17|Updated Feb 27, 2026
Search Tags:#authorization#api#twitter#follow#xquik#unfollow
One-click install
npx skills add https://github.com/Xquik-dev/x-twitter-scraper --skill follow-unfollow
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: follow-unfollow
Source: https://github.com/Xquik-dev/x-twitter-scraper/tree/main/skills/follow-unfollow
Command: npx skills add https://github.com/Xquik-dev/x-twitter-scraper --skill follow-unfollow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enables safe and controlled follow/unfollow actions on X for connected accounts, preventing accidental mass following and providing a clear approval flow.

Core Features & Use Cases

  • Single-target follow and unfollow operations with explicit confirmation.
  • Follow-state checks to verify whether an account follows another.
  • Guardrails for bulk operations, including per-action consent and rate-limit awareness.

Quick Start

Ask the agent to follow a target account by numeric ID, or unfollow and verify the follow state for a given account.

Frequently Asked Questions about follow-unfollow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate following and unfollowing actions on X safely?▼

Automating following and unfollowing on X requires authenticated API endpoints with explicit user confirmation and guardrails against mass actions to prevent accidental bulk operations.

Can I check if one X account follows another using an API?▼

Follow-state checks via authenticated API endpoints verify whether a connected X account follows another, resolving target handles to numeric IDs to execute the query.

Do I need an API key to follow or unfollow users on X in bulk?▼

Bulk follow or unfollow operations on X require a valid XQUIK_API_KEY for authentication, applying per-action consent and rate-limit awareness guardrails to protect connected accounts.

What's the best way to prevent accidental mass following on X?▼

Preventing accidental mass following on X involves applying guardrails to bulk operations, enforcing per-action consent, and requiring explicit user confirmation before executing list-based actions.

Why does my X follow API request require a numeric ID?▼

X follow API requests require numeric IDs because authenticated endpoints execute actions using resolved identifiers, converting target handles to numeric values when needed for processing.

Are there limitations when automating bulk unfollow operations on X?▼

Bulk unfollow operations on X are constrained by rate-limit awareness and per-action consent guardrails, requiring explicit user confirmation for each action to prevent mass executions.

Related Skills

Explore More Content & Communication Skills→
KatsumitecKatsumitec

ll-order-by-chnl

Identify merchant orders from channel order IDs via an API endpoint.

Official
Advanced
steipetesteipete
385.7k

bird

Read, search, and post on X/Twitter via CLI with cookie or API authentication.

Community
Intermediate
JStaRFilmsJStaRFilms
23

twitter-automation

Automate posting, engagement, and user management on Twitter/X via the inference.sh CLI.

Community
Intermediate
zangjeicyzangjeicy

xurl

Perform X API v2 social media actions via command-line interface.

Community
Advanced