dan-publish-all

name	dan-publish-all
description	One-click publish markdown articles with auto-generated illustrations and covers to blog (dhpie.com), WeChat, X Article, and Xiaohongshu cards. Triggers on "发布各个平台", "publish all", "全平台发布", "发布到所有平台", "publish everywhere".

dan-publish-all

一键发布 markdown 文章到所有平台：自动配图、生成封面、上传 CDN、发布博客、微信公众号、X Article 和小红书图片卡。

Language

Match user's language.

Workflow Overview

输入文章 → 检查配图 → 检查封面 → 上传 R2 → 并行发布博客 + 公众号 + X Article + 小红书卡片

Step 1: Select Articles

List all .md files in current directory, sorted by modification time (newest first). Present as numbered list for user to select (single or multiple).

If user already specified files, skip this step.

Step 2: Analyze Each Article

For each selected article, read the file and determine:

Check	How
Has illustrations?	Scan for ![ references pointing to illustrations/ directory
Has cover?	Scan for ![ references pointing to cover-image/ directory, or check if cover-image/{slug}/cover.jpg exists
Language	Detect from content: Chinese → zh, English → en
Is paired?	Check if a corresponding zh/en version exists in the same directory

Report findings to user:

文章分析结果：
1. ✓/✗ 配图 | ✓/✗ 封面 | zh | [title]
2. ✓/✗ 配图 | ✓/✗ 封面 | en | [title]
...

Step 3: Generate Missing Assets (Parallel)

CRITICAL: Use sub-agents (Agent tool) to parallelize image generation across articles. Each article's assets are independent and can be generated concurrently.

Image Generation Strategy (agent-first, Gemini fallback)

For every image (illustration or cover), the sub-agent generates in this order:

1. Agent-native first — the sub-agent attempts to generate the image using its own runtime-native image-generation tool (if the runtime exposes one). Save the result directly to the target output path.
2. Gemini API fallback — if the agent has no native image tool available, or its generation fails (after one retry), fall back to the Gemini API via baoyu-image-gen:

   # Resolve the installed baoyu-image-gen skill (checks common skill dirs)
   IMAGE_GEN="$(ls ~/.agent/skills/baoyu-image-gen/scripts/main.ts \
                   ~/.claude/skills/baoyu-image-gen/scripts/main.ts \
                   ~/.claude/plugins/marketplaces/baoyu-skills/skills/baoyu-image-gen/scripts/main.ts \
                   2>/dev/null | head -1)"
   bun "$IMAGE_GEN" \
     --promptfiles <prompt_file> --image <output_path> --ar <aspect_ratio> --quality 2k --provider google
   

Hard rules:

• Always write the full prompt to prompts/NN-{type}-[slug].md BEFORE invoking any backend (reproducibility + lets fallback reuse the same prompt).
• Never substitute SVG/HTML/canvas/code-based rendering for a raster image. If the agent cannot produce a raster image, fall through to the Gemini API — do not emit vector/code art.
• In the Step 6 report, note which backend produced each batch (agent-native vs Gemini fallback).

3a: Generate Illustrations (if missing)

For each article missing illustrations, launch a sub-agent that:

1. Reads the article content
2. Analyzes structure to identify 2-4 illustration positions
3. Generates illustrations with these settings:
   • Density: balanced (per-section)
   • Type: mixed (auto-select per illustration: framework, comparison, flowchart, infographic, etc.)
   • Style: blueprint (dark background, cyan/teal lines, tech schematic feel)
   • Language: bilingual (中文主标签 + English subtitle)
   • Aspect ratio: 16:9
4. Creates prompt files in illustrations/{topic-slug}/prompts/
5. Generates images following the Image Generation Strategy above (agent-native first; Gemini API fallback via baoyu-image-gen --ar 16:9 --quality 2k --provider google)
6. Post-processes each image:

   # Compress to JPEG (resolve the installed baoyu-compress-image skill)
   COMPRESS="$(ls ~/.agent/skills/baoyu-compress-image/scripts/main.ts \
                  ~/.claude/skills/baoyu-compress-image/scripts/main.ts \
                  ~/.claude/plugins/marketplaces/baoyu-skills/skills/baoyu-compress-image/scripts/main.ts \
                  2>/dev/null | head -1)"
   bun "$COMPRESS" \
     <image.png> --format jpeg --quality 95 --output <image.jpg>
   # Strip EXIF
   sips --deleteProperty all <image.jpg>
   

7. Inserts ![description](illustrations/{slug}/XX-type-name.jpg) into the article at appropriate positions
8. If article has a paired zh/en version, inserts same image references into both

3b: Generate Cover (if missing)

For each article (or article pair) missing a cover, launch a sub-agent that:

1. Reads the article content
2. Generates a cover image prompt with:
   • Type: conceptual
   • Palette: cool (articles 1-2) or dark (article 3) — auto-select based on content
   • Rendering: flat-vector
   • Text: title-subtitle (中文标题 + English subtitle)
   • Mood: balanced
   • Font: clean
   • Aspect ratio: 2.35:1
3. Creates prompt file in cover-image/{topic-slug}/prompts/cover.md
4. Generates image following the Image Generation Strategy above (agent-native first; Gemini API fallback via baoyu-image-gen --ar 2.35:1 --quality 2k --provider google)
5. Post-processes (compress to JPEG q95 + strip EXIF)
6. Inserts ![cover](cover-image/{slug}/cover.jpg) after front matter in the article
7. If article has a paired zh/en version, inserts same cover reference into both

Step 4: Upload to R2

After all images for an article are generated, upload new images to R2:

SKILL_DIR="$HOME/.agent/skills/dan-r2-skill"
bun "$SKILL_DIR/scripts/main.ts" \
  --files "<comma-separated list of new image files>" \
  --dir "<article directory>"

This automatically:

• Uploads files to Cloudflare R2
• Replaces local paths in markdown files with CDN URLs

Step 4.5: Pre-generate Slugs

Before publishing, generate and verify slugs for all articles upfront. This allows blog and WeChat to publish in parallel since both need the slug.

For each article:

1. Generate a URL-friendly slug from the title
2. Verify uniqueness: bun run $BLOG_SKILL_DIR/scripts/blog-publish.ts --check-slug <slug>
3. Record the mapping: { title, slug, language, blog_url }
   • zh articles: blog_url = https://dhpie.com/posts/cn/{slug}
   • en articles: blog_url = https://dhpie.com/posts/en/{slug}

Step 5: Publish to All Platforms (Parallel)

Launch sub-agents in parallel for each platform. Slugs and blog URLs are already known from Step 4.5.

5a: Publish to Blog (dhpie.com)

Invoke dan-blog-sync skill for all selected articles:

SKILL_DIR="$HOME/.agent/skills/dan-blog-sync"

# 1. Check auth
bun run $SKILL_DIR/scripts/blog-publish.ts --check-auth

# 2. For each article, generate payload and publish
bun run $SKILL_DIR/scripts/blog-publish.ts --payload-file /tmp/blog-post-payload-N.json

Payload fields:

Field	Rule
title	Filename without .md extension
language	zh or en (detected in Step 2)
categoryId	zh → 158511301872074752 (cn), en → 158511301876269056 (en)。core v13 起为 Snowflake 字符串 ID，失效时用 curl -s https://api.dhpie.com/api/v3/categories 重新获取
slug	Use pre-generated slug from Step 4.5
tags	From front matter（Obsidian 与博客标签已统一，见 dan-blog-sync SKILL.md 的词表规则与 vault long-post/docs/标签规范.md）；无 front matter 时按该规范生成 3-5 个
summary	From front matter, or generate 1-2 sentence summary
hook	From front matter hook_a, format as blockquote > ...
text	Full markdown content (without front matter)
images	[]
copyright	true
allowComment	true
pin	false
pinOrder	1
relatedId	[]
isPublished	true

After publishing, insert hook blockquote at top of source file.

5b: Publish to WeChat (Chinese articles only, parallel with 5a)

For each Chinese article, invoke baoyu-post-to-wechat skill via API method.

WeChat draft/add payload 额外字段（CRITICAL）：

在调用 wechat-api.ts 发布前，确保 draft/add API 请求的 articles[] 中包含以下字段：

Field	Value	Description
content_source_url	https://dhpie.com/posts/cn/{slug}	原文链接，slug 来自 Step 4.5
need_open_comment	1	开启评论
only_fans_can_comment	0	所有人可评论

发布后手动设置（API 暂不支持）：

以下设置需要在微信公众号后台手动操作，因为 draft/add API 不直接支持：

设置	操作
声明原创	在草稿箱编辑时勾选「原创」
关闭快捷转载	原创声明后，取消勾选「允许快捷转载」
开启赞赏	编辑时开启「赞赏」功能
加入合集	发布时选择或创建合集

操作步骤：

1. 发布完成后，前往 https://mp.weixin.qq.com → 内容管理 → 草稿箱
2. 编辑每篇草稿：
   • 底部勾选「原创」→ 取消「允许快捷转载」
   • 开启「赞赏」
3. 发布时选择合集（如果合集不存在，先创建）

提醒用户： 在 Step 6 报告中明确提醒用户需要手动完成上述四项设置。

5c: Publish to X Article (parallel with 5a and 5b)

For each article, invoke baoyu-post-to-x skill to publish as an X Article (long-form markdown).

1. Read the article content (without front matter)
2. Use baoyu-post-to-x skill with article mode:
   • Title: article title (filename without .md)
   • Content: full markdown content with CDN image URLs
   • The skill handles markdown → HTML conversion, image downloading, and Chrome CDP posting
3. The skill opens Chrome with the X Article editor pre-filled — user reviews and clicks publish

Note: X Article publishing uses Chrome CDP and requires manual publish confirmation in the browser. The draft will be ready for review.

5d: Generate Xiaohongshu Cards (sequential, after 5a-5c)

For each Chinese article, invoke the baoyu-xhs-images skill to run its complete workflow. This skill has its own multi-step process with two user confirmations — follow it exactly.

IMPORTANT: Do NOT bypass or shortcut the baoyu-xhs-images workflow. It has 6 steps including 2 required user confirmations. Invoke the skill and let it run its full flow.

Invocation:

Skill: baoyu-xhs-images
Args: <path-to-chinese-article.md>

The skill will execute these steps internally:

1. Step 0: Load preferences (EXTEND.md)
2. Step 1: Deep content analysis → analysis.md (content type, hook analysis, audience, engagement design, swipe flow)
3. Step 2: ⚠️ Confirmation 1 — Validate content understanding with user (core selling points, target audience, style preference)
4. Step 3: Generate 3 outline strategies (Story-Driven / Information-Dense / Visual-First), each with different style recommendations
5. Step 4: ⚠️ Confirmation 2 — User selects outline strategy, visual style, and element preferences
6. Step 5: Generate images sequentially (5-10 cards, 3:4 aspect ratio, 1080×1440px)
7. Step 6: Completion report

Output directory: xhs-images/{topic-slug}/ (NOT xhs-cards/)

After completion:

• Report card count, file paths, and suggested posting text
• Include blog URL in the last card for traffic redirection
• Generate suggested XHS caption with hashtags

Note: XHS cards are generated locally, not auto-posted. User manually uploads to Xiaohongshu app. The skill handles all style/layout decisions through its confirmation flow — do not pre-select these in dan-publish-all.

Sequencing: Because baoyu-xhs-images requires 2 user confirmations, it should run AFTER the other parallel publishing tasks (5a-5c) complete, so it doesn't block those. Alternatively, launch it in parallel but expect the user to interact with its confirmation prompts while other tasks run in background.

Step 6: Report Results

发布完成！

配图：X 篇文章生成了 Y 张插图
封面：生成了 Z 张封面图
R2：上传了 N 个文件
博客：发布了 A 篇文章到 dhpie.com
  - [title1]: [url1]
  - [title2]: [url2]
公众号：发布了 B 篇草稿到微信公众号（原文链接已设置为博客地址）
  - [title1]: media_id → 原文链接: [blog_url]
  - [title2]: media_id → 原文链接: [blog_url]

X Article：C 篇文章已在 Chrome 中打开预览
  - [title1]: 请在浏览器中确认后点击发布

小红书：生成了 D 组卡片（via baoyu-xhs-images skill）
  - [title1]: E 张卡片 → xhs-images/{slug}/
  - 建议配文已生成

⚠️ 公众号草稿还需手动设置：
  1. 勾选「原创」→ 取消「允许快捷转载」
  2. 开启「赞赏」
  3. 加入合集
前往操作：https://mp.weixin.qq.com → 内容管理 → 草稿箱

Parallelization Strategy

                    ┌─ Agent: Article 1 illustrations ─┐
Step 3 (parallel) ──┼─ Agent: Article 2 illustrations ─┼── wait all
                    ├─ Agent: Article 3 illustrations  │
                    ├─ Agent: Cover 1                  │
                    ├─ Agent: Cover 2                  │
                    └─ Agent: Cover 3                 ─┘
                              │
Step 4 (sequential) ── R2 upload (--files, all new images)
                              │
Step 4.5 ── Pre-generate slugs + blog URLs
                              │
                    ┌─ Agent: Blog publish (all articles)              ─┐
Step 5 (parallel) ──┼─ Agent: WeChat publish (zh, 原文链接=blog URL)  ─┼── wait all
                    └─ Agent: X Article publish (all articles)         ─┘
                              │
Step 5d (sequential) ── baoyu-xhs-images skill (zh articles, requires 2 user confirmations)
                              │
Step 6 ── Report results

Notes

• Image generation is agent-first: the sub-agent uses its runtime-native image tool when available, and only falls back to the Gemini API (baoyu-image-gen --provider google) when no native tool exists or generation fails
• Blueprint style ensures visual consistency across the series
• Paired zh/en articles share the same illustrations and covers
• WeChat only receives Chinese articles; blog receives both zh and en
• R2 upload uses --files flag to only upload newly generated images
• X Article uses Chrome CDP via baoyu-post-to-x — draft opens in browser for manual publish confirmation
• If auth for any platform expires, report which platform and stop that branch only
• XHS cards use the full baoyu-xhs-images skill workflow (analysis → 2 confirmations → generation) — not a shortcut
• XHS cards are generated locally, not auto-posted — user uploads manually via Xiaohongshu app
• XHS output goes to xhs-images/{slug}/ (not xhs-cards/)