x-api

To safely post a tweet to X, this Skill validates OAuth credentials and enforces 280-character limits via a dry-run gate before executing any write operation. It blocks public publishing until you provide explicit approval during the confirmation turn.

Thread posting with the X API is handled by chaining multiple tweets together after validating content length and credentials. The process performs dry-run validation for each tweet in the thread and stops immediately on any error output or rate-limit warning.

Yes, you need OAuth tokens configured in your environment variables to use this X API posting tool. The Skill automatically selects read versus write authentication modes based on the required operation and validates these credentials before attempting any media upload or tweet posting.

The best way to handle media uploads and tweet posting is using a two-step process with enforced size and format constraints. This approach safely uploads media first, preventing orphaned files, and then publishes the tweet after passing the explicit confirmation gate.

Your tweet posting stops before publishing to the timeline because the Skill enforces a mandatory confirmation gate that blocks write operations without explicit approval. It also halts immediately if dry-run validation detects character limit exceedances or rate-limit warnings.

Yes, you can check rate limits and content validation before an X API write operation through the built-in dry-run gate. The Skill surfaces rate-limit warnings immediately and enforces 280-character limits, stopping the process on any error output before public publishing occurs.