＋ Add to collection

Install (CLI)

npx skillmds add jimliu/baoyu-post-to-x

Or Copy and Paste in Your Agent chat

Please install the Agent Skill "jimliu/baoyu-post-to-x" for me from skillmd.com. A SkillMD skill is a SKILL.md file — plain markdown plus a few companion files — that you save into my skills directory. Use whichever fetch route fits your setup: (1) if you have a terminal, run npx -y skillmds add jimliu/baoyu-post-to-x; (2) otherwise fetch the file manifest at https://api.skillmd.com/api/skills/jimliu/baoyu-post-to-x/bundle?format=manifest and download each listed file from its "url" into baoyu-post-to-x/ in your skills directory; (3) if the SkillMD MCP tools are connected, call skillmd_download with slug "jimliu/baoyu-post-to-x" and save the returned files under baoyu-post-to-x/. Show me the SKILL.md before saving if you'd like me to review it. If your skills directory is read-only (e.g. the Claude desktop app), save the files to a working folder instead and tell me — I'll add them through my app's skills settings.

README badge

Show this skill's registry status in your repo:

[![SkillMD](https://skillmd.com/badge/jimliu/baoyu-post-to-x.svg)](https://skillmd.com/skills/jimliu/baoyu-post-to-x)

baoyu-post-to-x

Name: baoyu-post-to-x
Rating: 4.2 (5 reviews)
Author: Jim Liu (baoyu)

jimliu/baoyu-post-to-x · Agent Skill (multi-file)

by Jim Liu (baoyu) · bundle

Published Jul 5, 2026 · Last updated Jul 6, 2026

Posts text, images, videos, and long-form Markdown articles to X (Twitter) using a real Chrome browser with multiple automation modes.

SKILL.md

Post to X (Twitter)

Posts text, images, videos, and long-form articles to X via a real Chrome browser.

In Codex, do not conflate these browser paths:

Codex Chrome plugin / @chrome / Chrome Extension: use the bundled chrome:Chrome skill and its Node REPL browser client. This is required whenever the user says "Codex Chrome plugin", "Codex 自带的 Chrome 插件", @chrome, or similar.
Chrome Computer Use: use mcp__computer_use__.* against the visible Google Chrome UI only when the user asks for Computer Use or no Chrome-plugin preference is stated and Computer Use is available.
CDP script mode: use only as a fallback when the selected mode is unavailable or the user explicitly asks for CDP/script mode.

Script Directory

Important: All scripts are located in the scripts/ subdirectory of this skill.

Agent Execution Instructions:

Determine this SKILL.md file's directory path as {baseDir}
Script path = {baseDir}/scripts/<script-name>.ts
Replace all {baseDir} in this document with the actual path
Resolve ${BUN_X} runtime: if bun installed → bun; if npx available → npx -y bun; else suggest installing bun

Script Reference:

Script	Purpose
`scripts/x-browser.ts`	Regular posts (text + images), CDP fallback
`scripts/x-video.ts`	Video posts (text + video), CDP fallback
`scripts/x-quote.ts`	Quote tweet with comment, CDP fallback
`scripts/x-article.ts`	Long-form article publishing (Markdown), CDP fallback
`scripts/md-to-html.ts`	Markdown → HTML conversion
`scripts/copy-to-clipboard.ts`	Copy content to clipboard
`scripts/paste-from-clipboard.ts`	Send real paste keystroke
`scripts/check-paste-permissions.ts`	Verify environment & permissions

Execution Mode Selection (Required)

Choose exactly one mode before interacting with X:

If the user explicitly asks for the Codex Chrome plugin, @chrome, the Chrome extension, or "Codex 自带的 Chrome 插件", use Codex Chrome Plugin Mode. Do not call Computer Use first.
If the user explicitly asks for Chrome Computer Use, use Chrome Computer Use Mode. Do not fall back to CDP, Playwright, the in-app Browser, or the Chrome plugin without telling the user and getting approval.
If the user explicitly asks for CDP/script mode, use CDP Script Mode.
Otherwise, prefer Chrome Computer Use Mode. For Markdown X Articles with local content images, use the tested X editor flow: insert each body image from the toolbar (Insert -> Media -> dialog icon button Add photos or video) at its placeholder, then delete the placeholder text. Use CDP Script Mode only when the selected browser-control mode is unavailable or the UI upload/selection flow is unreliable.

Never use the in-app Browser for X publishing workflows.

Codex Chrome Plugin Mode

Use this mode whenever the user requests the Codex Chrome plugin, @chrome, or the Chrome Extension path. This uses the user's real Chrome profile and X login through the bundled Chrome plugin, not Computer Use and not CDP.

Setup

Load the chrome:Chrome skill before browser work.
Use tool_search for node_repl js if the Node REPL js tool is not already visible.
Initialize the Chrome browser client exactly as the Chrome skill specifies, then run a lightweight call such as browser.user.openTabs() to verify the extension connection.
If the first lightweight call fails, wait 2 seconds and retry once. If it still fails, follow the Chrome skill's extension checks and recovery steps. If checks pass but communication still fails, ask the user before opening a new Chrome window. Do not switch to Computer Use or CDP silently.

General rules

Use the Chrome plugin's browser.tabs.*, tab.playwright.*, tab.cua.*, and file chooser APIs for X UI actions.
Shell commands are allowed for Markdown preprocessing and rich-HTML clipboard preparation. For X Article body images, do not rely on image clipboard paste; use the editor's Insert -> Media upload flow.
If a file upload fails with Not allowed, tell the user: To enable file upload, go to chrome://extensions in Chrome, click Details under the Codex extension, and enable "Allow access to file URLs." See https://developers.openai.com/codex/app/chrome-extension#upload-files for details.
If the Chrome plugin reports native pipe is closed, retry the lightweight browser call once after 2 seconds, then run the Chrome skill health checks. If Chrome is running, the extension is enabled, and the native host manifest is correct, ask permission to open a new Chrome window and retry. Do not keep sending browser actions through the broken pipe.
Never click Publish, Post, or any externally visible submit action without explicit final confirmation from the user in the current conversation.

X Articles

Convert Markdown and keep the image map:

${BUN_X} {baseDir}/scripts/md-to-html.ts article.md --save-html /tmp/x-article-body.html > /tmp/x-article.json

Read the JSON output for title, coverImage, and contentImages (placeholder → localPath).
Open or create the article draft at https://x.com/compose/articles.
Upload the cover with the Chrome plugin file chooser flow. If upload is blocked by extension permissions, stop and report the exact permission fix above.

Fill the title, then copy rich HTML:

${BUN_X} {baseDir}/scripts/copy-to-clipboard.ts html --file /tmp/x-article-body.html

Paste into the article body with a real paste keystroke through the Chrome plugin. On macOS use Meta+V.
Verify the editor text contains the article body and XIMGPH_ placeholders. Do not rely on tab.clipboard.readText() as proof of the system clipboard after shell clipboard writes; on macOS verify with pbpaste if needed.
For each contentImages item in placeholder order:
- Locate the visible placeholder text (XIMGPH_N) and click it to place the caret there.
- Open the toolbar menu Insert -> Media.
- In the modal, click the icon button with aria-label="Add photos or video"; do not click the text/dropzone or hidden file input.
- Use the file chooser to upload that image's localPath.
- After the image appears, if XIMGPH_N remains above it, select exactly that placeholder and press Delete first. Use Backspace only if Delete fails and the selected text is confirmed to be exactly the placeholder.
- Verify the placeholder count for that XIMGPH_N is 0.
Open Preview and verify title, cover, body, links, and images.
Ask for explicit confirmation before clicking Publish.

Preferences (EXTEND.md)

Check EXTEND.md in priority order — the first one found wins:

Priority	Path	Scope
1	`.baoyu-skills/baoyu-post-to-x/EXTEND.md`	Project
2	`${XDG_CONFIG_HOME:-$HOME/.config}/baoyu-skills/baoyu-post-to-x/EXTEND.md`	XDG
3	`$HOME/.baoyu-skills/baoyu-post-to-x/EXTEND.md`	User home

If none found, use defaults.

EXTEND.md supports: Default Chrome profile

Prerequisites

Google Chrome or Chromium
bun runtime
First run: log in to X manually (session saved)

Pre-flight Check (Optional)

Before first use, suggest running the environment check. User can skip if they prefer.

${BUN_X} {baseDir}/scripts/check-paste-permissions.ts

Checks: Chrome, profile isolation, Bun, Accessibility, clipboard, paste keystroke, Chrome conflicts.

If any check fails, provide fix guidance per item:

Check	Fix
Chrome	Install Chrome or set `X_BROWSER_CHROME_PATH` env var
Profile dir	Shared profile at `baoyu-skills/chrome-profile` (see CLAUDE.md Chrome Profile section)
Bun runtime	`brew install oven-sh/bun/bun` (macOS) or `npm install -g bun`
Accessibility (macOS)	System Settings → Privacy & Security → Accessibility → enable terminal app
Clipboard copy	Ensure Swift/AppKit available (macOS Xcode CLI tools: `xcode-select --install`)
Paste keystroke (macOS)	Same as Accessibility fix above
Paste keystroke (Linux)	Install `xdotool` (X11) or `ydotool` (Wayland)

References

Regular Posts: See references/regular-posts.md for manual workflow, troubleshooting, and technical details
X Articles: See references/articles.md for long-form article publishing guide

Chrome Computer Use Mode

Use this mode when the user explicitly asks for Chrome Computer Use, or when no Chrome-plugin preference is stated and Codex can control Google Chrome with Computer Use. This uses the user's existing Chrome window, cookies, login, extensions, and X session.

General rules:

Start each assistant turn that controls Chrome by calling get_app_state for Google Chrome.
Prefer element-index actions when available; use coordinates only for editor text selection or drag selection.
Do not use the in-app Browser, the Chrome plugin, Playwright, or CDP for X UI actions in this mode unless the user approves a mode change.
Never click Publish, Post, or any externally visible submit action without an explicit final confirmation from the user in the current conversation.

Regular posts:

Open or navigate Chrome to https://x.com/compose/post.
Type the post text into the composer using Computer Use.

For each image, run:

${BUN_X} {baseDir}/scripts/copy-to-clipboard.ts image /absolute/path/to/image.png

Paste with Computer Use (super+v on macOS, control+v on Windows/Linux), then wait until X finishes uploading media.
Ask for confirmation before clicking Post.

Video posts:

Open or navigate Chrome to https://x.com/compose/post.
Type the post text into the composer.
Use the visible media upload/file picker UI to attach the video.
Wait for upload and processing to complete.
Ask for confirmation before clicking Post.

Quote tweets:

Open the tweet URL in Chrome.
Use the visible quote/repost UI to choose Quote.
Type the comment.
Ask for confirmation before clicking Post.

X Articles:

Convert Markdown and keep the image map:

${BUN_X} {baseDir}/scripts/md-to-html.ts article.md --save-html /tmp/x-article-body.html > /tmp/x-article.json

Read the JSON output for title, coverImage, and contentImages (placeholder → localPath).
In Chrome, open https://x.com/compose/articles, create or open the draft, upload the cover if present, and fill the title.

Copy rich HTML to the clipboard:

${BUN_X} {baseDir}/scripts/copy-to-clipboard.ts html --file /tmp/x-article-body.html

Paste into the article body with Computer Use.
For each contentImages entry in placeholder order:
- Locate the exact visible placeholder text such as XIMGPH_3 and click it to set the insertion point.
- Open the toolbar Insert dropdown, choose Media, then click the modal's icon button labeled Add photos or video.
- Use the native file picker to choose the image's localPath.
- Wait until the image block appears and any upload activity is finished.
- If the placeholder remains above the inserted image, reselect exactly that placeholder text and press Delete first. Use Backspace only if Delete fails and the selected text is confirmed to be exactly the placeholder.
Verify no XIMGPH_ placeholders remain and the expected images appear.
Open Preview and verify title, cover, body, links, and images.
Ask for explicit confirmation before clicking Publish.

If Computer Use selection, toolbar upload, or file-picker control becomes unreliable, stop and report the blocker instead of switching to the Chrome plugin or CDP silently.

CDP Script Mode (Fallback)

Use the script sections below only when the selected browser-control mode is unavailable, unreliable, or explicitly not requested. These scripts launch or reuse a real Chrome instance via CDP and keep the browser open for review.

Do not use CDP Script Mode when the user explicitly requires the Codex Chrome plugin or Chrome Computer Use unless the user approves the fallback after you explain the blocker.

Post Type Selection

Unless the user explicitly specifies the post type:

Plain text + within 10,000 characters → Regular Post (Premium members support up to 10,000 characters, non-Premium: 280)
Markdown file (.md) → X Article

Regular Posts

${BUN_X} {baseDir}/scripts/x-browser.ts "Hello!" --image ./photo.png

Parameters:

Parameter	Description
`<text>`	Post content (positional)
`--image <path>`	Image file (repeatable, max 4)
`--profile <dir>`	Custom Chrome profile

Note: Script opens browser with content filled in. User reviews and publishes manually.

Codex mode note: If the user explicitly requested the Codex Chrome plugin, use Codex Chrome Plugin Mode. Otherwise, if Chrome Computer Use is enabled, use Chrome Computer Use Mode instead of running x-browser.ts.

Video Posts

Text + video file.

${BUN_X} {baseDir}/scripts/x-video.ts "Check this out!" --video ./clip.mp4

Parameters:

Parameter	Description
`<text>`	Post content (positional)
`--video <path>`	Video file (MP4, MOV, WebM)
`--profile <dir>`	Custom Chrome profile

Note: Script opens browser with content filled in. User reviews and publishes manually.

Limits: Regular 140s max, Premium 60min. Processing: 30-60s.

Quote Tweets

Quote an existing tweet with comment.

${BUN_X} {baseDir}/scripts/x-quote.ts https://x.com/user/status/123 "Great insight!"

Parameters:

Parameter	Description
`<tweet-url>`	URL to quote (positional)
`<comment>`	Comment text (positional, optional)
`--profile <dir>`	Custom Chrome profile

Note: Script opens browser with content filled in. User reviews and publishes manually.

X Articles

Long-form Markdown articles (requires X Premium).

${BUN_X} {baseDir}/scripts/x-article.ts article.md
${BUN_X} {baseDir}/scripts/x-article.ts article.md --cover ./cover.jpg

Parameters:

Parameter	Description
`<markdown>`	Markdown file (positional)
`--cover <path>`	Cover image
`--title <text>`	Override title

Frontmatter: title, cover_image supported in YAML front matter.

Codex mode note: If the user explicitly requested the Codex Chrome plugin, follow Codex Chrome Plugin Mode above. If the user explicitly requested Chrome Computer Use, follow Chrome Computer Use Mode. Otherwise, prefer Chrome Computer Use; for Markdown articles with local content images, use the toolbar Insert -> Media image-upload workflow before falling back to x-article.ts in CDP Script Mode.

CDP fallback note: The script opens browser with article filled in. User reviews and publishes manually unless --submit is used.

Publish safety: Do not use --submit or click Publish unless the user explicitly confirms the final public publish action.

Post-Composition Check: The script automatically verifies after all images are inserted:

Remaining XIMGPH_ placeholders in editor content
Expected vs actual image count

If the check fails (warnings in output), alert the user with the specific issues before they publish.

Troubleshooting

Chrome debug port not ready

CDP fallback only: if a script fails with Chrome debug port not ready or Unable to connect, kill existing Chrome CDP instances first, then retry:

pkill -f "Chrome.*remote-debugging-port" 2>/dev/null; pkill -f "Chromium.*remote-debugging-port" 2>/dev/null; sleep 2

Important: This should be done automatically — when encountering this error, kill Chrome CDP instances and retry the command without asking the user.

Notes

First run: manual login required (session persists)
In Codex Chrome Plugin Mode and Chrome Computer Use Mode, use the user's existing Chrome session and do not launch a separate CDP profile
CDP scripts only fill content into the browser by default; user must review and publish manually unless --submit is explicitly used
Cross-platform: macOS, Linux, Windows

Extension Support

Custom configurations via EXTEND.md. See Preferences section for paths and supported options.

---
name: baoyu-post-to-x
description: Posts text, images, videos, and long-form Markdown articles to X (Twitter) using a real Chrome browser with multiple automation modes.
---

# Post to X (Twitter)

Posts text, images, videos, and long-form articles to X via a real Chrome browser.

In Codex, do not conflate these browser paths:
- **Codex Chrome plugin / `@chrome` / Chrome Extension**: use the bundled `chrome:Chrome` skill and its Node REPL browser client. This is required whenever the user says "Codex Chrome plugin", "Codex 自带的 Chrome 插件", `@chrome`, or similar.
- **Chrome Computer Use**: use `mcp__computer_use__.*` against the visible Google Chrome UI only when the user asks for Computer Use or no Chrome-plugin preference is stated and Computer Use is available.
- **CDP script mode**: use only as a fallback when the selected mode is unavailable or the user explicitly asks for CDP/script mode.

## Script Directory

**Important**: All scripts are located in the `scripts/` subdirectory of this skill.

**Agent Execution Instructions**:
1. Determine this SKILL.md file's directory path as `{baseDir}`
2. Script path = `{baseDir}/scripts/<script-name>.ts`
3. Replace all `{baseDir}` in this document with the actual path
4. Resolve `${BUN_X}` runtime: if `bun` installed → `bun`; if `npx` available → `npx -y bun`; else suggest installing bun

**Script Reference**:
| Script | Purpose |
|--------|---------|
| `scripts/x-browser.ts` | Regular posts (text + images), CDP fallback |
| `scripts/x-video.ts` | Video posts (text + video), CDP fallback |
| `scripts/x-quote.ts` | Quote tweet with comment, CDP fallback |
| `scripts/x-article.ts` | Long-form article publishing (Markdown), CDP fallback |
| `scripts/md-to-html.ts` | Markdown → HTML conversion |
| `scripts/copy-to-clipboard.ts` | Copy content to clipboard |
| `scripts/paste-from-clipboard.ts` | Send real paste keystroke |
| `scripts/check-paste-permissions.ts` | Verify environment & permissions |

## Execution Mode Selection (Required)

Choose exactly one mode before interacting with X:

1. If the user explicitly asks for the Codex Chrome plugin, `@chrome`, the Chrome extension, or "Codex 自带的 Chrome 插件", use **Codex Chrome Plugin Mode**. Do not call Computer Use first.
2. If the user explicitly asks for Chrome Computer Use, use **Chrome Computer Use Mode**. Do not fall back to CDP, Playwright, the in-app Browser, or the Chrome plugin without telling the user and getting approval.
3. If the user explicitly asks for CDP/script mode, use **CDP Script Mode**.
4. Otherwise, prefer **Chrome Computer Use Mode**. For Markdown **X Articles with local content images**, use the tested X editor flow: insert each body image from the toolbar (`Insert` -> `Media` -> dialog icon button `Add photos or video`) at its placeholder, then delete the placeholder text. Use CDP Script Mode only when the selected browser-control mode is unavailable or the UI upload/selection flow is unreliable.

Never use the in-app Browser for X publishing workflows.

## Codex Chrome Plugin Mode

Use this mode whenever the user requests the Codex Chrome plugin, `@chrome`, or the Chrome Extension path. This uses the user's real Chrome profile and X login through the bundled Chrome plugin, not Computer Use and not CDP.

**Setup**
1. Load the `chrome:Chrome` skill before browser work.
2. Use `tool_search` for `node_repl js` if the Node REPL `js` tool is not already visible.
3. Initialize the Chrome browser client exactly as the Chrome skill specifies, then run a lightweight call such as `browser.user.openTabs()` to verify the extension connection.
4. If the first lightweight call fails, wait 2 seconds and retry once. If it still fails, follow the Chrome skill's extension checks and recovery steps. If checks pass but communication still fails, ask the user before opening a new Chrome window. Do not switch to Computer Use or CDP silently.

**General rules**
- Use the Chrome plugin's `browser.tabs.*`, `tab.playwright.*`, `tab.cua.*`, and file chooser APIs for X UI actions.
- Shell commands are allowed for Markdown preprocessing and rich-HTML clipboard preparation. For X Article body images, do not rely on image clipboard paste; use the editor's `Insert` -> `Media` upload flow.
- If a file upload fails with `Not allowed`, tell the user: `To enable file upload, go to chrome://extensions in Chrome, click Details under the Codex extension, and enable "Allow access to file URLs." See https://developers.openai.com/codex/app/chrome-extension#upload-files for details.`
- If the Chrome plugin reports `native pipe is closed`, retry the lightweight browser call once after 2 seconds, then run the Chrome skill health checks. If Chrome is running, the extension is enabled, and the native host manifest is correct, ask permission to open a new Chrome window and retry. Do not keep sending browser actions through the broken pipe.
- Never click `Publish`, `Post`, or any externally visible submit action without explicit final confirmation from the user in the current conversation.

**X Articles**
1. Convert Markdown and keep the image map:
   ```bash
   ${BUN_X} {baseDir}/scripts/md-to-html.ts article.md --save-html /tmp/x-article-body.html > /tmp/x-article.json
   ```
2. Read the JSON output for `title`, `coverImage`, and `contentImages` (`placeholder` → `localPath`).
3. Open or create the article draft at `https://x.com/compose/articles`.
4. Upload the cover with the Chrome plugin file chooser flow. If upload is blocked by extension permissions, stop and report the exact permission fix above.
5. Fill the title, then copy rich HTML:
   ```bash
   ${BUN_X} {baseDir}/scripts/copy-to-clipboard.ts html --file /tmp/x-article-body.html
   ```
6. Paste into the article body with a real paste keystroke through the Chrome plugin. On macOS use `Meta+V`.
7. Verify the editor text contains the article body and `XIMGPH_` placeholders. Do not rely on `tab.clipboard.readText()` as proof of the system clipboard after shell clipboard writes; on macOS verify with `pbpaste` if needed.
8. For each `contentImages` item in placeholder order:
   - Locate the visible placeholder text (`XIMGPH_N`) and click it to place the caret there.
   - Open the toolbar menu `Insert` -> `Media`.
   - In the modal, click the icon button with `aria-label="Add photos or video"`; do not click the text/dropzone or hidden file input.
   - Use the file chooser to upload that image's `localPath`.
   - After the image appears, if `XIMGPH_N` remains above it, select exactly that placeholder and press `Delete` first. Use `Backspace` only if `Delete` fails and the selected text is confirmed to be exactly the placeholder.
   - Verify the placeholder count for that `XIMGPH_N` is `0`.
9. Open Preview and verify title, cover, body, links, and images.
10. Ask for explicit confirmation before clicking `Publish`.

## Preferences (EXTEND.md)

Check EXTEND.md in priority order — the first one found wins:

| Priority | Path | Scope |
|----------|------|-------|
| 1 | `.baoyu-skills/baoyu-post-to-x/EXTEND.md` | Project |
| 2 | `${XDG_CONFIG_HOME:-$HOME/.config}/baoyu-skills/baoyu-post-to-x/EXTEND.md` | XDG |
| 3 | `$HOME/.baoyu-skills/baoyu-post-to-x/EXTEND.md` | User home |

If none found, use defaults.

**EXTEND.md supports**: Default Chrome profile

## Prerequisites

- Google Chrome or Chromium
- `bun` runtime
- First run: log in to X manually (session saved)

## Pre-flight Check (Optional)

Before first use, suggest running the environment check. User can skip if they prefer.

```bash
${BUN_X} {baseDir}/scripts/check-paste-permissions.ts
```

Checks: Chrome, profile isolation, Bun, Accessibility, clipboard, paste keystroke, Chrome conflicts.

**If any check fails**, provide fix guidance per item:

| Check | Fix |
|-------|-----|
| Chrome | Install Chrome or set `X_BROWSER_CHROME_PATH` env var |
| Profile dir | Shared profile at `baoyu-skills/chrome-profile` (see CLAUDE.md Chrome Profile section) |
| Bun runtime | `brew install oven-sh/bun/bun` (macOS) or `npm install -g bun` |
| Accessibility (macOS) | System Settings → Privacy & Security → Accessibility → enable terminal app |
| Clipboard copy | Ensure Swift/AppKit available (macOS Xcode CLI tools: `xcode-select --install`) |
| Paste keystroke (macOS) | Same as Accessibility fix above |
| Paste keystroke (Linux) | Install `xdotool` (X11) or `ydotool` (Wayland) |

## References

- **Regular Posts**: See `references/regular-posts.md` for manual workflow, troubleshooting, and technical details
- **X Articles**: See `references/articles.md` for long-form article publishing guide

---

## Chrome Computer Use Mode

Use this mode when the user explicitly asks for Chrome Computer Use, or when no Chrome-plugin preference is stated and Codex can control `Google Chrome` with Computer Use. This uses the user's existing Chrome window, cookies, login, extensions, and X session.

**General rules**:
- Start each assistant turn that controls Chrome by calling `get_app_state` for `Google Chrome`.
- Prefer element-index actions when available; use coordinates only for editor text selection or drag selection.
- Do not use the in-app Browser, the Chrome plugin, Playwright, or CDP for X UI actions in this mode unless the user approves a mode change.
- Never click `Publish`, `Post`, or any externally visible submit action without an explicit final confirmation from the user in the current conversation.

**Regular posts**:
1. Open or navigate Chrome to `https://x.com/compose/post`.
2. Type the post text into the composer using Computer Use.
3. For each image, run:
   ```bash
   ${BUN_X} {baseDir}/scripts/copy-to-clipboard.ts image /absolute/path/to/image.png
   ```
4. Paste with Computer Use (`super+v` on macOS, `control+v` on Windows/Linux), then wait until X finishes uploading media.
5. Ask for confirmation before clicking `Post`.

**Video posts**:
1. Open or navigate Chrome to `https://x.com/compose/post`.
2. Type the post text into the composer.
3. Use the visible media upload/file picker UI to attach the video.
4. Wait for upload and processing to complete.
5. Ask for confirmation before clicking `Post`.

**Quote tweets**:
1. Open the tweet URL in Chrome.
2. Use the visible quote/repost UI to choose Quote.
3. Type the comment.
4. Ask for confirmation before clicking `Post`.

**X Articles**:
1. Convert Markdown and keep the image map:
   ```bash
   ${BUN_X} {baseDir}/scripts/md-to-html.ts article.md --save-html /tmp/x-article-body.html > /tmp/x-article.json
   ```
2. Read the JSON output for `title`, `coverImage`, and `contentImages` (`placeholder` → `localPath`).
3. In Chrome, open `https://x.com/compose/articles`, create or open the draft, upload the cover if present, and fill the title.
4. Copy rich HTML to the clipboard:
   ```bash
   ${BUN_X} {baseDir}/scripts/copy-to-clipboard.ts html --file /tmp/x-article-body.html
   ```
5. Paste into the article body with Computer Use.
6. For each `contentImages` entry in placeholder order:
   - Locate the exact visible placeholder text such as `XIMGPH_3` and click it to set the insertion point.
   - Open the toolbar `Insert` dropdown, choose `Media`, then click the modal's icon button labeled `Add photos or video`.
   - Use the native file picker to choose the image's `localPath`.
   - Wait until the image block appears and any upload activity is finished.
   - If the placeholder remains above the inserted image, reselect exactly that placeholder text and press `Delete` first. Use `Backspace` only if `Delete` fails and the selected text is confirmed to be exactly the placeholder.
7. Verify no `XIMGPH_` placeholders remain and the expected images appear.
8. Open Preview and verify title, cover, body, links, and images.
9. Ask for explicit confirmation before clicking `Publish`.

If Computer Use selection, toolbar upload, or file-picker control becomes unreliable, stop and report the blocker instead of switching to the Chrome plugin or CDP silently.

---

## CDP Script Mode (Fallback)

Use the script sections below only when the selected browser-control mode is unavailable, unreliable, or explicitly not requested. These scripts launch or reuse a real Chrome instance via CDP and keep the browser open for review.

Do not use CDP Script Mode when the user explicitly requires the Codex Chrome plugin or Chrome Computer Use unless the user approves the fallback after you explain the blocker.

---

## Post Type Selection

Unless the user explicitly specifies the post type:
- **Plain text** + within 10,000 characters → **Regular Post** (Premium members support up to 10,000 characters, non-Premium: 280)
- **Markdown file** (.md) → **X Article**

## Regular Posts

```bash
${BUN_X} {baseDir}/scripts/x-browser.ts "Hello!" --image ./photo.png
```

**Parameters**:
| Parameter | Description |
|-----------|-------------|
| `<text>` | Post content (positional) |
| `--image <path>` | Image file (repeatable, max 4) |
| `--profile <dir>` | Custom Chrome profile |

**Note**: Script opens browser with content filled in. User reviews and publishes manually.

**Codex mode note**: If the user explicitly requested the Codex Chrome plugin, use **Codex Chrome Plugin Mode**. Otherwise, if Chrome Computer Use is enabled, use **Chrome Computer Use Mode** instead of running `x-browser.ts`.

---

## Video Posts

Text + video file.

```bash
${BUN_X} {baseDir}/scripts/x-video.ts "Check this out!" --video ./clip.mp4
```

**Parameters**:
| Parameter | Description |
|-----------|-------------|
| `<text>` | Post content (positional) |
| `--video <path>` | Video file (MP4, MOV, WebM) |
| `--profile <dir>` | Custom Chrome profile |

**Note**: Script opens browser with content filled in. User reviews and publishes manually.

**Codex mode note**: If the user explicitly requested the Codex Chrome plugin, use **Codex Chrome Plugin Mode**. Otherwise, if Chrome Computer Use is enabled, use **Chrome Computer Use Mode** instead of running `x-video.ts`.

**Limits**: Regular 140s max, Premium 60min. Processing: 30-60s.

---

## Quote Tweets

Quote an existing tweet with comment.

```bash
${BUN_X} {baseDir}/scripts/x-quote.ts https://x.com/user/status/123 "Great insight!"
```

**Parameters**:
| Parameter | Description |
|-----------|-------------|
| `<tweet-url>` | URL to quote (positional) |
| `<comment>` | Comment text (positional, optional) |
| `--profile <dir>` | Custom Chrome profile |

**Note**: Script opens browser with content filled in. User reviews and publishes manually.

**Codex mode note**: If the user explicitly requested the Codex Chrome plugin, use **Codex Chrome Plugin Mode**. Otherwise, if Chrome Computer Use is enabled, use **Chrome Computer Use Mode** instead of running `x-quote.ts`.

---

## X Articles

Long-form Markdown articles (requires X Premium).

```bash
${BUN_X} {baseDir}/scripts/x-article.ts article.md
${BUN_X} {baseDir}/scripts/x-article.ts article.md --cover ./cover.jpg
```

**Parameters**:
| Parameter | Description |
|-----------|-------------|
| `<markdown>` | Markdown file (positional) |
| `--cover <path>` | Cover image |
| `--title <text>` | Override title |

**Frontmatter**: `title`, `cover_image` supported in YAML front matter.

**Codex mode note**: If the user explicitly requested the Codex Chrome plugin, follow **Codex Chrome Plugin Mode** above. If the user explicitly requested Chrome Computer Use, follow **Chrome Computer Use Mode**. Otherwise, prefer Chrome Computer Use; for Markdown articles with local content images, use the toolbar `Insert` -> `Media` image-upload workflow before falling back to `x-article.ts` in **CDP Script Mode**.

**CDP fallback note**: The script opens browser with article filled in. User reviews and publishes manually unless `--submit` is used.

**Publish safety**: Do not use `--submit` or click `Publish` unless the user explicitly confirms the final public publish action.

**Post-Composition Check**: The script automatically verifies after all images are inserted:
- Remaining `XIMGPH_` placeholders in editor content
- Expected vs actual image count

If the check fails (warnings in output), alert the user with the specific issues before they publish.

---

## Troubleshooting

### Chrome debug port not ready

CDP fallback only: if a script fails with `Chrome debug port not ready` or `Unable to connect`, kill existing Chrome CDP instances first, then retry:

```bash
pkill -f "Chrome.*remote-debugging-port" 2>/dev/null; pkill -f "Chromium.*remote-debugging-port" 2>/dev/null; sleep 2
```

**Important**: This should be done automatically — when encountering this error, kill Chrome CDP instances and retry the command without asking the user.

## Notes

- First run: manual login required (session persists)
- In Codex Chrome Plugin Mode and Chrome Computer Use Mode, use the user's existing Chrome session and do not launch a separate CDP profile
- CDP scripts only fill content into the browser by default; user must review and publish manually unless `--submit` is explicitly used
- Cross-platform: macOS, Linux, Windows

## Extension Support

Custom configurations via EXTEND.md. See **Preferences** section for paths and supported options.

Files

This skill is a package of 15 files. Install with the command above, or download the folder.

📄SKILL.md entry
📁references
📄articles.md 13.1 KB
📄regular-posts.md 4.0 KB
📁scripts
⚙️check-paste-permissions.ts 8.1 KB
⚙️copy-to-clipboard.ts 11.9 KB
⚙️md-to-html.test.ts 5.5 KB
⚙️md-to-html.ts 13.1 KB
◆package.json 378 B
⚙️paste-from-clipboard.ts 5.5 KB
⚙️x-article.ts 31.0 KB
⚙️x-browser.ts 8.8 KB
⚙️x-quote.ts 8.9 KB
⚙️x-utils.test.ts 1.6 KB
⚙️x-utils.ts 8.6 KB
⚙️x-video.ts 9.3 KB

JimLiu/baoyu-skills/tree/main/skills/baoyu-post-to-x commit · 6b7a2e4175

▌
baoyu-post-to-x · ecnu-icalk bundle
Posts text, images, videos, and long-form articles to X (Twitter) using a real Chrome browser to bypass anti-bot detection.

559
repo stars
▌
baoyu-post-to-weibo · jimliu bundle
Posts text, images, videos, and long-form Markdown articles to Weibo via a real Chrome browser, bypassing anti-bot detection.

23.1k
repo stars
▌
cookie-sync · browserbase bundle
Exports cookies from a local Chrome browser and saves them into a Browserbase persistent context, enabling authenticated browsing sessions via the browse CLI.

3.6k
repo stars
▌
bird · kbarbel640-del bundle
Read, search, and post to X/Twitter from the command line using browser cookies or the Sweetistics API.

1
repo stars
▌
x-dm-auto-chat · browser-act bundle
Automates X (Twitter) DM workflows: scan inbox, read conversations, generate persona-based replies, and send messages. Also supports searching users and starting new conversations with rate control and E2E passcode unlock.

3.7k
repo stars
▌
clawdcursor · gabrielmoreira bundle
Drives a real desktop GUI as a fallback when APIs, CLIs, file edits, and browser automation are unavailable, letting agents click, type, read the screen, and control apps across Windows, macOS, and Linux.

17
repo stars

Frequently asked questions

How do I install the baoyu-post-to-x skill?

Run npx skillmds add jimliu/baoyu-post-to-x in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the baoyu-post-to-x skill do?

Posts text, images, videos, and long-form Markdown articles to X (Twitter) using a real Chrome browser with multiple automation modes. It is listed under Integrations & APIs, Docs & Writing, Productivity, SaaS Connectors on SkillMD.

Is baoyu-post-to-x safe to use?

SkillMD's automated safety review verdict for this skill is CAUTION. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: executes scripts, makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with baoyu-post-to-x?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is baoyu-post-to-x free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published baoyu-post-to-x?

Jim Liu (baoyu) (@jimliu) published this skill. Their other Agent Skills are listed on their SkillMD profile.

baoyu-post-to-x

Post to X (Twitter)

Script Directory

Execution Mode Selection (Required)

Codex Chrome Plugin Mode

Preferences (EXTEND.md)

Prerequisites

Pre-flight Check (Optional)

References

Chrome Computer Use Mode

CDP Script Mode (Fallback)

Post Type Selection

Regular Posts

Video Posts

Quote Tweets

X Articles

Troubleshooting

Chrome debug port not ready

Notes

Extension Support

Files

Related

Frequently asked questions