メニュー
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.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/tangzheng202202/hermes-skills --skill xitterコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Integrate Darwin evaluation system with skill-manager for automated skill quality assessment and evolution using AI optimization
DevOps tools - Docker, cron jobs, webhooks, troubleshooting
GitHub workflows - repos, PRs, issues, code review
SOC 職業分類に基づく
SKILL.md を表示中
| name | xitter |
| description | 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. |
| version | 1.0.0 |
| author | Siddharth Balyan + Hermes Agent |
| license | MIT |
| platforms | ["linux","macos"] |
| prerequisites | {"commands":["uv"],"env_vars":["X_API_KEY","X_API_SECRET","X_BEARER_TOKEN","X_ACCESS_TOKEN","X_ACCESS_TOKEN_SECRET"]} |
| metadata | {"hermes":{"tags":["twitter","x","social-media","x-cli"],"homepage":"https://github.com/Infatoshi/x-cli"}} |
Use x-cli for official X/Twitter API interactions from the terminal.
This skill is for:
This skill intentionally does not vendor a separate CLI implementation into Hermes. Install and use upstream x-cli instead.
⚠️ 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).
Install upstream x-cli with uv:
uv tool install git+https://github.com/Infatoshi/x-cli.git
Upgrade later with:
uv tool upgrade x-cli
Verify:
x-cli --help
You need these five values from the X Developer Portal:
X_API_KEYX_API_SECRETX_BEARER_TOKENX_ACCESS_TOKENX_ACCESS_TOKEN_SECRETGet them from:
Unfortunately, the official X API splits auth across both app-level and user-level credentials:
X_API_KEY + X_API_SECRET identify your appX_BEARER_TOKEN is used for app-level read accessX_ACCESS_TOKEN + X_ACCESS_TOKEN_SECRET let the CLI act as your user account for writes and authenticated actionsSo yes — it is a lot of secrets for one integration, but this is the stable official API path and is still preferable to cookie/session scraping.
Setup requirements in the portal:
Read and writehttp://localhost:8000/callback (for CLI tools)https://x.com/your_usernamex-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.
If copying Bearer Token from the web portal, it may contain URL-encoded characters like %2B (for +). Decode these before saving:
import urllib.parse
decoded = urllib.parse.unquote("YOUR_ENCODED_TOKEN")
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.
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.
x-cli looks for credentials in ~/.config/x-cli/.env.
If you already keep your X credentials in ~/.hermes/.env, the cleanest setup is:
mkdir -p ~/.config/x-cli
ln -sf ~/.hermes/.env ~/.config/x-cli/.env
Or create a dedicated file:
mkdir -p ~/.config/x-cli
cat > ~/.config/x-cli/.env <<'EOF'
X_API_KEY=your_consumer_key
X_API_SECRET=your_secret_key
X_BEARER_TOKEN=your_bearer_token
X_ACCESS_TOKEN=your_access_token
X_ACCESS_TOKEN_SECRET=your_access_token_secret
EOF
chmod 600 ~/.config/x-cli/.env
x-cli user get openai
x-cli tweet search "from:NousResearch" --max 3
x-cli me mentions --max 5
If reads work but writes fail, regenerate the access token after confirming Read and write permissions.
x-cli tweet post "hello world"
x-cli tweet get https://x.com/user/status/1234567890
x-cli tweet delete 1234567890
x-cli tweet reply 1234567890 "nice post"
x-cli tweet quote 1234567890 "worth reading"
x-cli tweet search "AI agents" --max 20
x-cli tweet metrics 1234567890
x-cli user get openai
x-cli user timeline openai --max 10
x-cli user followers openai --max 50
x-cli user following openai --max 50
x-cli me mentions --max 20
x-cli me bookmarks --max 20
x-cli me bookmark 1234567890
x-cli me unbookmark 1234567890
x-cli like 1234567890
x-cli retweet 1234567890
Use structured output when the agent needs to inspect fields programmatically:
x-cli -j tweet search "AI agents" --max 5
x-cli -p user get openai
x-cli -md tweet get 1234567890
x-cli -v -j tweet get 1234567890
Recommended defaults:
-j for machine-readable output-v when you need timestamps, metrics, or metadatax-cli is installeduser get, tweet search, me mentions)-j when extracting fields for later stepsx-cli requires OAuth 1.0a (Consumer Key + Access Token). OAuth 2.0 (Client ID only) won't work.Read and write.tweet quote is often more reliable than tweet reply.~/.hermes/.env, make sure ~/.config/x-cli/.env still points at the current file.If you need to post without paying $100/month:
| Platform | API Cost | Notes |
|---|---|---|
| Bluesky | Free | Open protocol, official API, growing fast |
| Mastodon | Free | Open source, self-hostable, many instances |
| Nostr | Free | Decentralized, no API limits |
| Browser Automation | Free | Use Playwright/Selenium to automate x.com (risky, can break) |
x-cli accepts both.