agentleFS
HeyvhuangHeyvhuang/ship-faster/skills/tool-x-article-publisher/SKILL.md

tool-x-article-publisher

Skill337 starsChanged 10 months agoMITView on GitHub

Publish Markdown to X (Twitter) Articles as a draft (never auto-publish). Use when the user asks to publish/post an article to X Articles, convert Markdown to X Articles rich text, or mentions "X article", "publish to X", "post to Twitter articles". Converts Markdown → HTML, pastes rich text, and inserts images deterministically.

  • Installs packages

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    User must be logged in: before automation starts.

    line 13

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

X Article Publisher

Publish Markdown content into X (Twitter) Articles as a draft, preserving formatting via rich text paste and deterministic image insertion.

Hard Rules (Safety)

  1. Never auto-publish (draft only; user publishes manually).
  2. User must be logged in before automation starts.
  3. First image = cover image (if any).

Prerequisites

  • Browser automation available (Playwright MCP or equivalent)
  • X account can access Articles (Premium / Premium Plus)
  • macOS recommended (clipboard helper uses Cocoa)
  • Python 3.9+ with:
    • pip install Pillow pyobjc-framework-Cocoa

Inputs / Outputs (Recommended)

Inputs (paths only):

  • article_md_path: Markdown file to publish
  • Optional: run_dir for artifacts (otherwise use /tmp/)

Outputs (recommended artifacts):

  • /tmp/x_article.json (parsed structure)
  • /tmp/x_article.html (HTML body for paste)
  • Optional: run_dir/evidence/x-article-draft.md (what was done + links)

Bundled Scripts

Installed path (typical):

  • ~/.claude/skills/tool-x-article-publisher/scripts/parse_markdown.py
  • ~/.claude/skills/tool-x-article-publisher/scripts/copy_to_clipboard.py

Runbook (Step-by-step)

Follow: references/runbook.md

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.