post-to-x_skill

Overview

This skill posts content and articles to X (Twitter) using a real Chrome browser and the Chrome DevTools Protocol to avoid automation detection. It supports regular tweets with up to four images and X Articles (rich long-form posts) from Markdown. The workflow preserves a persistent Chrome profile so you log in once and then automate composition, preview, and optional submission.

How this skill works

The scripts launch a real Chrome instance with anti-automation flags and use CDP commands to type text, paste images from the system clipboard, and interact with the X DOM. For Articles, Markdown is converted to HTML, images and frontmatter are extracted, and content is pasted into the X Articles editor with images inserted at placeholders. A preview period lets you inspect the composed post before using the --submit flag to publish.

When to use it

• Publish short tweets with text and up to 4 images from a scriptable workflow.
• Publish long-form X Articles from Markdown files with cover images and embedded images.
• Automate posting while avoiding Playwright/Puppeteer blocking by X.
• Prepare drafts and preview content in a real browser session before publishing.
• Integrate into daily logging or content pipelines where repeatable, authenticated posting is required.

Best practices

• Run the first session interactively to log in; the persistent profile saves cookies for future runs.
• Always preview posts (default) and use --submit only when ready to publish.
• Limit images to supported formats (PNG, JPEG, GIF, WebP) and max 4 per tweet.
• For Articles, include frontmatter (title, cover_image) and use placeholders for inline images.
• Set X_BROWSER_CHROME_PATH if Chrome/Chromium is not detected by default.

Example use cases

• Daily developer journal posts combining short commentary and a screenshot.
• Publishing a technical blog post written in Markdown as an X Article with cover image.
• Batch composing multiple tweets with images from a CI job using a saved Chrome profile.
• Rapidly composing content drafts for review with a 30–60 second browser preview window.
• Automating reposts of highlights from reading notes, podcasts, or meeting summaries.