x post

The problem

Managing X/Twitter content from a terminal or IDE usually requires fighting with OAuth2, handling complex character counting for emojis/URLs, and manually splitting text into threads. Scaling this process or scheduling posts without leaving your development environment is a friction-heavy task.

What it does

• Automates multi-post thread creation by splitting long-form content at paragraph or sentence boundaries.
• Handles X-specific character counting rules, including double-weighting for emojis and URL length calculations.
• Supports media uploads for up to 4 images or a 2-minute video per post.
• Schedules posts and threads for future delivery using ISO 8601 timestamps.
• Provides manual thread control via simple three-dash syntax for precise structural breaks.

Frameworks & tools

Publora MCP server, X/Twitter API, and standard REST API fallback.

Why this beats prompting it yourself

Standard LLM prompts often fail to account for the exact 280-character limit when emojis or links are present, leading to API rejection. This skill uses the Publora MCP to handle the actual mechanics of thread numbering (1/N), media conversion to PNG, and authenticating with the X API securely.

Use cases

• Schedule product launch threads directly from your project's README or notes.
• Automate technical "Build in Public" updates during development sessions.
• Post screenshots of UI changes to X without opening a browser.
• Bulk-schedule content using a simple local text file as a source.

Known limitations

Requires a paid Publora Pro or Premium plan. Video duration is capped at 2 minutes per API limits. Threads can only attach media to the first post. Animated GIFs will lose animation during auto-conversion.