x-account-management

name	x-account-management
description	X/Twitter account management via GeeLark cloud phone automation. Covers posting, engagement, profile setup, account health, warming schedules, and phone lifecycle management.

X Account Management Skill

Manage X/Twitter accounts via GeeLark cloud phone automation. All operations execute through Chrome on Android cloud phones, bypassing Castle.io fingerprint detection that blocks headless browsers.

When to Use This Skill

• Posting tweets or replies from managed accounts
• Executing warming schedules for new accounts
• Engaging with content (likes, follows, retweets, quotes)
• Creating and onboarding new X accounts
• Setting up account profiles (avatar, banner, bio)
• Health checking accounts for suspension/lock detection
• Refreshing session cookies for API compatibility

Available Tools

X Operations (Async -- returns job_id)

Tool	Purpose	Key Params
geelark_post_tweet	Post a tweet	account_id, phone_id, text
geelark_like_tweet	Like a tweet	phone_id, tweet_id
geelark_unlike_tweet	Remove a like	account_id, phone_id, tweet_id
geelark_reply_to_tweet	Reply to a tweet	phone_id, tweet_id, text
geelark_follow_user	Follow a user	phone_id, username
geelark_unfollow_user	Unfollow a user	phone_id, username
geelark_retweet	Repost a tweet	phone_id, tweet_id
geelark_unretweet	Undo a repost	phone_id, tweet_id
geelark_quote_tweet	Quote tweet with comment	phone_id, tweet_id, text

Account Management (Async -- returns job_id)

Tool	Purpose	Key Params
geelark_create_x_account	Create new X account	email, email_password, phone_id
geelark_login_x_account	Login to existing account	account_id, phone_id
geelark_check_account_health	Deep health check via Chrome	account_id, phone_id
geelark_setup_profile	Update name/bio/avatar/banner	account_id, phone_id, avatar_url, banner_url
geelark_change_handle	Change @username	phone_id, account_id, new_handle
geelark_purchase_premium	Buy X Premium subscription	account_id, phone_id, card details

Account Management (Synchronous)

Tool	Purpose	Key Params
geelark_refresh_cookies	Extract fresh session cookies	account_id, phone_id

Phone Lifecycle

Tool	Purpose	Key Params
geelark_launch_phone	Start a cloud phone (30-90s)	phone_id
geelark_stop_phone	Stop a running phone	phone_id
geelark_list_phones	List all phone profiles	(none)
geelark_create_phone	Create new phone profile	(optional: name, proxy_country)
geelark_destroy_phone	Delete phone profile	phone_id
geelark_update_proxy	Rotate proxy IP	phone_id

Debugging

Tool	Purpose	Key Params
geelark_take_screenshot	Screenshot for debugging	phone_id
geelark_ui_dump	Get UI state as JSON	phone_id
geelark_shell_execute	Run Android shell command	phone_id, command
geelark_navigate_chrome	Open URL in Chrome	phone_id, url

Content Discovery (x-research-mcp -- no auth required)

Tool	Purpose	Key Params
xr_search_tweets	Search tweets by query	query
xr_find_reply_targets	Find tweets good for replies	topic
xr_get_user_tweets	Get user's recent tweets	username
xr_get_tweet	Get single tweet by ID	tweet_id
xr_get_trending_topics	Get trending topics	(optional: niche)
xr_analyze_engagement	Analyze tweet viral potential	tweet_id
xr_get_account_analytics	Account-level analytics	username
xr_get_tweet_metrics	Track tweet metrics over time	tweet_id

Vault Management (vault-mcp)

Tool	Purpose	Notes
Account listing	List vault accounts with state	Via vault-mcp tools
Account details	Get account credentials/metadata	From encrypted vault

Async Polling Pattern

Most GeeLark operations are asynchronous. They return a job_id immediately. Poll geelark_check_job_status every 10-15 seconds until the job completes.

// Step 1: Start the operation
const result = geelark_post_tweet({
  account_id: "vault-uuid",
  phone_id: "PHONE_ID",
  text: "Tweet content",
  auto_stop: true  // Optional: auto-stop phone when done (default: true)
})
// Returns: { job_id: "uuid" }

// Step 2: Poll for completion (every 10-15 seconds)
let status = "running"
while (status !== "completed" && status !== "failed") {
  // Wait 10-15 seconds between polls
  const check = geelark_check_job_status({ job_id: result.job_id })
  status = check.status
  // status values: "running", "completed", "failed"
}

// Step 3: Handle result
if (status === "completed") {
  // Success -- check.result contains operation-specific data
} else {
  // Failure -- check.error contains error details
}

Exceptions (synchronous -- no polling needed):

• geelark_refresh_cookies -- returns immediately (~10 seconds)
• geelark_list_phones -- returns immediately

Phone Lifecycle Patterns

Single-Operation Flow (Use auto_stop)

For one-off operations, let GeeLark handle phone shutdown automatically:

// Phone stops automatically after the operation completes
geelark_post_tweet({
  account_id: "uuid",
  phone_id: "PHONE_ID",
  text: "Hello world",
  auto_stop: true  // default
})
// Poll for completion, then done -- phone is already stopped

Multi-Operation Flow (Explicit Lifecycle)

For batch operations or multiple actions on the same account, manage the phone lifecycle explicitly to avoid repeated start/stop overhead:

// Step 1: Launch phone (blocks until running, 30-90 seconds)
geelark_launch_phone({ phone_id: "PHONE_ID" })

// Step 2: Login (async)
const loginJob = geelark_login_x_account({
  account_id: "uuid",
  phone_id: "PHONE_ID",
  auto_stop: false  // Keep phone running
})
// Poll geelark_check_job_status until completed

// Step 3: Perform multiple operations (all with auto_stop: false)
const postJob = geelark_post_tweet({
  account_id: "uuid",
  phone_id: "PHONE_ID",
  text: "...",
  auto_stop: false
})
// Poll for completion

const likeJob = geelark_like_tweet({
  phone_id: "PHONE_ID",
  tweet_id: "...",
  auto_stop: false
})
// Poll for completion

// Step 4: Refresh cookies (synchronous -- no polling)
geelark_refresh_cookies({
  account_id: "uuid",
  phone_id: "PHONE_ID"
})

// Step 5: Stop phone manually
geelark_stop_phone({ phone_id: "PHONE_ID" })

Session Batching Pattern

When performing multiple actions across accounts or multiple actions on one account, use session batching to minimize phone churn:

Key principle: Set auto_stop: false on ALL operations within a batch, then call geelark_stop_phone once at the end.

Example: Warming batch for one account

// Launch once
geelark_launch_phone({ phone_id: "PHONE_ID" })

// Login once
const login = geelark_login_x_account({
  account_id: "uuid", phone_id: "PHONE_ID", auto_stop: false
})
// Poll until completed

// Execute multiple warming actions
for (const target of warmingTargets) {
  const job = geelark_like_tweet({
    phone_id: "PHONE_ID",
    tweet_id: target.tweet_id,
    auto_stop: false
  })
  // Poll until completed
  // Wait 60-120 seconds between actions (safety delay)
}

// Refresh cookies after session
geelark_refresh_cookies({ account_id: "uuid", phone_id: "PHONE_ID" })

// Stop phone once
geelark_stop_phone({ phone_id: "PHONE_ID" })

Example: Health check batch across accounts

// Launch one phone
geelark_launch_phone({ phone_id: "PHONE_ID" })

// Check each account sequentially
for (const account of accounts) {
  const job = geelark_check_account_health({
    account_id: account.id,
    phone_id: "PHONE_ID",
    auto_stop: false
  })
  // Poll until completed
  // Record result
}

// Stop phone once
geelark_stop_phone({ phone_id: "PHONE_ID" })

Warming Schedule

New accounts must be gradually warmed over 21 days to avoid X's detection systems. Warming is agent-level orchestration -- the agent selects and executes individual GeeLark actions based on account age.

Day Range	Max Actions/Day	Allowed Actions (GeeLark Tools)
0-3	2	geelark_like_tweet only
4-7	5	geelark_like_tweet, geelark_follow_user
8-14	10	Above + geelark_reply_to_tweet
15-21	15	Above + geelark_post_tweet, geelark_retweet
21+	Unlimited	Full access -- account is warmed

Warming Orchestration Steps

1. Determine account age from creation_date in vault
2. Look up allowed actions and max count from schedule above
3. Use xr_search_tweets or xr_find_reply_targets to find engagement targets
4. Launch phone, login, execute allowed actions via GeeLark tools
5. Add 60-120 second random delays between actions
6. Track daily action count to respect limits
7. Stop phone after completing warming session

Content Discovery (Read-Only)

Use x-research-mcp tools (xr_*) to find content for engagement. These tools do not require authentication and work independently of GeeLark sessions.

// Find tweets to engage with during warming
xr_search_tweets({ query: "topic relevant to account niche", count: 20 })

// Find good reply targets (scored by viral potential + timing)
xr_find_reply_targets({ topic: "AI", max_age_hours: 2, count: 10 })

// Read a specific user's recent tweets
xr_get_user_tweets({ username: "target_user", count: 20 })

// Get details of a specific tweet (for engagement decisions)
xr_get_tweet({ tweet_id: "1234567890" })

Safety Guardrails

Rate Limiting

• Warming accounts: Follow the warming schedule strictly (see table above)
• Active accounts: Max 50 actions per day recommended
• Delays between actions: 60-120 seconds (randomized) within a session

Unfollow Safety

geelark_unfollow_user carries the highest suspension risk on X:

• Never unfollow more per day than you follow
• Never unfollow accounts followed within 48 hours
• Maximum safe rate: 5-10 unfollows/day with 5-minute gaps

Suspension Detection

Use geelark_check_account_health to detect:

• Account suspension
• Account lock
• Challenge/verification requirements
• Run health checks at least once daily for active accounts

Cookie Freshness

• Call geelark_refresh_cookies after every login/operation session
• Stale cookies cause API failures in other tools that may still use them
• Cookie refresh is synchronous (~10 seconds, no polling needed)

Capabilities NOT Available

These features from the old HTTP API layer are not available via GeeLark:

Old Feature	Status	Workaround
Thread posting (x_post_thread)	No direct tool	Post tweets sequentially with geelark_post_tweet + geelark_reply_to_tweet chaining
Media upload (x_upload_media)	No equivalent	Deferred to V2
Timeline reading (x_get_timeline)	Use xr_* instead	xr_get_user_tweets for user timelines, xr_search_tweets for topic search
Notifications (x_get_notifications)	No equivalent	Use xr_search_tweets with @handle mentions filter
Single-tool warming (x_warming_step)	Agent-level	Agent implements warming logic using schedule + individual GeeLark tools

Required Environment Variables

X_VAULT_PASSPHRASE       # Encryption key for account vault

Prerequisites

• GeeLark cloud phone profiles must be created and have Chrome installed
• Accounts must be logged in via geelark_login_x_account before operations
• Proxy should be configured at phone profile level via geelark_update_proxy