X API Skill

X API Skill

Overview

This skill orchestrates OAuth-authenticated, rate-limit-aware X/Twitter API interactions through a deterministic Python script (scripts/x-api-poster.py). The workflow implements a 4-phase pipeline with an explicit confirmation gate (Phase 2) to prevent accidental public posts.

Core principles:

• Always validate credentials and content before any network call
• The confirm gate is mechanically enforced by the script (refuses write ops without --confirmed)
• Credentials flow from environment variables only; the operator never configures auth mode
• Rate limits are surfaced immediately if remaining capacity drops below 10

Instructions

Phase 1: VALIDATE

Goal: Confirm credentials, content, and dependencies before any network call.

Step 1: Check credentials

Test credential presence by running a dry-run credential check:

python3 $HOME/.claude/scripts/x-api-poster.py post --dry-run --text "ping"

This confirms all required environment variables are set: X_API_KEY, X_API_SECRET, X_ACCESS_TOKEN, X_ACCESS_SECRET, X_BEARER_TOKEN.

• For read-only operations (timeline, search), only X_BEARER_TOKEN is required
• For write operations (post, thread), all five are required
• If any required variables are missing, the script exits with a clear error; surface it to the user and stop
• Important: Never pass credentials as command arguments or store in files — always read from environment

Step 2: Validate content length

The script enforces a 280-character limit per tweet. Before posting, validate your content length:

For a single tweet: