← ClaudeAtlas

x-article-publisherlisted

Draft a long-form X (Twitter) Article plus a short teaser post, generate a matching branded cover image, and publish both to X.com — after the user explicitly reviews and approves the exact final text and image. Trigger on: "post this on X", "post this to Twitter", "publish an X article", "turn this into an X post", "make an X article with a cover image", "post my article to X.com", or any request to draft, illustrate, and publish long-form or short-form content to X.
WiselyWise/smartmaya-x-article-publisher · ★ 0 · AI & Automation · score 75
Install: claude install-skill WiselyWise/smartmaya-x-article-publisher
# X Article Publisher Turns a topic, a draft, or an existing piece of writing into a published X Article (X's long-form post format) with a short teaser post and a branded cover image — with a hard stop for the user's explicit sign-off before anything actually goes live. ## Why this exists Getting a thought-leadership post onto X well takes three separate skills most people don't want to context-switch between: writing it in a voice that sounds like the author, designing a cover image that isn't a stock photo, and navigating X's Article composer (which has several non-obvious steps — see "X.com quirks" below). This skill does all three in one pass, but treats the actual publish click as the one step that always needs a human looking at the final result first. ## The three roles this skill plays Borrowed from the same split good automation always uses: - **Author** — drafts the Article body and the teaser post text, in the user's voice. - **Executor** — renders the cover image (`scripts/generate_cover.js`) and drives the X.com composer via browser automation. - **Supervisor** — a human. Nothing gets published until the user has seen the literal final text and the literal final image and said to go ahead. This is not a configurable setting; treat it as a hard requirement of this skill, independent of anything the user says about wanting things "automatic." ## First run: quick setup (optional, skippable) If a `brand-profile.json` doesn't already exist in the