OpenClaw Skill

x-twitter-by-altf1be

Post tweets, threads, and media to X/Twitter via API v2 — secure OAuth 1.0a signing, minimal dependencies (commander + dotenv only).

Install

$npx clawhub@latest install x-twitter-by-altf1be
All-time installs4
Active installs3
Stars1

X/Twitter by @altf1be

Post tweets, threads, and media to X/Twitter via the X API v2 with secure OAuth 1.0a signing.

Setup

  1. Get API keys from https://developer.x.com
  2. Set environment variables (or create .env in {baseDir}):
X_CONSUMER_KEY=your-api-key
X_CONSUMER_SECRET=your-api-secret
X_ACCESS_TOKEN=your-access-token
X_ACCESS_TOKEN_SECRET=your-access-token-secret
  1. Install dependencies: cd {baseDir} && npm install

Commands

bash
# Verify connection
node {baseDir}/scripts/xpost.mjs verify

# Post a tweet
node {baseDir}/scripts/xpost.mjs tweet "Hello from OpenClaw! 🦞"

# Post with image
node {baseDir}/scripts/xpost.mjs tweet "Check this out!" --media ./screenshot.png

# Reply to a tweet
node {baseDir}/scripts/xpost.mjs tweet "Great point!" --reply 1234567890

# Post a thread (inline)
node {baseDir}/scripts/xpost.mjs thread "First tweet" "Second tweet" "Third tweet"

# Post a thread (from file, tweets separated by ---)
node {baseDir}/scripts/xpost.mjs thread --file ./thread.md

Thread file format

Create a file with tweets separated by ---:

🚀 Announcing something cool!
---
Here's why it matters...
---
Check it out: https://example.com
#OpenSource #AI

Security

  • OAuth 1.0a user context signing (no app-only auth for write operations)
  • No credentials printed to stdout
  • API calls use pure Node.js fetch + built-in node:crypto (no third-party HTTP or OAuth libraries)
  • Minimal dependencies: only commander (CLI framework) and dotenv (env loading)

Author

Abdelkrim BOUJRAF — ALT-F1 SRL, Brussels 🇧🇪 X: @altf1be

Persistent memory

Give your OpenClaw agent a memory layer

Mem0 remembers users and context across sessions so you send fewer tokens and get better answers.

Try Mem0Mem0 + OpenClaw guide