Markdown to X Article (riba2534/x-article-post)Partly tested🇨🇳 CN

Writing X Articles in Markdown: @riba2534's Chrome extension and xap bridge turn Markdown into an X Article draft in one click (a Claude Code Skill is included)

X's Article editor doesn't keep pasted Markdown—code, tables and math have to be inserted by hand. Chinese author @riba2534 open-sourced Markdown to X Article (MIT, Chrome MV3): write Markdown in a side panel, then write native X headings/lists/code/tables/LaTeX into a draft; Mermaid is rendered locally and uploaded. It only creates drafts—never publishes. A local xap bridge (127.0.0.1:17345) and Claude Code Skill let an agent preflight and create drafts. Needs Chrome 116+, an X login, and X Premium for Articles. On the box after npm ci, vitest: 368/371 passed, 2 skipped; the "200 KB convert under 300ms" case failed at ~757ms here. We did not load the extension or write a real X draft.

Visit site Markdown to X Article (riba2534/x-article-post) ↗
Pricing
Free
Region
Global
Where it's from
Chinese community
Added
Nov 4, 2026
Tested on
Nov 4, 2026
Version we used
x-article-post v1.0.64 (GitHub tag); package.json 1.0.0; vitest 5.0.5
Categories
WritingProductivity
Original author
riba2534 @riba2534 ↗
Our test
Partly tested
Cost / time
Extension and bridge are free/open source. X Articles need an X Premium (or higher) plan; the agent path needs local Node 22+.
Source
X @riba2534 ↗GitHub riba2534/x-article-post ↗

The task

Turn Markdown from a blog or notes (code, tables, math, Mermaid, images) into an X Article draft, optionally via Claude Code over a local bridge, then review and publish yourself.

Steps

  1. Download the latest extension zip from GitHub Releases (we saw tag v1.0.64), enable Developer mode on chrome://extensions, and Load unpacked. Needs Chrome 116+, an x.com login, and X Premium for Articles.
  2. Open the side panel, paste or write Markdown; optional front matter title / featured_image. Create draft (or append/replace the current one). Keep the X tab visible while it writes; many images can take minutes.
  3. Open the draft and review. Downgraded syntax (e.g. H3+ → bold paragraphs, long code splits) shows in the report; publish yourself in X—the extension never auto-posts.
  4. For agents: Node ≥22, run `node xap.mjs serve` (Release asset or `npm run bridge` in-repo); first run writes `~/.config/x-article-post/token`. In Settings → Agent bridge: enable, URL `ws://127.0.0.1:17345/ext`, paste `xap token`.
  5. Copy `skills/markdown-to-x-article` into `~/.claude/skills/` (or the Release skill zip). Agent: `xap status` / `xap convert article.md`, then `xap draft article.md`. For remote images, allow reading all site images in settings first.

Prompt

Use Markdown to X Article to turn this note into an X Article draft: confirm the xap bridge and extension are connected, run convert and explain any warnings, wait for my OK, then draft—create a draft only, never publish. Note path: ./notes/post.md

What the author says

@riba2534: posting Markdown on X was painful, so he built this Chrome extension. Native formatting (headings, lists, quotes, links, bold/italic), highlighted code blocks, tables and LaTeX, Mermaid rendered locally to PNG, images fetched/converted/uploaded, title/cover from front matter, preview with a downgrade report; drafts only. Local API + Claude Code Skill for agents. Free, MIT.

Our test

Cloned riba2534/x-article-post (v1.0.64), npm ci, npm test (vitest). Read README and skills/markdown-to-x-article/SKILL.md. Did not load the Chrome extension, start xap serve, sign into X, or create a real draft.

What we found when we tried it:vitest: 18 passed / 1 failed / 1 skipped files; 368 passed / 1 failed / 2 skipped tests. Failure: "converts a 200 KB document within the time budget" (300ms budget, ~757ms on this box). Other convert/bridge unit tests passed.

How to get in

GitHub Releases zip; needs Chrome and x.com. X Articles require Premium on any account. Original post in Chinese.

Who it suits

People who publish long technical posts as X Articles; authors who want Claude Code to draft and will publish themselves.

Pitfalls

  • Without X Premium there is no Article editor—the extension can't help.
  • Keep the X tab visible while writing; allow reading all site images or agent drafts skip remote images into warnings.
  • H3+, footnotes and some HTML are downgraded—read the convert report before draft.
  • Our run: vitest 368/371; the large-doc timing assert failed on this box (~757ms vs 300ms budget); we did not E2E-write a real Chrome/X draft.

More in this category