chore: release v1.115.1

In Codex, prefer the bundled Chrome Computer Use path for all X UI
actions (compose, article, quote, video). CDP scripts become a fallback
when Computer Use is unavailable or explicitly not requested.

.claude-plugin/marketplace.json

@@ -6,7 +6,7 @@
   },
   "metadata": {
     "description": "Skills shared by Baoyu for improving daily work efficiency",
-    "version": "1.113.0"
+    "version": "1.115.1"
   },
   "plugins": [
     {

.claude/skills/release-skills/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: release-skills
-description: Universal release workflow. Auto-detects version files and changelogs. Supports Node.js, Python, Rust, Claude Plugin, and generic projects. Use when user says "release", "发布", "new version", "bump version", "push", "推送".
+description: Universal release workflow. Auto-detects version files and changelogs. Supports Node.js, Python, Rust, Claude Plugin, GitHub Releases, annotated tags, historical release backfill, and generic projects. Use when user says "release", "发布", "new version", "bump version", "push", "推送", "release notes", "GitHub Release", or "回填 Release".
 ---
 
 # Release Skills
@@ -39,6 +39,7 @@ Just run `/release-skills` - auto-detects your project configuration.
 | `--major` | Force major version bump |
 | `--minor` | Force minor version bump |
 | `--patch` | Force patch version bump |
+| `--backfill-releases` | Create missing GitHub Releases for existing tags from changelog sections |
 
 ## Workflow
 
@@ -57,7 +58,11 @@ Just run `/release-skills` - auto-detects your project configuration.
    - `HISTORY*.md`
    - `CHANGES*.md`
 4. Identify language of each changelog by filename suffix
-5. Display detected configuration
+5. Detect GitHub release support:
+   - Check whether `origin` points to GitHub
+   - Check whether `gh` is installed and authenticated
+   - Check existing releases with `gh release list --limit 5` when available
+6. Display detected configuration
 
 **Project Hook Contract**:
 
@@ -310,6 +315,14 @@ git commit -m "docs(project): update architecture documentation"
    - Read version file (JSON/TOML/text)
    - Update version number
    - Write back (preserve formatting)
+3. **Create release notes file**:
+   - Prefer the new version section from `CHANGELOG.md`
+   - If no English/default changelog exists, use the first detected changelog
+   - Extract only the exact `## {VERSION} - {YYYY-MM-DD}` section through the next `##`
+   - Match both plain version and tag-prefixed headings when needed, e.g. `1.2.3` and `v1.2.3`
+   - Keep breaking changes near the top; if needed, add a short highlight before other sections
+   - Write notes to a UTF-8 temp file and reuse it for annotated tag messages, GitHub Releases, and `publish_artifact`
+   - In normal mode, stop rather than creating an empty tag or GitHub Release when notes cannot be found
 
 **Version Paths by File Type**:
 
@@ -325,7 +338,7 @@ git commit -m "docs(project): update architecture documentation"
 
 Before creating the release commit, ask user to confirm:
 
-**Use AskUserQuestion with two questions**:
+**Use AskUserQuestion with three questions**:
 
 1. **Version bump** (single select):
    - Show recommended version based on Step 3 analysis
@@ -335,6 +348,11 @@ Before creating the release commit, ask user to confirm:
 2. **Push to remote** (single select):
    - Options: "Yes, push after commit", "No, keep local only"
 
+3. **Publish GitHub Release** (single select):
+   - Offer this only when GitHub release support is available
+   - Default to "Yes, publish after tag push" when the user also chose push
+   - If the user keeps the release local, do not create or edit a GitHub Release
+
 **Example Output Before Confirmation**:
 ```
 Commits created:
@@ -349,10 +367,11 @@ Changelog preview (en):
   ### Fixes
   - Improve panel layout for long dialogues in comic
 
-Ready to create release commit and tag.
+Release notes source: CHANGELOG.md#1.3.0
+Ready to create release commit, annotated tag, and GitHub Release.
 ```
 
-### Step 9: Create Release Commit and Tag
+### Step 9: Create Release Commit and Annotated Tag
 
 After user confirmation:
 
@@ -367,10 +386,11 @@ After user confirmation:
    git commit -m "chore: release v{VERSION}"
    ```
 
-3. **Create tag**:
+3. **Create annotated tag**:
    ```bash
-   git tag v{VERSION}
+   git tag -a v{VERSION} -F <release-notes-file>
    ```
+   If `.releaserc.yml` sets `tag.sign: true`, use `git tag -s` with the same notes file.
 
 4. **Push if user confirmed** (Step 8):
    ```bash
@@ -380,6 +400,28 @@ After user confirmation:
 
 **Note**: Do NOT add Co-Authored-By line. This is a release commit, not a code contribution.
 
+### Step 10: Publish Release Artifacts and GitHub Release
+
+Project artifact publishing and GitHub Releases are separate outputs:
+
+1. **Project artifacts**:
+   - If `release.hooks.publish_artifact` exists, run it once per prepared target
+   - Pass the same `{release_notes_file}` used for the tag and GitHub Release
+   - In dry-run mode, pass `{dry_run}=true` and report what would be published
+
+2. **GitHub Release**:
+   - Run only if the user confirmed remote publishing and GitHub support is available
+   - Ensure the tag exists on the remote before creating the release
+   - Create or update using the extracted notes:
+     ```bash
+     if gh release view v{VERSION} >/dev/null 2>&1; then
+       gh release edit v{VERSION} --title "v{VERSION}" --notes-file <release-notes-file>
+     else
+       gh release create v{VERSION} --title "v{VERSION}" --notes-file <release-notes-file> --verify-tag
+     fi
+     ```
+   - Never inline multiline release notes into shell commands
+
 **Post-Release Output**:
 ```
 Release v1.3.0 created.
@@ -391,9 +433,32 @@ Commits:
   4. chore: release v1.3.0
 
 Tag: v1.3.0
+Tag type: annotated
+GitHub Release: published  # or "skipped/local only"
 Status: Pushed to origin  # or "Local only - run git push when ready"
 ```
 
+## Backfill Existing GitHub Releases
+
+Use this mode when the user asks to backfill historical releases or passes `--backfill-releases`.
+
+1. Do not bump versions, edit changelogs, or create release commits.
+2. List existing tags in version order and detect missing releases:
+   ```bash
+   git tag --sort=v:refname
+   gh release view <tag>
+   ```
+3. For each tag without a GitHub Release:
+   - Normalize the changelog lookup by stripping the configured tag prefix, e.g. `v1.2.3` -> `1.2.3`
+   - Extract the matching section from `CHANGELOG.md`; fall back to the first matching changelog file
+   - Skip or ask before publishing if no matching changelog section exists
+   - Create the release with:
+     ```bash
+     gh release create <tag> --title "<tag>" --notes-file <release-notes-file> --verify-tag
+     ```
+4. Detect lightweight tags with `git cat-file -t <tag>` (`commit` means lightweight, `tag` means annotated).
+5. Do not rewrite public lightweight tags by default. Converting an existing remote tag to an annotated tag requires explicit user confirmation because it rewrites a published reference.
+
 ## Configuration (.releaserc.yml)
 
 Optional config file in project root to override defaults:
@@ -498,6 +563,7 @@ No changes made. Run without --dry-run to execute.
 /release-skills --minor      # Force minor bump
 /release-skills --patch      # Force patch bump
 /release-skills --major      # Force major bump (with confirmation)
+/release-skills --backfill-releases  # Create missing GitHub Releases for existing tags
 ```
 
 ## When to Use
@@ -506,6 +572,7 @@ Trigger this skill when user requests:
 - "release", "发布", "create release", "new version", "新版本"
 - "bump version", "update version", "更新版本"
 - "prepare release"
+- "release notes", "GitHub Release", "回填 Release"
 - "push to remote" (with uncommitted changes)
 
 **Important**: If user says "just push" or "直接 push" with uncommitted changes, STILL follow all steps above first.

CHANGELOG.md

@@ -2,6 +2,31 @@
 
 English | [中文](./CHANGELOG.zh.md)
 
+## 1.115.1 - 2026-05-10
+
+### Fixes
+- `baoyu-imagine`: change the default MiniMax image API endpoint to `https://api.minimaxi.com` to match the current official image generation documentation, while keeping `https://api.minimax.io` available through `MINIMAX_BASE_URL` overrides.
+- `baoyu-image-gen`: sync the deprecated image-generation entrypoint with the same MiniMax default endpoint and regression coverage.
+
+## 1.115.0 - 2026-05-09
+
+### Features
+- `baoyu-post-to-x`: add Chrome Computer Use as the preferred execution mode in Codex. When Computer Use tools are available, all X UI actions (compose, article, quote, video) go through the user's real Chrome window instead of CDP scripts. CDP scripts become a fallback when Computer Use is unavailable or explicitly not requested.
+
+## 1.114.1 - 2026-05-08
+
+### Fixes
+- `baoyu-danger-gemini-web`: restore generated-image extraction for current Gemini Web responses where image URLs appear as `https://lh3.googleusercontent.com/gg-dl/` without the legacy generated-image markers. Adds regression coverage for the fallback response shape. (by @evilstar2016)
+
+## 1.114.0 - 2026-05-05
+
+### Features
+- `baoyu-infographic`: add `retro-popup-pop` style — retro pixel popup × pop-art collage. Renders content as a stack of 80/90s desktop popup windows (title bars, close buttons, ERROR / ALERT dialogs, file windows like `PROBLEMS.EXE`, progress bars, OK / CANCEL / FIX IT buttons) with thick black outlines, flat color fills, and bright cyan (#12B8DE) or vintage cream (#F5F0E6) backgrounds. Pairs especially well with the `dense-modules` layout; promoted as a recommended style for the `高密度信息大图` keyword shortcut and the `Product/Buying Guide` content type. Style Gallery count goes from 21 to 22.
+  Credit to AJ@WaytoAGI.
+
+### Documentation
+- `release-skills`: document GitHub Release publishing in the release workflow, including release-notes extraction from changelog sections, annotated tag creation, `gh release create/edit`, and historical release backfill for existing tags.
+
 ## 1.113.0 - 2026-04-25
 
 ### Features
@@ -682,7 +707,7 @@ English | [中文](./CHANGELOG.zh.md)
 - `baoyu-format-markdown`: add reader-perspective content analysis phase — analyzes highlights, structure, and formatting issues before applying formatting
 - `baoyu-format-markdown`: restructure workflow from 8 steps to 7 with explicit do/don't formatting principles and completion report
 - `baoyu-translate`: extract Step 2 workflow mechanics to separate reference file for cleaner SKILL.md
-- `baoyu-translate`: expand trigger keywords (改成中文, 快翻, 本地化, etc.) for better skill activation
+- `baoyu-translate`: expand trigger keywords (改成中文，快翻，本地化，etc.) for better skill activation
 - `baoyu-translate`: add proactive warning for long content in quick mode
 - `baoyu-translate`: save frontmatter to `chunks/frontmatter.md` during chunking
 

CHANGELOG.zh.md

@@ -2,6 +2,31 @@
 
 [English](./CHANGELOG.md) | 中文
 
+## 1.115.1 - 2026-05-10
+
+### 修复
+- `baoyu-imagine`：将默认 MiniMax 图片 API 端点改为 `https://api.minimaxi.com`，与当前官方图片生成文档保持一致；仍可通过 `MINIMAX_BASE_URL` 覆盖为 `https://api.minimax.io`。
+- `baoyu-image-gen`：同步已废弃图片生成入口的 MiniMax 默认端点和回归测试。
+
+## 1.115.0 - 2026-05-09
+
+### 新功能
+- `baoyu-post-to-x`：新增 Chrome Computer Use 作为 Codex 环境下的首选执行模式。当 Computer Use 工具可用时，所有 X 界面操作（发帖、文章、引用、视频）均通过用户真实 Chrome 窗口完成，不再使用 CDP 脚本。CDP 脚本降级为 Computer Use 不可用或用户明确要求时的回退方案。
+
+## 1.114.1 - 2026-05-08
+
+### 修复
+- `baoyu-danger-gemini-web`：修复当前 Gemini Web 响应中生成图 URL 以 `https://lh3.googleusercontent.com/gg-dl/` 形式出现、但不再包含旧版生成图 marker 时的图片提取失败问题。补充该响应形态的回归测试。 (by @evilstar2016)
+
+## 1.114.0 - 2026-05-05
+
+### 新功能
+- `baoyu-infographic`：新增 `retro-popup-pop` 风格 —— 复古像素弹窗 × 波普信息图。画面由多个 80/90 年代桌面弹窗叠加而成（标题栏、关闭按钮、ERROR / ALERT 报错对话框、`PROBLEMS.EXE` 等复古文件窗、进度条、OK / CANCEL / FIX IT 按钮），统一粗黑描边、平涂色块，背景使用亮青蓝（#12B8DE）或复古奶油色（#F5F0E6）。与 `dense-modules` 布局尤其契合；同时升级为 `高密度信息大图` 关键词快捷方式与 `Product/Buying Guide` 内容类型的推荐风格。风格库从 21 个扩展至 22 个。
+  Credit to AJ@WaytoAGI.
+
+### 文档
+- `release-skills`：补充 GitHub Release 发布流程，包括从 changelog 段落提取 release notes、创建 annotated tag、执行 `gh release create/edit`，以及为已有 tag 回填历史 GitHub Releases。
+
 ## 1.113.0 - 2026-04-25
 
 ### 新功能
@@ -29,7 +54,7 @@
 
 ### 重构
 - 统一所有图片生成类技能（`baoyu-infographic`、`baoyu-comic`、`baoyu-cover-image`、`baoyu-image-cards`、`baoyu-article-illustrator`、`baoyu-slide-deck`、`baoyu-xhs-images`）的后端选择规则：新增单一 `preferred_image_backend` 偏好字段（`auto | ask | <backend-id>`），用 4 步解析规则（当前请求覆盖 → 已保存偏好 → 自动选择 → 询问用户）替换原有的无状态询问规则。默认优先使用运行时原生工具（如 Codex `imagegen`、Hermes `image_generate`）；未设置该字段的现有 `EXTEND.md` 文件视为 `auto`，无需升级 schema 版本。
-- 在每个图片技能中新增顶级 `## Changing Preferences` 章节,作为固定后端和修改常用偏好的一级入口。
+- 在每个图片技能中新增顶级 `## Changing Preferences` 章节，作为固定后端和修改常用偏好的一级入口。
 
 ## 1.110.0 - 2026-04-21
 
@@ -638,7 +663,7 @@
 ## 1.52.0 - 2026-03-06
 
 ### 新功能
-- `baoyu-post-to-weibo`：新增 `--video` 视频上传支持（图片+视频最多 18 个文件）
+- `baoyu-post-to-weibo`：新增 `--video` 视频上传支持（图片 + 视频最多 18 个文件）
 - `baoyu-post-to-weibo`：上传方式从剪贴板粘贴改为 `DOM.setFileInputFiles`，提升上传可靠性
 
 ### 修复
@@ -1101,7 +1126,7 @@
 ## 1.20.0 - 2026-01-24
 
 ### 新功能
-- `baoyu-cover-image`：从类型 × 风格二维系统升级为**四维系统**——新增 `--text` 维度（none 无文字、title-only 仅标题、title-subtitle 标题+副标题、text-rich 丰富文字）控制文字密度，新增 `--mood` 维度（subtle 低调、balanced 平衡、bold 醒目）控制情感强度。新增 `--quick` 标志跳过确认，直接使用自动选择。
+- `baoyu-cover-image`：从类型 × 风格二维系统升级为**四维系统**——新增 `--text` 维度（none 无文字、title-only 仅标题、title-subtitle 标题 + 副标题、text-rich 丰富文字）控制文字密度，新增 `--mood` 维度（subtle 低调、balanced 平衡、bold 醒目）控制情感强度。新增 `--quick` 标志跳过确认，直接使用自动选择。
 
 ### 文档
 - `baoyu-cover-image`：新增维度参考文件——`references/dimensions/text.md`（文字密度级别）和 `references/dimensions/mood.md`（氛围强度级别）。
@@ -1121,7 +1146,7 @@
 - `baoyu-image-gen`：代码模块化——类型定义提取至 `types.ts`，provider 实现提取至 `providers/google.ts` 和 `providers/openai.ts`。
 
 ### 文档
-- `baoyu-comic`：改进 ohmsha 预设文档，明确默认哆啦A梦角色定义和视觉描述。
+- `baoyu-comic`：改进 ohmsha 预设文档，明确默认哆啦 A 梦角色定义和视觉描述。
 
 ## 1.18.3 - 2026-01-23
 

README.md

@@ -834,7 +834,7 @@ AI SDK-based image generation using OpenAI GPT Image 2, Azure OpenAI, Google, Op
 | `DASHSCOPE_BASE_URL` | Custom DashScope endpoint | - |
 | `ZAI_BASE_URL` | Custom Z.AI endpoint | `https://api.z.ai/api/paas/v4` |
 | `BIGMODEL_BASE_URL` | Backward-compatible alias for Z.AI endpoint | - |
-| `MINIMAX_BASE_URL` | Custom MiniMax endpoint | `https://api.minimax.io` |
+| `MINIMAX_BASE_URL` | Custom MiniMax endpoint | `https://api.minimaxi.com` |
 | `REPLICATE_BASE_URL` | Custom Replicate endpoint | - |
 | `JIMENG_BASE_URL` | Custom Jimeng endpoint | `https://visual.volcengineapi.com` |
 | `JIMENG_REGION` | Jimeng region | `cn-north-1` |
@@ -1167,7 +1167,7 @@ ZAI_IMAGE_MODEL=glm-image
 # MiniMax
 MINIMAX_API_KEY=xxx
 MINIMAX_IMAGE_MODEL=image-01
-# MINIMAX_BASE_URL=https://api.minimax.io
+# MINIMAX_BASE_URL=https://api.minimaxi.com
 
 # Replicate
 REPLICATE_API_TOKEN=r8_xxx

README.zh.md

@@ -834,7 +834,7 @@ AI 驱动的生成后端。
 | `DASHSCOPE_BASE_URL` | 自定义 DashScope 端点 | - |
 | `ZAI_BASE_URL` | 自定义 Z.AI 端点 | `https://api.z.ai/api/paas/v4` |
 | `BIGMODEL_BASE_URL` | Z.AI 端点向后兼容别名 | - |
-| `MINIMAX_BASE_URL` | 自定义 MiniMax 端点 | `https://api.minimax.io` |
+| `MINIMAX_BASE_URL` | 自定义 MiniMax 端点 | `https://api.minimaxi.com` |
 | `REPLICATE_BASE_URL` | 自定义 Replicate 端点 | - |
 | `JIMENG_BASE_URL` | 自定义即梦端点 | `https://visual.volcengineapi.com` |
 | `JIMENG_REGION` | 即梦区域 | `cn-north-1` |
@@ -1167,7 +1167,7 @@ ZAI_IMAGE_MODEL=glm-image
 # MiniMax
 MINIMAX_API_KEY=xxx
 MINIMAX_IMAGE_MODEL=image-01
-# MINIMAX_BASE_URL=https://api.minimax.io
+# MINIMAX_BASE_URL=https://api.minimaxi.com
 
 # Replicate
 REPLICATE_API_TOKEN=r8_xxx

skills/baoyu-danger-gemini-web/scripts/gemini-webapi/client.test.ts

@@ -0,0 +1,25 @@
+import assert from "node:assert/strict";
+import test from "node:test";
+
+import { collect_generated_image_urls_from_response_parts } from "./client.ts";
+
+test("response part fallback finds generated images when legacy generated markers are absent", () => {
+  const generatedUrl = "https://lh3.googleusercontent.com/gg-dl/example-generated-image";
+  const initialCandidate = ["rcid-1", ["image generated successfully"]];
+  const imageCandidate = [
+    "rcid-1",
+    ["image generated successfully"],
+    { nestedPayload: [{ media: generatedUrl }] },
+  ];
+  const responseJson = [
+    ["wrb.fr", null, JSON.stringify([null, [], null, null, [initialCandidate]])],
+    ["wrb.fr", null, JSON.stringify([null, [], null, null, [imageCandidate]])],
+  ];
+
+  assert.equal(initialCandidate[12], undefined);
+  assert.equal(
+    /http:\/\/googleusercontent\.com\/image_generation_content\/\d+/.test(String(initialCandidate[1]?.[0])),
+    false,
+  );
+  assert.deepEqual(collect_generated_image_urls_from_response_parts(responseJson, 0, 0), [generatedUrl]);
+});

skills/baoyu-danger-gemini-web/scripts/gemini-webapi/client.ts

@@ -37,6 +37,8 @@ type InitOptions = {
 
 type RequestKwargs = RequestInit & { timeout_ms?: number };
 
+const GENERATED_IMAGE_URL_PREFIX = 'https://lh3.googleusercontent.com/gg-dl/';
+
 function normalize_headers(h?: HeadersInit): Record<string, string> {
   if (!h) return {};
   if (Array.isArray(h)) return Object.fromEntries(h.map(([k, v]) => [k, v]));
@@ -78,6 +80,59 @@ function collect_strings(root: unknown, accept: (s: string) => boolean, limit: n
   return out;
 }
 
+function collect_generated_image_urls(root: unknown, limit: number = 4): string[] {
+  return collect_strings(root, (s) => s.startsWith(GENERATED_IMAGE_URL_PREFIX), limit);
+}
+
+function parse_response_part_body(part: unknown): unknown[] | null {
+  if (!Array.isArray(part)) return null;
+  const part_body = get_nested_value<string | null>(part, [2], null);
+  if (!part_body) return null;
+  try {
+    const part_json = JSON.parse(part_body) as unknown;
+    return Array.isArray(part_json) ? part_json : null;
+  } catch {
+    return null;
+  }
+}
+
+function find_generated_image_part(
+  response_json: unknown[],
+  body_index: number,
+  candidate_index: number,
+  limit: number = 4,
+): { body: unknown[]; urls: string[] } | null {
+  for (let part_index = body_index; part_index < response_json.length; part_index++) {
+    const part_json = parse_response_part_body(response_json[part_index]);
+    if (!part_json) continue;
+    const cand = get_nested_value<unknown>(part_json, [4, candidate_index], null);
+    if (!cand) continue;
+    const urls = collect_generated_image_urls(cand, limit);
+    if (urls.length > 0) return { body: part_json, urls };
+  }
+  return null;
+}
+
+export function collect_generated_image_urls_from_response_parts(
+  response_json: unknown[],
+  body_index: number,
+  candidate_index: number,
+  limit: number = 4,
+): string[] {
+  return find_generated_image_part(response_json, body_index, candidate_index, limit)?.urls ?? [];
+}
+
+function push_generated_images(
+  generated_images: GeneratedImage[],
+  urls: string[],
+  proxy: string | null,
+  cookies: Record<string, string>,
+): void {
+  for (const url of urls) {
+    generated_images.push(new GeneratedImage(url, '[Generated Image]', '', proxy, cookies));
+  }
+}
+
 export class GeminiClient extends GemMixin {
   public cookies: Record<string, string> = {};
   public proxy: string | null = null;
@@ -404,24 +459,8 @@ export class GeminiClient extends GemMixin {
             /http:\/\/googleusercontent\.com\/image_generation_content\/\d+/.test(text);
 
           if (wants_generated) {
-            let img_body: unknown[] | null = null;
-            for (let part_index = body_index; part_index < (response_json as unknown[]).length; part_index++) {
-              const part = (response_json as unknown[])[part_index];
-              if (!Array.isArray(part)) continue;
-              const part_body = get_nested_value<string | null>(part, [2], null);
-              if (!part_body) continue;
-              try {
-                const part_json = JSON.parse(part_body) as unknown[];
-                const cand = get_nested_value<unknown>(part_json, [4, candidate_index], null);
-                if (!cand) continue;
-
-                const urls = collect_strings(cand, (s) => s.startsWith('https://lh3.googleusercontent.com/gg-dl/'), 1);
-                if (urls.length > 0) {
-                  img_body = part_json;
-                  break;
-                }
-              } catch {}
-            }
+            const image_part = find_generated_image_part(response_json as unknown[], body_index, candidate_index, 1);
+            const img_body = image_part?.body ?? null;
 
             if (!img_body) {
               throw new ImageGenerationError(
@@ -452,13 +491,22 @@ export class GeminiClient extends GemMixin {
             }
 
             if (generated_images.length === 0) {
-              const urls = collect_strings(img_candidate, (s) => s.startsWith('https://lh3.googleusercontent.com/gg-dl/'), 4);
-              for (const url of urls) {
-                generated_images.push(new GeneratedImage(url, '[Generated Image]', '', this.proxy, this.cookies));
-              }
+              push_generated_images(generated_images, collect_generated_image_urls(img_candidate), this.proxy, this.cookies);
             }
           }
 
+          // Fallback: unconditionally scan all response parts for generated image URLs.
+          // The `wants_generated` detection above relies on `candidate[12][7][0]` and an old
+          // `googleusercontent.com/image_generation_content/` URL pattern, both of which no
+          // longer appear in the current Gemini Web API response format.
+          // When Gemini does generate images, their URLs now start with
+          // `https://lh3.googleusercontent.com/gg-dl/` and are present somewhere in the
+          // response parts — this fallback finds them so images are not silently dropped.
+          if (generated_images.length === 0) {
+            const urls = collect_generated_image_urls_from_response_parts(response_json as unknown[], body_index, candidate_index);
+            push_generated_images(generated_images, urls, this.proxy, this.cookies);
+          }
+
           out.push(new Candidate({ rcid, text, thoughts, web_images, generated_images }));
         }
 

skills/baoyu-image-gen/references/providers/minimax.md

@@ -24,6 +24,6 @@ Read when the user picks `--provider minimax` or sets `default_model.minimax`. D
 
 ## Official References
 
-- [Image Generation Guide](https://platform.minimax.io/docs/guides/image-generation)
-- [Text-to-Image API](https://platform.minimax.io/docs/api-reference/image-generation-t2i)
-- [Image-to-Image API](https://platform.minimax.io/docs/api-reference/image-generation-i2i)
+- [Image Generation Guide](https://platform.minimaxi.com/docs/guides/image-generation)
+- [Text-to-Image API](https://platform.minimaxi.com/docs/api-reference/image-generation-t2i)
+- [Image-to-Image API](https://platform.minimaxi.com/docs/api-reference/image-generation-i2i)

skills/baoyu-image-gen/scripts/providers/minimax.test.ts

@@ -60,8 +60,11 @@ function makeArgs(overrides: Partial<CliArgs> = {}): CliArgs {
   };
 }
 
-test("MiniMax URL builder normalizes /v1 suffixes", (t) => {
-  useEnv(t, { MINIMAX_BASE_URL: "https://api.minimax.io" });
+test("MiniMax URL builder uses documented default and normalizes /v1 suffixes", (t) => {
+  useEnv(t, { MINIMAX_BASE_URL: null });
+  assert.equal(buildMinimaxUrl(), "https://api.minimaxi.com/v1/image_generation");
+
+  process.env.MINIMAX_BASE_URL = "https://api.minimax.io";
   assert.equal(buildMinimaxUrl(), "https://api.minimax.io/v1/image_generation");
 
   process.env.MINIMAX_BASE_URL = "https://proxy.example.com/custom/v1/";

skills/baoyu-image-gen/scripts/providers/minimax.ts

@@ -44,7 +44,7 @@ function getApiKey(): string | null {
 }
 
 export function buildMinimaxUrl(): string {
-  const base = (process.env.MINIMAX_BASE_URL || "https://api.minimax.io").replace(/\/+$/g, "");
+  const base = (process.env.MINIMAX_BASE_URL || "https://api.minimaxi.com").replace(/\/+$/g, "");
   return base.endsWith("/v1") ? `${base}/image_generation` : `${base}/v1/image_generation`;
 }
 
@@ -197,7 +197,7 @@ export async function generateImage(
 ): Promise<Uint8Array> {
   const apiKey = getApiKey();
   if (!apiKey) {
-    throw new Error("MINIMAX_API_KEY is required. Get one from https://platform.minimax.io/");
+    throw new Error("MINIMAX_API_KEY is required. Get one from https://platform.minimaxi.com/");
   }
 
   const body = await buildRequestBody(prompt, model, args);

skills/baoyu-imagine/references/providers/minimax.md

@@ -24,6 +24,6 @@ Read when the user picks `--provider minimax` or sets `default_model.minimax`. D
 
 ## Official References
 
-- [Image Generation Guide](https://platform.minimax.io/docs/guides/image-generation)
-- [Text-to-Image API](https://platform.minimax.io/docs/api-reference/image-generation-t2i)
-- [Image-to-Image API](https://platform.minimax.io/docs/api-reference/image-generation-i2i)
+- [Image Generation Guide](https://platform.minimaxi.com/docs/guides/image-generation)
+- [Text-to-Image API](https://platform.minimaxi.com/docs/api-reference/image-generation-t2i)
+- [Image-to-Image API](https://platform.minimaxi.com/docs/api-reference/image-generation-i2i)

skills/baoyu-imagine/scripts/providers/minimax.test.ts

@@ -61,8 +61,11 @@ function makeArgs(overrides: Partial<CliArgs> = {}): CliArgs {
   };
 }
 
-test("MiniMax URL builder normalizes /v1 suffixes", (t) => {
-  useEnv(t, { MINIMAX_BASE_URL: "https://api.minimax.io" });
+test("MiniMax URL builder uses documented default and normalizes /v1 suffixes", (t) => {
+  useEnv(t, { MINIMAX_BASE_URL: null });
+  assert.equal(buildMinimaxUrl(), "https://api.minimaxi.com/v1/image_generation");
+
+  process.env.MINIMAX_BASE_URL = "https://api.minimax.io";
   assert.equal(buildMinimaxUrl(), "https://api.minimax.io/v1/image_generation");
 
   process.env.MINIMAX_BASE_URL = "https://proxy.example.com/custom/v1/";

skills/baoyu-imagine/scripts/providers/minimax.ts

@@ -44,7 +44,7 @@ function getApiKey(): string | null {
 }
 
 export function buildMinimaxUrl(): string {
-  const base = (process.env.MINIMAX_BASE_URL || "https://api.minimax.io").replace(/\/+$/g, "");
+  const base = (process.env.MINIMAX_BASE_URL || "https://api.minimaxi.com").replace(/\/+$/g, "");
   return base.endsWith("/v1") ? `${base}/image_generation` : `${base}/v1/image_generation`;
 }
 
@@ -197,7 +197,7 @@ export async function generateImage(
 ): Promise<Uint8Array> {
   const apiKey = getApiKey();
   if (!apiKey) {
-    throw new Error("MINIMAX_API_KEY is required. Get one from https://platform.minimax.io/");
+    throw new Error("MINIMAX_API_KEY is required. Get one from https://platform.minimaxi.com/");
   }
 
   const body = await buildRequestBody(prompt, model, args);

skills/baoyu-infographic/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: baoyu-infographic
-description: Generate professional infographics with 21 layout types and 21 visual styles. Analyzes content, recommends layout×style combinations, and generates publication-ready infographics. Use when user asks to create "infographic", "信息图", "visual summary", "可视化", or "高密度信息大图".
-version: 1.57.1
+description: Generate professional infographics with 21 layout types and 22 visual styles. Analyzes content, recommends layout×style combinations, and generates publication-ready infographics. Use when user asks to create "infographic", "信息图", "visual summary", "可视化", or "高密度信息大图".
+version: 1.58.0
 metadata:
   openclaw:
     homepage: https://github.com/JimLiu/baoyu-skills#baoyu-infographic
@@ -84,7 +84,7 @@ Default behavior: **confirm before generation**.
 | Option | Values |
 |--------|--------|
 | `--layout` | 21 options (see Layout Gallery), default: bento-grid |
-| `--style` | 21 options (see Style Gallery), default: craft-handmade |
+| `--style` | 22 options (see Style Gallery), default: craft-handmade |
 | `--aspect` | Named: landscape (16:9), portrait (9:16), square (1:1). Custom: any W:H ratio (e.g., 3:4, 4:3, 2.35:1) |
 | `--lang` | en, zh, ja, etc. |
 | `--no-confirm` | Skip Step 4 only when the user explicitly requests direct generation without confirmation |
@@ -118,7 +118,7 @@ Default behavior: **confirm before generation**.
 
 Full definitions live at `references/layouts/<layout>.md`.
 
-## Style Gallery (21)
+## Style Gallery (22)
 
 | Style | Description |
 |-------|-------------|
@@ -143,6 +143,7 @@ Full definitions live at `references/layouts/<layout>.md`.
 | `morandi-journal` | Hand-drawn doodle, warm Morandi tones |
 | `retro-pop-grid` | 1970s retro pop art, Swiss grid, thick outlines |
 | `hand-drawn-edu` | Macaron pastels, hand-drawn wobble, stick figures |
+| `retro-popup-pop` | Retro popup collage, vintage UI, thick outlines, flat pop colors |
 
 Full definitions live at `references/styles/<style>.md`.
 
@@ -165,6 +166,7 @@ Full definitions live at `references/styles/<style>.md`.
 | Product Guide | `dense-modules` + `morandi-journal` |
 | Technical Guide | `dense-modules` + `pop-laboratory` |
 | Trendy Guide | `dense-modules` + `retro-pop-grid` |
+| Retro Pop Guide | `dense-modules` + `retro-popup-pop` |
 | Educational Diagram | `hub-spoke` + `hand-drawn-edu` |
 | Process Tutorial | `linear-progression` + `hand-drawn-edu` |
 
@@ -176,7 +178,7 @@ When the user's input contains these keywords, use the mapped layout as the lead
 
 | User Keyword | Layout | Recommended Styles | Default Aspect | Prompt Notes |
 |--------------|--------|--------------------|----------------|--------------|
-| 高密度信息大图 / high-density-info | `dense-modules` | `morandi-journal`, `pop-laboratory`, `retro-pop-grid` | portrait | — |
+| 高密度信息大图 / high-density-info | `dense-modules` | `morandi-journal`, `pop-laboratory`, `retro-pop-grid`, `retro-popup-pop` | portrait | — |
 | 信息图 / infographic | `bento-grid` | `craft-handmade` | landscape | Minimalist: clean canvas, ample whitespace, no complex background textures. Simple cartoon elements and icons only. |
 
 ## Output Structure

skills/baoyu-infographic/references/analysis-framework.md

@@ -39,7 +39,7 @@ Approach content analysis as a **world-class instructional designer**:
 | **System/Structure** | Components, architecture, anatomy | structural-breakdown, bento-grid | technical-schematic, ikea-manual |
 | **Journey/Narrative** | Stories, user flows, milestones | winding-roadmap, story-mountain | storybook-watercolor, comic-strip |
 | **Overview/Summary** | Multiple topics, feature highlights | bento-grid, periodic-table, dense-modules | chalkboard, bold-graphic |
-| **Product/Buying Guide** | Multi-dimension comparisons, specs, pitfalls | dense-modules | morandi-journal, pop-laboratory, retro-pop-grid |
+| **Product/Buying Guide** | Multi-dimension comparisons, specs, pitfalls | dense-modules | morandi-journal, pop-laboratory, retro-pop-grid, retro-popup-pop |
 
 ### 2. Learning Objective Identification
 

skills/baoyu-infographic/references/layouts/dense-modules.md

@@ -68,5 +68,6 @@ High-density modular layout with 6-7 typed information modules packed with concr
 - `pop-laboratory`: Technical precision with coordinate markers and blueprint grid
 - `morandi-journal`: Hand-drawn warmth with doodle illustrations and organic frames
 - `retro-pop-grid`: 1970s pop art with strict grid cells and bold contrast
+- `retro-popup-pop`: Vintage desktop popups with chunky pixel UI for retro-tech dense guides
 - `corporate-memphis`: Clean business feel for product comparisons
 - `technical-schematic`: Engineering precision for technical product guides

skills/baoyu-infographic/references/styles/retro-popup-pop.md

@@ -0,0 +1,50 @@
+# retro-popup-pop
+
+Retro pixel popup × pop-art collage — content rendered as a stack of 80/90s desktop dialog windows with thick black outlines, flat color fills, and bright cyan or vintage cream backgrounds.
+
+## Color Palette
+
+- Background: Bright cyan (#12B8DE) primary canvas, vintage cream (#F5F0E6) alternate
+- Window fills: Vintage cream (#F5F0E6) and pure white (#FFFFFF)
+- Primary text and outlines: Pure black (#000000)
+- Reverse text: Pure white on solid black title bars
+- Accent fills (small areas only): Salmon pink, sky blue, mustard yellow, mint green — muted retro tones
+
+## Visual Elements
+
+- 80s/90s desktop popup windows with title bars, close buttons (×), and chunky borders
+- Multiple windows tiled or lightly overlapping with offset solid-black drop shadows for depth
+- ERROR / ALERT / WARNING dialogs to highlight misconceptions, common pitfalls, risks
+- File-window vignettes labeled with retro filenames (PROBLEMS.EXE, METHOD.PNG, BURNOUT.PSD, FOCUS_SCAN, SYSTEM_ALERT, IDEAS_MISSING)
+- Progress bars for completion, difficulty, conversion rate, or trend
+- Pixel-style chunky icons: folders, magnifiers, gears, exclamation marks, floppy disks, hourglasses
+- Action buttons with thick black borders and short pop-style copy: OK, CANCEL, FIX IT, SCAN, PLAY, RETRY, SAVE
+- Comparison data rendered as windowed lists or small tabular dialogs
+- Uniform thick black outlines on every window, button, icon, and divider
+- Pure 2D flat color fills throughout — no gradients, no glow, no glass
+
+## Typography
+
+- Headers: Pixel / dot-matrix / chunky bitmap display fonts, large and high-contrast
+- Body: Retro monospace or system-style sans-serif, high legibility
+- Title bars: Reverse white on solid black, all-caps preferred
+- Decorative all-caps English allowed for filenames, status strings, button labels (PROBLEMS.EXE, OK, CANCEL); body content text remains in the confirmed output language
+
+## Style Enforcement
+
+- Every information chunk must live inside a window, dialog, button, or progress bar — no floating elements
+- Uniform thick black outlines everywhere; offset solid-black drop shadows for stacked-window depth
+- Limit accent palette to ~4 colors per composition; let cyan or cream dominate the canvas
+- Maintain low-fi pixel/popup feel; humorous popup copy welcome, polished modern UI prohibited
+
+## Avoid
+
+- Modern UI styles: glassmorphism, neumorphism, soft shadows, blurs, gradients
+- 3D rendering, photorealism, ray-traced shadows
+- Hand-drawn wobble, watercolor washes, or sketch textures
+- Smooth anti-aliased curves on icons (prefer chunky pixel/stair-step edges)
+- Pure black backgrounds — keep cyan or cream as the canvas
+
+## Best For
+
+High-density "干货" knowledge guides, common-pitfall and debunking posts, knowledge-pop content for design-savvy or developer audiences, Xiaohongshu-style retro-tech posts, dense-modules portrait infographics.

skills/baoyu-post-to-x/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: baoyu-post-to-x
-description: Posts content and articles to X (Twitter). Supports regular posts with images/videos and X Articles (long-form Markdown). Uses real Chrome with CDP to bypass anti-automation. Use when user asks to "post to X", "tweet", "publish to Twitter", or "share on X".
-version: 1.56.2
+description: Posts content and articles to X (Twitter). Supports regular posts with images/videos and X Articles (long-form Markdown). In Codex, prefers the bundled Chrome Computer Use when available and falls back to real Chrome CDP scripts otherwise. Use when user asks to "post to X", "tweet", "publish to Twitter", or "share on X".
+version: 1.57.0
 metadata:
   openclaw:
     homepage: https://github.com/JimLiu/baoyu-skills#baoyu-post-to-x
@@ -15,6 +15,8 @@ metadata:
 
 Posts text, images, videos, and long-form articles to X via real Chrome browser (bypasses anti-bot detection).
 
+In Codex, first try the bundled **Chrome Computer Use** path. Use the CDP scripts only when Chrome Computer Use is not available or the user explicitly asks for the script/CDP workflow.
+
 ## Script Directory
 
 **Important**: All scripts are located in the `scripts/` subdirectory of this skill.
@@ -28,15 +30,27 @@ Posts text, images, videos, and long-form articles to X via real Chrome browser
 **Script Reference**:
 | Script | Purpose |
 |--------|---------|
-| `scripts/x-browser.ts` | Regular posts (text + images) |
-| `scripts/x-video.ts` | Video posts (text + video) |
-| `scripts/x-quote.ts` | Quote tweet with comment |
-| `scripts/x-article.ts` | Long-form article publishing (Markdown) |
+| `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)
+
+Before choosing a workflow, detect whether Codex Chrome Computer Use is enabled:
+
+1. If Computer Use tools are already visible, call `get_app_state` for app `Google Chrome`. In Codex these may be surfaced as `mcp__computer_use__.*`; use the exact available tool names.
+2. If they are not visible and `tool_search` is available, search for `computer-use get_app_state click press_key drag scroll Google Chrome`, then call `get_app_state` for app `Google Chrome`.
+3. If `get_app_state` succeeds, use **Chrome Computer Use Mode** below.
+4. If Computer Use tools are unavailable or `get_app_state` fails, use **CDP Script Mode**.
+5. If the user explicitly says to use Chrome Computer Use, do not fall back to CDP, Playwright, or the in-app Browser without telling the user and getting approval.
+
+When Chrome Computer Use Mode is active, all X UI actions must go through the Codex Computer Use tools against the user's real Google Chrome. Shell commands are still allowed for preprocessing Markdown and copying local files to the system clipboard.
+
 ## Preferences (EXTEND.md)
 
 Check EXTEND.md in priority order — the first one found wins:
@@ -86,6 +100,73 @@ Checks: Chrome, profile isolation, Bun, Accessibility, clipboard, paste keystrok
 
 ---
 
+## Chrome Computer Use Mode (Codex Preferred)
+
+Use this mode whenever 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, Playwright, or CDP for X UI actions in this mode.
+- 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:
+   - Copy the image with `copy-to-clipboard.ts image <localPath>`.
+   - Select the exact visible placeholder text such as `XIMGPH_3`.
+   - Paste with Computer Use (`super+v`/`control+v`).
+   - Wait until the X header no longer says `Uploading media...`.
+   - If the placeholder remains, reselect the exact placeholder text and press `BackSpace`. Never press `BackSpace` unless the app state confirms the selected text is exactly that 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 or paste becomes unreliable, stop and report the blocker instead of switching to CDP silently.
+
+---
+
+## CDP Script Mode (Fallback)
+
+Use the script sections below only when Chrome Computer Use 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 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:
@@ -107,6 +188,8 @@ ${BUN_X} {baseDir}/scripts/x-browser.ts "Hello!" --image ./photo.png
 
 **Note**: Script opens browser with content filled in. User reviews and publishes manually.
 
+**Chrome Computer Use preferred**: In Codex, if Chrome Computer Use is enabled, use the visible Chrome UI workflow in **Chrome Computer Use Mode** instead of running `x-browser.ts`.
+
 ---
 
 ## Video Posts
@@ -126,6 +209,8 @@ ${BUN_X} {baseDir}/scripts/x-video.ts "Check this out!" --video ./clip.mp4
 
 **Note**: Script opens browser with content filled in. User reviews and publishes manually.
 
+**Chrome Computer Use preferred**: In Codex, if Chrome Computer Use is enabled, use the visible Chrome UI workflow in **Chrome Computer Use Mode** instead of running `x-video.ts`.
+
 **Limits**: Regular 140s max, Premium 60min. Processing: 30-60s.
 
 ---
@@ -147,6 +232,8 @@ ${BUN_X} {baseDir}/scripts/x-quote.ts https://x.com/user/status/123 "Great insig
 
 **Note**: Script opens browser with content filled in. User reviews and publishes manually.
 
+**Chrome Computer Use preferred**: In Codex, if Chrome Computer Use is enabled, use the visible Chrome UI workflow in **Chrome Computer Use Mode** instead of running `x-quote.ts`.
+
 ---
 
 ## X Articles
@@ -167,7 +254,11 @@ ${BUN_X} {baseDir}/scripts/x-article.ts article.md --cover ./cover.jpg
 
 **Frontmatter**: `title`, `cover_image` supported in YAML front matter.
 
-**Note**: Script opens browser with article filled in. User reviews and publishes manually.
+**Chrome Computer Use preferred**: In Codex, if Chrome Computer Use is enabled, follow **Chrome Computer Use Mode** above instead of running `x-article.ts`.
+
+**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
@@ -181,7 +272,7 @@ If the check fails (warnings in output), alert the user with the specific issues
 
 ### Chrome debug port not ready
 
-If a script fails with `Chrome debug port not ready` or `Unable to connect`, kill existing Chrome CDP instances first, then retry:
+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
@@ -192,7 +283,8 @@ pkill -f "Chrome.*remote-debugging-port" 2>/dev/null; pkill -f "Chromium.*remote
 ## Notes
 
 - First run: manual login required (session persists)
-- All scripts only fill content into the browser, user must review and publish manually
+- In 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

skills/baoyu-post-to-x/references/articles.md

@@ -2,6 +2,17 @@
 
 Publish Markdown articles to X Articles editor with rich text formatting and images.
 
+## Mode Selection
+
+In Codex, prefer **Chrome Computer Use** when available:
+
+1. If Computer Use tools are already visible, call `get_app_state` for `Google Chrome`.
+2. If not, use `tool_search` for `computer-use get_app_state click press_key drag scroll Google Chrome`, then call `get_app_state`.
+3. If that succeeds, use the Computer Use workflow below.
+4. Use the CDP script workflow only when Computer Use is unavailable or explicitly requested.
+
+If the user explicitly asks for Chrome Computer Use, do not fall back to CDP, Playwright, or the in-app Browser without approval.
+
 ## Prerequisites
 
 - X Premium subscription (required for Articles)
@@ -10,6 +21,24 @@ Publish Markdown articles to X Articles editor with rich text formatting and ima
 
 ## Usage
 
+### Chrome Computer Use (Codex Preferred)
+
+Prepare the article HTML and image map:
+
+```bash
+${BUN_X} {baseDir}/scripts/md-to-html.ts article.md --save-html /tmp/x-article-body.html > /tmp/x-article.json
+```
+
+Copy the generated HTML as rich text:
+
+```bash
+${BUN_X} {baseDir}/scripts/copy-to-clipboard.ts html --file /tmp/x-article-body.html
+```
+
+Then use Codex Computer Use against `Google Chrome` for all X UI operations.
+
+### CDP Script Fallback
+
 ```bash
 # Publish markdown article (preview mode)
 ${BUN_X} {baseDir}/scripts/x-article.ts article.md
@@ -21,6 +50,8 @@ ${BUN_X} {baseDir}/scripts/x-article.ts article.md --cover ./cover.jpg
 ${BUN_X} {baseDir}/scripts/x-article.ts article.md --submit
 ```
 
+Do not use `--submit` unless the user has explicitly confirmed the final public publish action.
+
 ## Markdown Format
 
 ```markdown
@@ -118,7 +149,33 @@ JSON output:
 | `1. item` | `<ol><li>` |
 | `![](img)` | Image placeholder |
 
-## Workflow
+## Computer Use Workflow (Preferred in Codex)
+
+1. **Detect Computer Use**: call `get_app_state` for `Google Chrome`; use `tool_search` first if the tools are not visible.
+2. **Parse Markdown**: run `md-to-html.ts --save-html /tmp/x-article-body.html > /tmp/x-article.json`.
+3. **Read the map**: use `/tmp/x-article.json` for `title`, `coverImage`, and `contentImages`.
+4. **Open X Articles**: use Chrome Computer Use to navigate to `https://x.com/compose/articles`.
+5. **Create Draft**: click the create/write button if needed, or open the target draft.
+6. **Upload Cover**: if `coverImage` exists, use Chrome's visible upload/file picker UI. If the file picker cannot be operated reliably, stop and ask for help rather than switching to CDP silently.
+7. **Fill Title**: type the title into the title field.
+8. **Paste Content**:
+   - Run `copy-to-clipboard.ts html --file /tmp/x-article-body.html`.
+   - Click the article body.
+   - Press `super+v` on macOS or `control+v` on Windows/Linux with Computer Use.
+9. **Insert Images**: for each `contentImages` item in placeholder order:
+   - Run `copy-to-clipboard.ts image <localPath>`.
+   - Select the exact placeholder text (`XIMGPH_N`) in the editor.
+   - Press `super+v`/`control+v` with Computer Use.
+   - Wait for X to finish uploading media.
+   - If `XIMGPH_N` remains above the inserted image, reselect that exact text and press `BackSpace`.
+   - Do not press `BackSpace` unless the Computer Use state confirms the selected text is exactly the placeholder.
+10. **Verify**:
+   - Inspect the Computer Use state for `XIMGPH_` residue.
+   - Confirm the expected number of image blocks is visible.
+   - Open Preview and verify title, cover, body, links, and images.
+11. **Publish Safety**: ask the user for explicit final confirmation before clicking `Publish`.
+
+## CDP Script Workflow (Fallback)
 
 1. **Parse Markdown**: Extract title, cover, content images, generate HTML
 2. **Launch Chrome**: Real browser with CDP, persistent login
@@ -137,7 +194,7 @@ JSON output:
    - Compare expected vs actual image count
    - Warn if issues found
 10. **Review**: Browser stays open for 60s preview
-11. **Publish**: Only with `--submit` flag
+11. **Publish**: Only with `--submit` flag and explicit user confirmation
 
 ## Example Session
 
@@ -145,15 +202,15 @@ JSON output:
 User: /post-to-x article ./blog/my-post.md --cover ./thumbnail.png
 
 Claude:
-1. Parses markdown: title="My Post", 3 content images
-2. Launches Chrome with CDP
-3. Navigates to x.com/compose/articles
-4. Clicks create button
+1. Detects Chrome Computer Use
+2. Parses markdown: title="My Post", 3 content images
+3. Saves `/tmp/x-article-body.html` and `/tmp/x-article.json`
+4. Uses Chrome Computer Use to open X Articles and create a draft
 5. Uploads thumbnail.png as cover
 6. Fills title "My Post"
-7. Pastes HTML content
+7. Pastes HTML content with a real Chrome paste
 8. Inserts 3 images at placeholder positions
-9. Reports: "Article composed. Review and use --submit to publish."
+9. Opens Preview and asks before publishing
 ```
 
 ## Troubleshooting
@@ -162,6 +219,8 @@ Claude:
 - **Cover upload fails**: Check file path and format (PNG, JPEG)
 - **Images not inserting**: Verify placeholders exist in pasted content
 - **Content not pasting**: Check HTML clipboard: `${BUN_X} {baseDir}/scripts/copy-to-clipboard.ts html --file /tmp/test.html`
+- **Computer Use unavailable**: Use the CDP fallback script, unless the user explicitly required Chrome Computer Use.
+- **Placeholder remains after paste**: Select only the placeholder text and press BackSpace after upload completes.
 
 ## How It Works
 
@@ -172,7 +231,13 @@ Claude:
    - Downloads remote images locally
    - Returns structured JSON
 
-2. `x-article.ts` publishes via CDP:
+2. Chrome Computer Use publishes through the user's visible Chrome UI:
+   - Uses the user's active Chrome profile and logged-in X session
+   - Uses `copy-to-clipboard.ts` for rich HTML and image clipboard payloads
+   - Uses real keystrokes (`super+v`/`control+v`) through Codex Computer Use
+   - Keeps the final publish click under user confirmation
+
+3. `x-article.ts` publishes via CDP as a fallback:
    - Launches real Chrome (bypasses detection)
    - Uses persistent profile (saved login)
    - Navigates and fills editor via DOM manipulation

skills/baoyu-post-to-x/references/regular-posts.md

@@ -6,6 +6,17 @@ Detailed documentation for posting text and images to X.
 
 If you prefer step-by-step control:
 
+### Step 0: Prefer Chrome Computer Use in Codex
+
+When running inside Codex, first detect whether Chrome Computer Use is enabled:
+
+1. If Computer Use tools are already visible, call `get_app_state` for `Google Chrome`.
+2. If not, use `tool_search` for `computer-use get_app_state click press_key drag scroll Google Chrome`, then call `get_app_state`.
+3. If `get_app_state` succeeds, use the user's real Chrome with Computer Use for all X UI actions.
+4. Use CDP scripts only when Computer Use is unavailable or explicitly requested.
+
+If the user explicitly asks for Chrome Computer Use, do not use Playwright, the in-app Browser, or CDP without approval.
+
 ### Step 1: Copy Image to Clipboard
 
 ```bash
@@ -25,27 +36,15 @@ ${BUN_X} {baseDir}/scripts/paste-from-clipboard.ts --app "Google Chrome" --retri
 ${BUN_X} {baseDir}/scripts/paste-from-clipboard.ts --delay 200
 ```
 
-### Step 3: Use Playwright MCP (if Chrome session available)
+### Step 3: Use Chrome Computer Use (Preferred)
 
-```bash
-# Navigate
-mcp__playwright__browser_navigate url="https://x.com/compose/post"
-
-# Get element refs
-mcp__playwright__browser_snapshot
-
-# Type text
-mcp__playwright__browser_click element="editor" ref="<ref>"
-mcp__playwright__browser_type element="editor" ref="<ref>" text="Your content"
-
-# Paste image (after copying to clipboard)
-mcp__playwright__browser_press_key key="Meta+v"  # macOS
-# or
-mcp__playwright__browser_press_key key="Control+v"  # Windows/Linux
-
-# Screenshot to verify
-mcp__playwright__browser_take_screenshot filename="preview.png"
-```
+1. Use `get_app_state` for `Google Chrome`.
+2. Navigate Chrome to `https://x.com/compose/post` if needed.
+3. Click the composer and type the post text.
+4. Copy each image to the clipboard with `copy-to-clipboard.ts image <path>`.
+5. Press `super+v` on macOS or `control+v` on Windows/Linux with Computer Use.
+6. Wait until X finishes media upload.
+7. Ask for explicit confirmation before clicking `Post`.
 
 ## Image Support
 
@@ -59,12 +58,12 @@ mcp__playwright__browser_take_screenshot filename="preview.png"
 User: /post-to-x "Hello from Claude!" --image ./screenshot.png
 
 Claude:
-1. Runs: ${BUN_X} {baseDir}/scripts/x-browser.ts "Hello from Claude!" --image ./screenshot.png
-2. Chrome opens with X compose page
-3. Text is typed into editor
-4. Image is copied to clipboard and pasted
-5. Browser stays open 30s for preview
-6. Reports: "Post composed. Use --submit to post."
+1. Detects Chrome Computer Use
+2. Opens X compose in the user's real Chrome
+3. Types text into editor
+4. Copies image to clipboard and pastes with Computer Use
+5. Waits for upload and verifies the preview
+6. Asks before clicking Post
 ```
 
 ## Troubleshooting
@@ -80,7 +79,13 @@ Claude:
 
 ## How It Works
 
-The `x-browser.ts` script uses Chrome DevTools Protocol (CDP) to:
+In Chrome Computer Use mode:
+1. Codex controls the user's visible Google Chrome window
+2. Text is typed through the real UI
+3. Images are copied to the system clipboard and pasted with real keystrokes
+4. The user confirms before the final public post
+
+The `x-browser.ts` script is the CDP fallback. It uses Chrome DevTools Protocol (CDP) to:
 1. Launch real Chrome (not Playwright) with `--disable-blink-features=AutomationControlled`
 2. Use persistent profile directory for saved login sessions
 3. Interact with X via CDP commands (Runtime.evaluate, Input.dispatchKeyEvent)