How to Install and Use x-twitter in OpenClaw

Open your terminal and run the ClawHub install command. The skill downloads from the ClawHub registry and registers with your local OpenClaw instance. The install output will show four required configuration variables — you will generate these in the next step. The x-twitter skill requires more credentials than single-key integrations because X/Twitter uses OAuth 1.0a with both app-level and user-level credentials. This is normal and necessary for both reading your timeline and posting on your behalf. Don't be concerned by the number of required config keys — the developer portal provides all of them in one place. If `clawhub install` fails, check your network connection and retry. Use `clawhub install x-twitter --force` if a partial install is causing issues.

1clawhub install x-twitter

Go to developer.x.com and sign in with your X/Twitter account. If this is your first time using the developer portal, you will need to apply for a developer account — the free Basic tier is sufficient for OpenClaw integration. The approval process is usually instant for existing accounts in good standing. Once inside the developer portal, click 'Create Project' (or navigate to Projects & Apps). Create a new project, then create a new App within that project. Give it a name like 'OpenClaw Integration'. After creating the app, navigate to the app's Settings tab. Under 'User authentication settings', click 'Set up'. Set app permissions to 'Read and Write' (you need write access to post tweets). The app type should be 'Web App, Automated App or Bot'. For the callback URI and website URL fields, you can use `http://localhost:8080` and `https://openclaw.ai` respectively — these are not used but required by the form. After saving settings, go to the 'Keys and tokens' tab. Here you'll find your API Key and API Secret (app-level credentials). Click 'Generate' next to Access Token and Secret — these are user-level credentials tied to your specific account. Copy all four values immediately and store them safely — the secrets are only shown once.

Add your four X/Twitter credentials to OpenClaw's configuration. Because there are four variables, using the `clawhub config set` command for each is clean and straightforward. Alternatively, add all four to your `~/.openclaw/.env` file in one edit session. The variable names must be exactly as shown — the skill checks for these specific names. After setting all four, run `clawhub reload` to apply the configuration. Verify each one with `clawhub config get` to confirm they're all properly set. If you're setting up OpenClaw for a team where multiple people need Twitter access, each person should generate their own Access Token and Access Token Secret from the same app — they authenticate as their own Twitter account. The API Key and API Secret are app-level and can be shared within a team.

1# Add to ~/.openclaw/.env
2X_API_KEY=your-api-key-here
3X_API_SECRET=your-api-secret-here
4X_ACCESS_TOKEN=your-access-token-here
5X_ACCESS_TOKEN_SECRET=your-access-token-secret-here
6
7# Or set each via clawhub config
8clawhub config set X_API_KEY your-api-key-here
9clawhub config set X_API_SECRET your-api-secret-here
10clawhub config set X_ACCESS_TOKEN your-access-token-here
11clawhub config set X_ACCESS_TOKEN_SECRET your-access-token-secret-here
12
13# Verify all four are set
14clawhub config get X_API_KEY
15clawhub config get X_ACCESS_TOKEN
16
17clawhub reload

Open OpenClaw chat and start with a read query — this tests your credentials without posting anything publicly. Ask OpenClaw to read your home timeline or search for a specific hashtag. A successful read confirms your API Key and API Secret are correct and that your Access Token is properly authorized. Once reading works, test posting with a simple tweet. Write something you don't mind appearing on your timeline — it will post immediately. Include a note to yourself that this is a test, so it's clear in your timeline history. The x-twitter skill returns rich metadata with posts: tweet ID, author, timestamp, text, likes, retweets, reply count, and any attached media URLs. Use this metadata in follow-up prompts — for example, 'reply to tweet ID 12345...' or 'retweet the post from @username about...'. RapidDev can help configure automated Twitter monitoring workflows in OpenClaw — for example, routing specific mention alerts to Slack or setting up competitor tracking that runs on a schedule.

Beyond basic reading and posting, the X/Twitter skill supports several advanced patterns: monitoring specific user timelines on a schedule, tracking hashtag trends over time, and building engagement workflows that draft replies to relevant mentions. **Mention monitoring**: Ask OpenClaw to check your mentions and filter for posts that require a response — questions from customers, positive feedback worth amplifying, or criticism worth addressing. OpenClaw can draft replies for you to review before posting. **List and timeline reading**: If you maintain Twitter lists of industry accounts, ask OpenClaw to read a list timeline and summarize the most important posts from the last 24 hours. This turns Twitter's overwhelming timeline into a curated digest. **Trend detection**: Search for a topic multiple times over a period and ask OpenClaw to identify whether engagement is growing. Combine with the Postiz or Upload Post skill to react quickly when a trend is accelerating. **Thread reading**: Ask OpenClaw to retrieve the full context of a thread by post ID — useful when someone replies to a conversation and you want to see the full chain before engaging.

1# Optional skill config
2# ~/.openclaw/skills/x-twitter.yaml
3x-twitter:
4  default_count: 20           # number of results per query (max 100)
5  include_retweets: false     # exclude retweets from timeline reads
6  default_language: en        # filter search results by language
7  tweet_mode: extended        # get full text (not truncated at 140 chars)