x-publish

Automate saving tweets and threads to X drafts via Playwright.

320|49|Updated Jan 20, 2026
One-click install
npx skills add https://github.com/kangarooking/x-skills --skill x-publish
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: x-publish
Source: https://github.com/kangarooking/x-skills/tree/main/x-publish
Command: npx skills add https://github.com/kangarooking/x-skills --skill x-publish

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pyobjc-framework-Cocoa, pyperclip, pywin32, and includes scripts (resource) components.

What problem does it solve?

This skill automates saving content to X drafts instead of publishing, ensuring a safe, reviewable workflow for social media posts.

Core Features & Use Cases

  • Automates saving single tweets and threaded content to X drafts
  • Uses Playwright-based browser automation to navigate and save drafts
  • Verifies user login status and prevents accidental immediate publication

Quick Start

Provide your tweet or thread content and run the publish-to-draft flow to save it to your X drafts.

Frequently Asked Questions about x-publish

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I save tweets to X drafts using browser automation?

You can save tweets to X drafts by running a Playwright-based browser automation flow that navigates to X, verifies your login status, inputs your content, and explicitly triggers the save-to-draft action to ensure non-auto-publish behavior.

Can I automate saving a multi-tweet thread to X drafts?

Yes, the automation supports saving multi-tweet threaded content to X drafts. It handles the workflow by validating your content structure and applying explicit save-to-draft steps for each tweet in the thread.

Does saving content to X drafts via automation prevent accidental publishing?

Yes, the automation explicitly prevents accidental immediate publication by enforcing a safe, reviewable workflow that only saves content to drafts, requiring you to manually publish from drafts after validation.

Do I need to log in to X every time I run the draft automation?

No, the automation relies on user login persistence. It verifies your login status at runtime to maintain the session without requiring manual authentication on every execution.

What is the best way to automate a safe review workflow for X content creation?

The best way is to use a draft-saving automation flow that inputs your tweet content and applies explicit save-to-draft steps, ensuring a reviewable workflow where you manually publish from drafts after validation.