Interact with X/Twitter via the x-cli terminal client using official X API credentials. Use for posting, reading timelines, searching tweets, liking, retweeting, bookmarks, mentions, and user lookups.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
Interact with X/Twitter via the x-cli terminal client using official X API credentials. Use for posting, reading timelines, searching tweets, liking, retweeting, bookmarks, mentions, and user lookups.
Use x-cli for official X/Twitter API interactions from the terminal.
This skill is for:
posting tweets, replies, and quote tweets
searching tweets and reading timelines
looking up users, followers, and following
liking and retweeting
checking mentions and bookmarks
This skill intentionally does not vendor a separate CLI implementation into Hermes. Install and use upstream x-cli instead.
Important Cost / Access Note
⚠️ CRITICAL (2024+): X API free tier no longer supports posting tweets. Free tier = read-only. To post, you need Basic tier ($100/month) or higher.
If you get HTTP 402: CreditsDepleted, your account doesn't have write credits. This is a billing issue, not a configuration problem.
Expect to need paid X developer access for any write operations. If commands fail with permissions or quota errors, check your X developer plan first.
Tier
Price
Read Limit
Post Tweets
Free
$0
500/month
❌ NOT ALLOWED
Basic
$100/month
10K/month
✅ Yes
Pro
$5000/month
1M/month
✅ Yes
If you get HTTP 402 CreditsDepleted, your Free account cannot post tweets. You must upgrade to Basic ($100/mo) or use browser automation (unofficial, risky).
Generate or regenerate the access token + access token secret after enabling write permissions
Save all five values carefully — missing any one of them will usually produce confusing auth or permission errors
OAuth 1.0a vs OAuth 2.0
x-cli requires OAuth 1.0a. If you only see "Client ID" and "Client Secret" in your portal, you have OAuth 2.0 which won't work. Look for "Consumer Keys" section instead.
Bearer Token URL Encoding
If copying Bearer Token from the web portal, it may contain URL-encoded characters like %2B (for +). Decode these before saving:
Note: upstream x-cli expects the full credential set to be present, so even if you mostly care about read-only commands, it is simplest to configure all five.
Cost / Friction Reality Check
If this setup feels heavier than it should be, that is because it is. X’s official developer flow is high-friction and often paid. This skill chooses the official API path because it is more stable and maintainable than browser-cookie/session approaches.
If the user wants the least brittle long-term setup, use this skill. If they want a zero-setup or unofficial path, that is a different trade-off and not what this skill is for.
Where to Store Credentials
x-cli looks for credentials in ~/.config/x-cli/.env.
If you already keep your X credentials in ~/.hermes/.env, the cleanest setup is:
