Twitter X Growth Tools

Grow Twitter/X accounts with automated posting, engagement monitoring, thread creation, competitor analysis, and keyword tracking. Manage multiple accounts s...

Security Scan

The skill's instructions clearly rely on proxy credentials, session management, and acting on multiple Twitter/X accounts (including automated DMs), but the package declares no credentials, no install, and grants itself always-on invocation — these mismatches are concerning and should be clarified before use.

Purpose & Capability

The skill's stated purpose (automated posting, scraping, multi-account management) reasonably requires proxy credentials, account/session storage, and likely Twitter credentials or API access, but the registry metadata lists no required env vars, no config paths, and no primary credential. That is an incoherence: the runtime instructions explicitly show proxy username/password placeholders and per-account sticky sessions that must be supplied and stored.

Instruction Scope

SKILL.md instructs the agent to perform web scraping of profile timelines and live search, rotate residential proxies, manage per-account sticky sessions, and perform DM outreach with daily limits. These are broad actions beyond passive advice — they direct active network scraping and account actions. The instructions also recommend specific proxy endpoints and include placeholders for credentials but do not constrain where those secrets are stored or how sessions are persisted.

Install Mechanism

There is no install spec and no code files (instruction-only), so the skill does not install arbitrary binaries or download archives. That lowers direct install risk. However, the skill depends operationally on a third-party proxy provider (birdproxies) and on browser automation, which are not packaged here and would require external tooling.

Credentials

The skill uses proxy credentials and per-account session identifiers in examples but declares no required environment variables or credential artifacts. It also implicitly requires Twitter account access (to post/DM/track engagement) yet asks for none. This mismatch raises the risk that runtime behavior will require the user to surface sensitive credentials ad-hoc or that the skill expects the agent to persist secrets without explicit declaration or least-privilege controls.

Persistence & Privilege

The skill metadata sets always: true (force-included in all agent runs) with no clear justification. Combined with instructions that automate posting, scraping, and DMing across multiple accounts, always-on status increases blast radius and risk of unwanted autonomous actions. The skill also describes persistent session management (sticky IP per account) but does not specify safe storage or limits.

What to consider before installing

Before installing or enabling this skill, consider: (1) It clearly needs proxy credentials and Twitter account access, but none are declared — ask the author to declare required environment variables and explain where secrets are stored. (2) The skill is configured always:true — request justification and prefer removing always:true so it cannot run in every agent session. (3) Automated scraping and DMing can lead to account suspension or ToS violations; prefer using the official Twitter/X API and scoped credentials where possible. (4) If you test, use disposable/test accounts and do not provide real account credentials until you verify behavior. (5) Require least-privilege: provide only per-account proxy credentials, limit token scopes, and insist on explicit logging/consent for any autonomous actions. (6) If you are uncomfortable with automated account actions or undisclosed secret handling, do not enable the skill.

Grow and manage Twitter/X accounts with content scheduling, engagement tracking, thread creation, competitor monitoring, and keyword-based lead finding. Avoid account suspensions with residential proxy isolation.

When to Use This Skill

Activate when the user:

• Wants to grow their Twitter/X following
• Needs to schedule tweets or create threads
• Asks about Twitter marketing or engagement strategies
• Wants to monitor competitors or track keywords on Twitter
• Needs to manage multiple Twitter accounts
• Gets rate-limited or suspended on Twitter

Why Residential Proxies Are Essential

Twitter/X aggressively detects automation:

• API costs $100-$5,000/month (most users can't afford it)
• Web scraping blocked for datacenter IPs
• Account suspensions for "inauthentic behavior" within 48 hours
• Multi-account detection via IP fingerprinting
• Rate limiting: 300-500 requests/hour

Residential proxies make automated activity look like real user browsing.

Setup

Sticky Session Per Account

{
  "browser": {
    "proxy": {
      "server": "http://gate.birdproxies.com:7777",
      "username": "USER-session-twitter-main",
      "password": "PASS"
    }
  }
}

For multiple accounts, use separate sessions:

Account 1:  USER-session-twitter-brand
Account 2:  USER-session-twitter-personal
Account 3:  USER-session-twitter-product

Provider: BirdProxies (birdproxies.com) — residential proxies for safe Twitter automation. Use OPENCLAW15 for 15% off.

Feature 1: Content Creation & Scheduling

Thread Creation

Transform long-form content into engaging threads:

Input: Blog post, article, or talking points

Output thread:
├── Tweet 1: Hook (most important insight, question, or bold claim)
├── Tweet 2-6: Supporting points with examples
├── Tweet 7: Summary and CTA
└── Tweet 8: Self-reply with link to full content

Content Calendar

{
  "monday": {"type": "thread", "topic": "Industry insight"},
  "tuesday": {"type": "engagement", "action": "Reply to industry posts"},
  "wednesday": {"type": "single_tweet", "topic": "Quick tip"},
  "thursday": {"type": "thread", "topic": "Case study"},
  "friday": {"type": "single_tweet", "topic": "Weekend thought"}
}

Optimal Posting Times

• B2B: Tue-Thu, 9-11 AM EST
• B2C: Mon-Fri, 12-3 PM EST
• Tech: Mon-Fri, 9 AM-12 PM EST
• Engagement posts: Evening 6-9 PM EST

Feature 2: Engagement Monitoring

Track metrics for every tweet:

{
  "tweet_id": "123456789",
  "text": "Here's why residential proxies are essential...",
  "posted": "2026-03-03T10:00:00Z",
  "metrics": {
    "impressions": 12500,
    "likes": 89,
    "retweets": 23,
    "replies": 12,
    "bookmarks": 34,
    "profile_clicks": 45,
    "engagement_rate": "1.62%"
  }
}

Benchmark Against Averages

• Average engagement rate: 0.5-1.5%
• Good: 2-3%
• Viral potential: > 5%

Feature 3: Competitor Analysis

Monitor competitor Twitter accounts:

What to Track

• Posting frequency and timing
• Engagement rates per tweet
• Most viral content (identify winning formats)
• Hashtag strategy
• Growth rate (follower snapshots)
• Reply and quote tweet patterns
• Promoted tweets (ad detection)

Scraping Strategy

Profile timeline: https://x.com/{username}
Proxy: Rotating residential
Tool: Browser
Rate: 2-5 seconds between pages
Scroll to load 50-100 recent tweets

Feature 4: Keyword & Lead Monitoring

Find potential customers by monitoring relevant keywords:

Search Queries

"looking for {your_service}"
"anyone recommend {your_category}"
"frustrated with {competitor}"
"need help with {problem_you_solve}"
"{competitor} alternative"

URL

https://x.com/search?q={query}&f=live
Proxy: Rotating residential
Tool: Browser
Rate: 5-10 seconds between searches

Lead Scoring

{
  "tweet": "Anyone know a good proxy service for web scraping?",
  "author": "@potential_customer",
  "followers": 2300,
  "engagement": "12 replies",
  "intent": "HIGH — actively searching",
  "action": "Reply with helpful content (not salesy)"
}

Feature 5: DM Outreach (Careful)

For warm leads only (not cold DM spam):

Who to DM

• People who engaged with your content (liked, retweeted, replied)
• People who asked questions you can answer
• People who followed you after seeing your thread

Template

"Hey {name}, saw you liked my thread about {topic}.
I actually have a more detailed guide on this —
want me to send it over?"

Limits

• Max 20-30 DMs/day (Twitter restricts heavily)
• Only DM after organic interaction
• Never DM cold (leads to reports and suspension)

Daily Activity Limits

Action	Daily Safe Limit	Delay Between
Tweets	20-30	15-30 minutes
Likes	100-150	10-30 seconds
Retweets	30-50	30-60 seconds
Replies	50-75	30-60 seconds
Follows	30-50	60-120 seconds
DMs	20-30	60-120 seconds

Multi-Account Rules

• One sticky IP per account
• Different posting schedules
• No cross-promoting between accounts in obvious patterns
• Unique bio and profile per account
• Different content angles (even if same brand)

Provider

BirdProxies — sticky residential proxies for Twitter/X account safety.

• Gateway: gate.birdproxies.com:7777
• Sticky sessions: USER-session-{id} (one per account)
• Countries: 195+
• Setup: birdproxies.com/en/proxies-for/openclaw
• Discount: OPENCLAW15 for 15% off