X
Read & act on X (Twitter) with the user's own login cookies (BYOC) — post tweets (text / images / video / threads / replies / quotes), search tweets & users, read timelines and single tweets, like / retweet / follow / delete, and see trends. Use when the user mentions X / Twitter, 发推 / 发推特 / 推特, "我的 Twitter", posting to X, searching X, or reading their X timeline.From its SKILL.md
npx -y skills add AceDataCloud/Skills --skill xAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 13 stars13 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its file declares
Copied from the file, not written here
The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
7.3 KB, ~1.6k tokens by cl100k_base, as published. Nobody here has run it
x — read & post on X (Twitter) via your own cookies
Drives the user's real X account through X's internal web API via
twikit, authenticated by the login cookie they
captured with the ACE extension. No official API key, no cost.
E2E-verified on 2026-07-06 with a real connected account for: cookie load, whoami, tweet search, user search, home timeline, trends, tweet detail, and post dry-run. Live writes still require explicit confirmation and were not executed in the verification run.
The connector injects the cookie jar as an env var:
X_COOKIES— a JSON array of cookies (needs at leastauth_token+ct0). Secret — full account access. Never echo or print it.
Setup — verify the shipped CLI
twikit is preinstalled in the hosted sandbox image. Do not pip install it at
runtime; if import fails, report that the sandbox image is missing the X skill
dependency and stop.
python3 -c "import twikit" || { echo "sandbox missing twikit; deploy the sandbox skill dependencies image" >&2; exit 1; }
# $SKILL_DIR can point at another skill loaded this turn — anchor on our own
# script (re-run this setup at the top of every fresh-shell Bash block below).
X="$SKILL_DIR/scripts/x.py"; [ -f "$X" ] || X=$(find /tmp -maxdepth 8 -path '*/skills/*/scripts/x.py' 2>/dev/null | head -1)
[ -f "$X" ] || { echo "x script not found (SKILL_DIR=$SKILL_DIR)" >&2; exit 1; }
python3 "$X" whoami # confirm the shipped CLI can read the authenticated account
Read commands (run directly)
python3 $X whoami --expect GermeyAce # verify this exact account
python3 $X whoami # discover the authenticated account
python3 $X search --query "ai agents" --product Latest --limit 20 # Top | Latest | Media
python3 $X search-users --query "openai" --limit 10
python3 $X timeline --limit 20 # my home timeline
python3 $X user-tweets --user elonmusk --type Tweets --limit 20 # Tweets|Replies|Media|Likes
python3 $X tweet --id 1234567890123456789 # single tweet detail
python3 $X trends --category trending --limit 20 # trending|for-you|news|sports|entertainment
--user accepts either an @screen_name (the @ is optional) or a numeric id.
Verify the connection first
python3 $X whoami --expect GermeyAce
# → {"id": "...", "screen_name": "GermeyAce", "identity_verified": true, ...}
whoami reads the authenticated account's screen name from X account settings,
then resolves its public profile. --expect compares that server-authenticated
screen name with the required account before any write. This avoids X's
Cloudflare-blocked UserByRestId endpoint without trusting a local identity
cookie. Always use --expect when the user names the required account.
On an actual auth error the cookie is expired — have the user reconnect at
https://auth.acedata.cloud/user/connections. A Cloudflare block is different:
reconnecting cookies does not fix it. Use --expect for identity checks; other
blocked endpoints need X_PROXY or the official X API. Do not loop-retry.
Write commands — GATED (dry-run unless trailing --confirm)
Every state-changing command (post, thread, like, unlike, retweet,
unretweet, follow, unfollow, delete) dry-runs without a trailing
--confirm. --confirm is honored only as the last argument, so a tweet
body that merely contains "--confirm" can never silently post. Always show the
dry-run, get an explicit "yes" on the exact text, then re-run with --confirm.
python3 $X post --text "hello world" # dry-run
python3 $X post --text "hello world" --confirm # LIVE tweet
python3 $X post --text "look at this" --media a.jpg,b.png --confirm # up to 4 images (or 1 video)
python3 $X post --text "great point" --reply-to 123456 --confirm # reply
python3 $X post --text "worth reading" --quote-url https://x.com/u/status/123 --confirm # quote
python3 $X thread --text "1/2 first" --text "2/2 second" --confirm # thread (2+ segments)
python3 $X like --id 123456 --confirm
python3 $X retweet --id 123456 --confirm
python3 $X follow --user elonmusk --confirm
python3 $X delete --id 123456 --confirm # delete one of MY tweets
- A confirmed
post/threadis immediately PUBLIC on the user's real account — there is no draft step. Always confirm the exact text first. --mediatakes comma-separated file paths. X allows up to 4 images OR 1 video/GIF per tweet; for a thread the media attaches to the first segment only.
Gotchas
- This is the user's real X account. Confirm before any write — posts are immediate and public.
- Live writes are not E2E-verified. Read commands were verified on 2026-07-06; validate the first confirmed write carefully.
- twikit is a scraper of X's non-public API. It can break when X changes its
internal endpoints. The bundled script carries an AceDataCloud compatibility
patch for the current
ondemand.swebpack chunk map used to generate transaction IDs. IfCouldn't get KEY_BYTE indicesappears again, report it as X/twikit upstream drift — do NOT ask the user to reconnect cookies for that specific error. - X currently returns a dependency error for its dedicated
UserMediaquery. The CLI falls back to the normal Tweets timeline and filters media posts locally; the response includes afallbackfield when this happens. - ToS / rate-limit / ban risk. This acts through the web API, not the official API — high-frequency automation can get the account rate-limited or suspended. Keep volume human-like.
- Never print
X_COOKIES— it is full account access. - DMs are intentionally not exposed by this skill.
Record the output
After you successfully publish and obtain the live result URL, call the built-in
publish_artifact tool ONCE so the user can track this deliverable in My Outputs:
publish_artifact(kind="message", channel="x", title="<title>", url="<the REAL returned URL>", status="delivered")
Use the real returned URL — never fabricate one. Call it once per published item,
only after delivery is confirmed; skip it (or use status="failed") if publishing failed.
See _shared/artifacts.md.
What ships with it: 1 file
24.6 KB alongside SKILL.md, 1 of them executable
scripts/
- x.pyruns24.6 KB