Back to Details

youmind-article-dispatch

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Content Dispatch Hub — One Topic, Every Platform

内容分发中心——一个主题，覆盖全平台

Distribute your content to multiple platforms from a single topic. Each platform skill independently adapts content for its target audience — developers on Dev.to, newsletter readers on Ghost, and more.
Get YouMind API Key → · More Skills →
基于单个主题将内容分发至多个平台。每个平台Skill会针对目标受众独立调整内容——比如面向Dev.to的开发者、Ghost的通讯订阅读者等。
获取YouMind API密钥 → · 更多Skill →

Onboarding

入门引导

⚠️ MANDATORY: When the user has just installed this skill, run the onboarding flow IMMEDIATELY. Translate to the user's language.
The onboarding flow sets up TWO things in ONE conversation: platform roster (where to publish) and author DNA (how to write). These are NOT separate steps — they happen together during the first dispatch.
⚠️ 强制要求：当用户刚安装此Skill时，立即执行入门引导流程。请翻译成用户使用的语言。
入门引导流程会在一次对话中完成两项设置：平台清单（发布目标平台）和作者特征库（写作风格）。这两个步骤并非分开进行——它们会在首次分发过程中同步完成。

Phase 1: Platform roster (30 seconds)

第一阶段：平台清单（30秒）

✅ Content Dispatch Hub installed!
Quick setup — which platforms do you use?
  1. Dev.to 2. Hashnode 3. WordPress 4. Tumblr 5. Ghost
  2. Beehiiv 7. Kit 8. X/Twitter 9. WeChat (公众号) 10. Qiita
(list numbers, e.g. "1, 5, 8")
After user selects:
  1. Save to 
    ~/.youmind/dispatch-roster.yaml
    → 
    active_platforms
  2. For each selected, check skill installed + YouMind connection via 
    validate
  3. Report status table (✅ connected / ❌ → setup link)
✅ 内容分发中心已安装！
快速设置——你使用哪些平台？
  1. Dev.to 2. Hashnode 3. WordPress 4. Tumblr 5. Ghost
  2. Beehiiv 7. Kit 8. X/Twitter 9. 微信（公众号） 10. Qiita
（请列出数字，例如："1, 5, 8"）
用户选择后：
  1. 保存至
    ~/.youmind/dispatch-roster.yaml
    的
    active_platforms
    字段
  2. 针对每个选中的平台，检查Skill是否已安装以及通过
    validate
    验证YouMind连接状态
  3. 生成状态表格（✅ 已连接 / ❌ → 设置链接）

Phase 2: Author DNA bootstrap (integrated into first dispatch)

第二阶段：作者特征库初始化（集成到首次分发中）

Do NOT ask the user to fill a profile form. Instead, bootstrap the author profile from one of two paths:
Path A — User has articles in YouMind KB (preferred):
  1. Call YouMind search API to fetch the user's recent 10–15 articles
  2. Analyze across articles: avg paragraph length, code density, language distribution, opening patterns, depth level, typical word count, tone markers
  3. Propose a profile:
📝 I analyzed your recent articles. Here's what I see:
  • Voice: Conversational-technical, first-person practitioner
  • Audience: Mid-level developers (you assume REST/Git knowledge)
  • Code density: High (avg 4 code blocks per article)
  • Depth: Practitioner-level (how-to with real gotchas, not beginner intros)
  • Languages: English primary, Chinese secondary
  • Signature moves: You always lead with the problem, include a gotchas section, and end with working code
Sound right? I'll use this as your baseline across all platforms. You can adjust anytime.
  1. User confirms/adjusts → save to 
    ~/.youmind/author-profile.yaml
  2. Immediately proceed to first dispatch with the profile active
Path B — New user, no articles (cold start): Embed 3 targeted questions INTO the first dispatch request, not as a separate quiz:
You said: "帮我写一篇关于 AI agents 的文章发到 Dev.to 和 X"
Great! Since this is your first dispatch, 3 quick questions so I write in YOUR voice:
1. 这篇文章的风格？ (a) 代码先行，先看效果再讲原理 (b) 故事驱动，用经历带出技术点 (c) 数据说话，benchmark 和对比为主 (d) 手把手教学，假设读者是入门者
2. 你的读者是谁？ (a) 做产品的开发者 (b) 正在学习的学生/新人 (c) 做技术决策的 TL/架构师 (d) 泛科技读者
3. 你的内容里绝对不要出现什么？ (自由回答 — 例如"不要营销话术"、"不要 AI 味"、"不要太长")
After user answers:
  1. Map answers to 
    author-profile.yaml
    fields
  2. Save profile
  3. Immediately continue the dispatch — no second round-trip. The first article is generated WITH the profile already active.
  4. After publishing, confirm: "Saved as your writing profile. Next time just say '帮我分发', I know your style."
请勿要求用户填写资料表单。 而是通过以下两种方式之一初始化作者资料：
路径A——用户YouMind知识库中有文章（优先选择）：
  1. 调用YouMind搜索API获取用户最近10-15篇文章
  2. 分析这些文章：平均段落长度、代码密度、语言分布、开篇模式、内容深度、典型字数、语气特征
  3. 生成一份资料建议：
📝 我分析了你的近期文章，发现以下特征：
  • 语气： 兼具技术性与对话感，第一人称从业者视角
  • 受众： 中级开发者（默认你假设读者具备REST/Git知识）
  • 代码密度： 高（平均每篇文章包含4个代码块）
  • 内容深度： 从业者级别（包含实际陷阱的实操指南，而非入门介绍）
  • 语言： 英文为主，中文为辅
  • 标志性风格： 你总是以问题开篇，包含陷阱提示章节，并以可运行代码结尾
是否符合你的风格？ 我将以此作为你在所有平台的基准风格，你可随时调整。
  1. 用户确认/调整后 → 保存至
    ~/.youmind/author-profile.yaml
  2. 立即使用该资料进行首次分发
路径B——新用户，无文章（冷启动）： 将3个针对性问题嵌入首次分发请求中，而非作为单独测验：
你说："帮我写一篇关于AI agents的文章发到Dev.to和X"
好的！这是你首次使用分发功能，我有3个快速问题以便匹配你的写作风格：
1. 这篇文章的风格？ (a) 代码先行，先看效果再讲原理 (b) 故事驱动，用经历带出技术点 (c) 数据说话，以基准测试和对比为主 (d) 手把手教学，假设读者是入门者
2. 你的读者是谁？ (a) 做产品的开发者 (b) 正在学习的学生/新人 (c) 做技术决策的TL/架构师 (d) 泛科技读者
3. 你的内容里绝对不要出现什么？ （自由回答——例如"不要营销话术"、"不要AI腔"、"不要太长"）
用户回答后：
  1. 将答案映射到
    author-profile.yaml
    的对应字段
  2. 保存资料
  3. 立即继续分发流程——无需二次交互。首篇文章将直接使用该资料生成。
  4. 发布完成后，确认："已保存为你的写作风格。下次只需说'帮我分发'，我就知道你的风格了。"

Why this matters

为什么这很重要

ApproachFirst article qualityUser friction
❌ No profilingGeneric, platform-defaultZero (but bad output)
❌ Separate 5-question formBetter, but profile ≠ real usageHigh (feels like homework)
✅ Path A: KB bootstrapExcellent — based on real writingNear-zero (confirm/adjust)
✅ Path B: 3 inline questionsGood — targeted baselineLow (embedded in first dispatch)
方式首篇文章质量用户操作成本
❌ 无资料配置通用化，平台默认风格零成本（但输出质量差）
❌ 单独5题表单质量较好，但资料与实际使用脱节高成本（像做作业）
✅ 路径A：知识库初始化极佳——基于真实写作内容几乎零成本（仅需确认/调整）
✅ 路径B：3个嵌入式问题良好——针对性基准风格低成本（嵌入首次分发）

Roster + Profile updates after onboarding

入门后的清单与资料更新

"Add Ghost to my platforms" → update 
~/.youmind/dispatch-roster.yaml
"Remove X/Twitter" → update roster "I want to write more beginner content" → update 
~/.youmind/author-profile.yaml
"Analyze my recent articles again" → re-run Path A bootstrap
"把Ghost添加到我的平台" → 更新
~/.youmind/dispatch-roster.yaml
"移除X/Twitter" → 更新平台清单 "我想写更多面向入门者的内容" → 更新
~/.youmind/author-profile.yaml
"重新分析我的近期文章" → 重新执行路径A的初始化流程

Usage Modes

使用模式

Mode 1: Single Platform Routing

模式1：单平台路由

User specifies one platform → dispatch directly invokes the corresponding platform skill.
"Write about AI agents for Dev.to"         → invoke youmind-devto-article
"Write a weekly issue for Beehiiv"         → invoke youmind-beehiiv-article
"Write a Tumblr post about indie hacking"  → invoke youmind-tumblr-article
"Draft a public creator post for Kit"      → invoke youmind-kit-article
"Post a thread about startup culture on X" → invoke youmind-x-article
"发布一篇技术文章到 WordPress"                → invoke youmind-wordpress-article
用户指定单个平台 → 分发中心直接调用对应平台的Skill。
"Write about AI agents for Dev.to"         → 调用youmind-devto-article
"Write a weekly issue for Beehiiv"         → 调用youmind-beehiiv-article
"Write a Tumblr post about indie hacking"  → 调用youmind-tumblr-article
"Draft a public creator post for Kit"      → 调用youmind-kit-article
"Post a thread about startup culture on X" → 调用youmind-x-article
"发布一篇技术文章到 WordPress"                → 调用youmind-wordpress-article

Mode 2: Multi-Platform Dispatch

模式2：多平台分发

User specifies multiple platforms → dispatch invokes each platform skill sequentially with the same topic.
"Write about AI agents and publish to Dev.to, Beehiiv, and Kit"
"把这个话题发布到 Dev.to 和 Hashnode"
用户指定多个平台 → 分发中心依次调用每个平台的Skill，使用同一主题。
"Write about AI agents and publish to Dev.to, Beehiiv, and Kit"
"把这个话题发布到 Dev.to 和 Hashnode"

Mode 3: All-Platform Broadcast

模式3：全平台广播

User wants maximum reach → dispatch to all installed platform skills.
"Publish everywhere about the future of AI coding"
"全平台发布：AI 编程的未来"
用户希望获得最大曝光 → 分发至所有已安装的平台Skill。
"Publish everywhere about the future of AI coding"
"全平台发布：AI 编程的未来"

Platform Skills Are Independent

平台Skill相互独立

Each 
youmind-{platform}-article
skill is independently installed, independently published, and fully self-contained. They work without this dispatch hub. Dispatch is an optional orchestration layer — not a dependency, not a framework that platform skills must fit into.
每个
youmind-{platform}-article
Skill都是独立安装、独立发布且完全自包含的。它们无需依赖此分发中心即可运行。分发中心是一个可选的编排层——并非平台Skill的依赖项，也不是平台Skill必须适配的框架。

How dispatch connects to platform skills (when both are installed)

分发中心与平台Skill的连接方式（当两者均已安装时）

  • Discovery, not coupling. Dispatch scans for installed 
    youmind-*-article
    skills at runtime. It optionally reads a small 
    dispatch-capabilities.yaml
    at each skill's root to learn what operations that skill supports (generate, adapt, condense, translate, etc.) and its hard limits. If a platform skill does not ship this file, dispatch falls back to sensible defaults and still invokes it normally.
  • Brief is an optional extra, not a requirement. When dispatch invokes a platform skill, it passes a content brief (topic, angle, keywords, optional 
    resolved_author
    block). Platform skills that understand these fields use them as richer context; skills that don't simply ignore the extras and work as usual.
  • Author profile lives in the user's home directory, not in this skill. Both this hub and platform skills read 
    ~/.youmind/author-profile.yaml
    — the canonical shared location defined in 
    shared/YOUMIND_HOME.md
    . Uninstalling dispatch does not remove the profile; platform skills continue to work standalone with full DNA support.
  • Results flow back as a standardized shape (status, URL, 
    result_links
    , title, conformance_report) so dispatch can aggregate multi-platform runs. Each platform skill publishes this same result shape regardless of whether dispatch is present — it's a clean output API, not a contract with dispatch.
  • 发现而非耦合：分发中心在运行时扫描已安装的
    youmind-*-article
    Skill。它可选择性读取每个Skill根目录下的小型
    dispatch-capabilities.yaml
    文件，以了解该Skill支持的操作（生成、调整、压缩、翻译等）及其硬性限制。如果平台Skill未提供此文件，分发中心会回退至合理默认值，仍可正常调用该Skill。
  • 内容简报是可选增强，非必需项：分发中心调用平台Skill时，会传递一份内容简报（主题、角度、关键词、可选的
    resolved_author
    块）。能识别这些字段的平台Skill会将其作为更丰富的上下文；无法识别的平台Skill则会忽略这些额外信息，照常运行。
  • 作者资料存储在用户主目录，而非此Skill中：分发中心和平台Skill均读取
    ~/.youmind/author-profile.yaml
    ——这是
    shared/YOUMIND_HOME.md
    中定义的标准共享位置。卸载分发中心不会删除该资料；平台Skill仍可独立运行并完整支持特征库功能。
  • 结果以标准化格式返回（状态、URL、
    result_links
    、标题、conformance_report），以便分发中心汇总多平台运行结果。无论分发中心是否存在，每个平台Skill都会发布相同格式的结果——这是一个清晰的输出API，而非与分发中心的契约。

Zero coupling obligations for platform skills

平台Skill无耦合义务

  • Platform skills do NOT import from dispatch.
  • Platform skills do NOT require dispatch to be installed.
  • Platform skills do NOT break if dispatch is uninstalled.
  • Platform skills do NOT need to be updated when dispatch changes.
  • dispatch-capabilities.yaml
    is opt-in metadata that lets dispatch route more intelligently. Removing it reverts to defaults; it never breaks the platform skill.
The optional integration protocol is documented at 
shared/DISPATCH_CONTRACT.md
 (v1.0). Platform skills that want richer dispatch integration may follow it; those that don't, don't.
  • 平台Skill无需从分发中心导入代码。
  • 平台Skill无需安装分发中心即可运行。
  • 卸载分发中心不会导致平台Skill失效。
  • 分发中心更新时，平台Skill无需同步更新。
  • dispatch-capabilities.yaml
    是可选元数据，可让分发中心更智能地路由。移除该文件会回退至默认值，但绝不会导致平台Skill失效。
可选集成协议记录在
shared/DISPATCH_CONTRACT.md
（v1.0）中。希望与分发中心实现更丰富集成的平台Skill可遵循此协议；无需集成的则可忽略。

Platform Registry

平台注册表

PlatformSkillAudienceBest For
Dev.to
youmind-devto-article
Developers, OSS contributorsTechnical tutorials, tool reviews, dev experience
Hashnode
youmind-hashnode-article
Dev bloggers, tech writersIn-depth technical blogs, series, developer stories
WordPress
youmind-wordpress-article
General audiencesLong-form articles, SEO-optimized content
Tumblr
youmind-tumblr-article
Blog followers, creator audiencesVoice-driven essays, build logs, creator notes
Ghost
youmind-ghost-article
Publishers, newsletter writersEditorial content, premium publications
Beehiiv
youmind-beehiiv-article
Newsletter operators, creator teamsGrowth updates, newsletter essays, operator notes
Kit
youmind-kit-article
Creators, audience buildersBroadcasts, creator updates, public newsletter feed posts
X/Twitter
youmind-x-article
General, viral audiencesHot takes, threads, breaking news commentary
WeChat
youmind-wechat-article
Chinese audiencesStyled long-form articles, official account content
Qiita
youmind-qiita-article
Japanese developersTechnical articles, tutorials, knowledge sharing
Auth: All platforms use YouMind OpenAPI. You need only a 
youmind.api_key
— platform credentials are stored encrypted in YouMind Connector Settings. No local platform keys.
Note: Each platform skill must be installed separately. Dispatch checks your roster (
dispatch-roster.yaml
) on each run.
平台Skill受众适用场景
Dev.to
youmind-devto-article
开发者、开源贡献者技术教程、工具评测、开发者体验分享
Hashnode
youmind-hashnode-article
开发者博主、技术作者深度技术博客、系列文章、开发者故事
WordPress
youmind-wordpress-article
通用受众长文、SEO优化内容
Tumblr
youmind-tumblr-article
博客追随者、创作者受众个性化随笔、构建日志、创作者笔记
Ghost
youmind-ghost-article
出版商、通讯作者编辑内容、付费出版物
Beehiiv
youmind-beehiiv-article
通讯运营者、创作者团队增长更新、通讯随笔、运营笔记
Kit
youmind-kit-article
创作者、受众构建者广播内容、创作者更新、公开通讯订阅源帖子
X/Twitter
youmind-x-article
通用受众、易传播受众热点观点、推文线程、突发新闻评论
微信
youmind-wechat-article
中文受众风格化长文、公众号内容
Qiita
youmind-qiita-article
日本开发者技术文章、教程、知识分享
认证： 所有平台均使用YouMind OpenAPI。你仅需
youmind.api_key
——平台凭据加密存储在YouMind连接器设置中。无需本地存储平台密钥。
注意： 每个平台Skill必须单独安装。分发中心每次运行时都会检查你的平台清单（
dispatch-roster.yaml
）。

Quick Skill Hints

快速Skill提示

Use these as lightweight routing clues before you open the full platform skill:
  • youmind-devto-article
    : code-first Markdown posts, TL;DR, practical developer tutorial voice
  • youmind-hashnode-article
    : deeper developer-blog storytelling, series-friendly, canonical-aware cross-posting
  • youmind-wordpress-article
    : HTML CMS publishing, taxonomy/excerpt aware, company-blog friendly
  • youmind-tumblr-article
    : voice-driven creator posting, one title plus one clean rich-text body
  • youmind-ghost-article
    : editorial publication tone, excerpt/tag aware, newsletter-style HTML
  • youmind-beehiiv-article
    : newsletter-first writing, subject/preview/web-email surfaces matter
  • youmind-kit-article
    : creator broadcast format, inbox/feed readability, compact CTA structure
  • youmind-x-article
    : concise hooks, thread splitting, sparse hashtags, native social adaptation
  • youmind-wechat-article
    : WeChat-native rich formatting, draft-box publishing, built-in direct-send for ready articles
  • youmind-qiita-article
    : Japanese developer Markdown, environment/setup context, note-box friendly
在打开完整平台Skill前，可将以下内容作为轻量路由线索：
  • youmind-devto-article
    ：代码优先的Markdown帖子，包含TL;DR，实用开发者教程语气
  • youmind-hashnode-article
    ：更深度的开发者博客叙事，适合系列文章，支持规范跨平台发布
  • youmind-wordpress-article
    ：HTML CMS发布，支持分类法/摘要，适合企业博客
  • youmind-tumblr-article
    ：个性化创作者发帖，一个标题加一个简洁富文本正文
  • youmind-ghost-article
    ：编辑出版语气，支持摘要/标签，通讯风格HTML
  • youmind-beehiiv-article
    ：通讯优先写作，主题/预览/网页-邮件展示至关重要
  • youmind-kit-article
    ：创作者广播格式，收件箱/订阅源可读性强，紧凑CTA结构
  • youmind-x-article
    ：简洁钩子，线程拆分，稀疏话题标签，原生社交适配
  • youmind-wechat-article
    ：微信原生富格式，草稿箱发布，内置已完成文章直接发送功能
  • youmind-qiita-article
    ：日本开发者Markdown，包含环境/设置上下文，适合笔记框

Dispatch Pipeline

分发流程

Step 1: Parse Request + Load Roster

步骤1：解析请求 + 加载平台清单

  • Extract topic/brief from user input
  • Load 
    ~/.youmind/dispatch-roster.yaml
    for the user's active platform list
  • Resolve target platforms:
    • User says "帮我分发" / "publish everywhere" → use 
      active_platforms
      from roster
    • User specifies platforms explicitly → use those (even if not in roster)
    • No roster exists → ask user which platforms (triggers onboarding)
  • For each target platform: verify skill installed + connection status from roster
  • Skip platforms that are not installed or not connected (with clear message + setup link)
  • 从用户输入中提取主题/简报
  • 加载用户的
    ~/.youmind/dispatch-roster.yaml
    获取活跃平台列表
  • 确定目标平台：
    • 用户说"帮我分发"/"publish everywhere" → 使用清单中的
      active_platforms
    • 用户明确指定平台 → 使用这些平台（即使不在清单中）
    • 无清单存在 → 询问用户选择哪些平台（触发入门引导）
  • 针对每个目标平台：验证Skill是否已安装以及清单中的连接状态
  • 跳过未安装或未连接的平台（显示清晰提示信息 + 设置链接）

Step 2: Load Author Profile + Generate Content Brief

步骤2：加载作者资料 + 生成内容简报

2a — Load author profile (if exists): Read 
~/.youmind/author-profile.yaml
(canonical shared location — see 
shared/YOUMIND_HOME.md
). This file captures the user's cross-platform writing DNA — voice, audience, content preferences, and per-platform overrides. See 
references/author-profile-spec.md
for format. Fallback: if the 
~/.youmind/
path is missing but 
skills/youmind-article-dispatch/author-profile.yaml
exists (legacy), offer to migrate.
If no profile exists → skip this step; dispatch works without it (just less personalized). After the first successful dispatch, offer to help the user build one.
2b — Generate content brief (see 
references/content-brief-format.md
):
yaml
topic: "The core topic sentence"
angle: "The specific angle or atomic insight"
keywords: ["keyword1", "keyword2", "keyword3"]
language: "en"        # or zh, ja, etc.
source_material: []   # from YouMind knowledge mining (if available)
resolved_author: {}   # per-platform resolved profile (computed in Step 3)
constraints: {}       # any user-specified constraints
YouMind knowledge mining: If the user has a YouMind API key configured in any platform skill's config, run 
mine-topics
ONCE and include the results in the brief. This avoids redundant YouMind calls across platform skills.
2c — Resolve author profile per platform: For EACH target platform, merge the author profile with that platform's DNA using the rules in 
references/content-adaptation-matrix.md
. This produces a resolved per-platform profile — NOT the raw author file. Each platform skill receives only the resolved, relevant fields for its platform. This prevents raw-profile leakage and irrelevant context bleed.
If a depth mismatch is detected (e.g., author targets "expert" but platform audience is "general"), the merge triggers a mandatory outline adaptation step — not just a warning. See matrix Priority 5.
2a — 加载作者资料（如果存在）： 读取
~/.youmind/author-profile.yaml
（标准共享位置——参见
shared/YOUMIND_HOME.md
）。该文件记录了用户跨平台写作的核心特征——语气、受众、内容偏好以及平台专属配置。格式参见
references/author-profile-spec.md
。回退方案：如果
~/.youmind/
路径不存在但
skills/youmind-article-dispatch/author-profile.yaml
存在（旧版本），则提供迁移选项。
如果无资料存在 → 跳过此步骤；分发中心可正常运行（仅个性化程度较低）。首次成功分发后，主动帮助用户创建资料。
2b — 生成内容简报（参见
references/content-brief-format.md
）：
yaml
topic: "核心主题句"
angle: "特定角度或核心见解"
keywords: ["keyword1", "keyword2", "keyword3"]
language: "en"        # 或 zh、ja等
source_material: []   # 来自YouMind知识库挖掘（如果可用）
resolved_author: {}   # 步骤3中计算的平台专属资料
constraints: {}       # 用户指定的任何限制条件
YouMind知识库挖掘： 如果用户在任意平台Skill的配置中已设置YouMind API密钥，运行一次
mine-topics
并将结果包含在简报中。这样可避免平台Skill重复调用YouMind。
2c — 为每个平台解析作者资料： 针对每个目标平台，使用
references/content-adaptation-matrix.md
中的规则将作者资料与平台特征合并。生成平台专属解析后资料——而非原始作者文件。每个平台Skill仅会收到针对其平台的解析后相关字段。这样可防止原始资料泄露和无关上下文干扰。
如果检测到深度不匹配（例如作者目标受众为"专家"但平台受众为"通用"），合并过程会触发强制大纲调整步骤——而非仅发出警告。参见矩阵优先级5。

Step 3: Dispatch to Platform Skills

步骤3：分发至平台Skill

For each target platform, invoke the platform skill with the content brief as context.
Sequential mode (default): Run each platform skill one at a time. The agent reads each skill's SKILL.md and follows its pipeline, passing the content brief as the initial topic/context.
Parallel mode (if subagents available): Spawn one subagent per platform. Each subagent independently runs its platform skill's full pipeline. Use this when the agent platform supports parallel subagents.
MANDATORY: Pass the content brief to each platform skill. When invoking a platform skill, include:
  1. The topic and angle from the brief
  2. Any YouMind knowledge context already mined
  3. The instruction to adapt content for that specific platform's audience
针对每个目标平台，调用对应的平台Skill并传递内容简报作为上下文。
顺序模式（默认）： 逐个运行每个平台Skill。Agent会读取每个Skill的SKILL.md并遵循其流程，将内容简报作为初始主题/上下文传递。
并行模式（如果支持子Agent）： 为每个平台生成一个子Agent。每个子Agent独立运行其平台Skill的完整流程。当Agent平台支持并行子Agent时使用此模式。
强制要求： 将内容简报传递给每个平台Skill。调用平台Skill时，需包含：
  1. 简报中的主题和角度
  2. 已挖掘的YouMind知识上下文
  3. 针对特定平台受众调整内容的指令

Step 4: Collect Results

步骤4：收集结果

Gather results from all platform dispatches:
FieldDescription
platformPlatform name
status
published
/ 
draft
/ 
failed
/ 
skipped
urlURL of published content (if available)
result_linksBest clickable links for post page / dashboard / stats entry
titleFinal title used
errorError message (if failed)
汇总所有平台分发的结果：
字段描述
platform平台名称
status
published
/ 
draft
/ 
failed
/ 
skipped
url已发布内容的URL（如果可用）
result_links帖子页面/仪表盘/统计入口的最佳可点击链接
title使用的最终标题
error错误信息（如果失败）

Step 5: Summary Report

步骤5：汇总报告

Present a summary table to the user:
undefined
向用户展示汇总表格：
undefined

Dispatch Results

分发结果

PlatformStatusTitleURL
Dev.to✅ Published"AI Agents: A Practical Guide"https://dev.to/...
Ghost✅ Published"Why AI Agents Matter for..."https://newsletter.example.com/...
X/Twitter✅ Thread posted"🧵 AI Agents are changing..."https://x.com/...

After the table, add a compact `Result links` section for each platform so the user can click straight into the post page, dashboard, or stats entry point. If a platform has no direct analytics URL, include the best platform entry URL instead.
平台状态标题URL
Dev.to✅ 已发布"AI Agents: A Practical Guide"https://dev.to/...
Ghost✅ 已发布"Why AI Agents Matter for..."https://newsletter.example.com/...
X/Twitter✅ 已发布推文线程"🧵 AI Agents are changing..."https://x.com/...

表格之后，添加一个紧凑的「结果链接」部分，为每个平台提供直接跳转至帖子页面、仪表盘或统计入口的链接。如果平台无直接分析URL，则提供最佳平台入口URL。

Resilience Rules

弹性规则

RuleDescription
Isolate failuresOne platform failing MUST NOT stop other platforms. Report partial results.
Progress updatesAfter each platform completes, show a brief status update to the user.
Missing skillsIf a requested platform skill is not installed, skip it with a clear message.
Config missingIf a platform skill's config is not set up, skip it and suggest setup instructions.
Fallback to draftWhen in doubt, create as draft rather than publishing directly.
规则描述
隔离故障单个平台失败绝不能影响其他平台。需展示部分结果。
进度更新每个平台完成后，向用户展示简短状态更新。
缺失Skill如果请求的平台Skill未安装，跳过该平台并显示清晰提示。
配置缺失如果平台Skill的配置未设置，跳过该平台并建议设置说明。
回退至草稿存疑时，优先创建草稿而非直接发布。

References

参考资料

FilePurpose
references/platform-registry.md
Detailed platform capabilities, audience profiles, and constraints
references/dispatch-protocol.md
Step-by-step dispatch workflow with examples
references/content-brief-format.md
Standardized content brief format specification (v2: includes resolved author profile)
references/author-profile-spec.md
Author profile format, cold-start guide, evolution strategy
references/content-adaptation-matrix.md
How author DNA × platform DNA merge (priority rules, merge algorithm)
references/profile-learning.md
How author DNA accumulates from usage (5 learning sources, diff analysis, cadence)
shared/YOUMIND_HOME.md
User-home directory convention (
~/.youmind/
— shared across ALL YouMind skills)
shared/DISPATCH_CONTRACT.md
Optional interop protocol between this hub and platform skills (v1.0)
skills/youmind-{platform}-article/dispatch-capabilities.yaml
Per-platform capability manifest (dispatch reads dynamically)
author-profile.example.yaml
Example author profile — copy to 
~/.youmind/author-profile.yaml
and customize
文件用途
references/platform-registry.md
详细的平台能力、受众资料和限制条件
references/dispatch-protocol.md
分步分发流程及示例
references/content-brief-format.md
标准化内容简报格式规范（v2：包含解析后作者资料）
references/author-profile-spec.md
作者资料格式、冷启动指南、演进策略
references/content-adaptation-matrix.md
作者特征×平台特征的合并方式（优先级规则、合并算法）
references/profile-learning.md
作者特征如何从使用中积累（5个学习来源、差异分析、更新频率）
shared/YOUMIND_HOME.md
用户主目录约定（
~/.youmind/
——所有YouMind Skill共享）
shared/DISPATCH_CONTRACT.md
可选分发中心与平台Skill的互操作协议（v1.0）
skills/youmind-{platform}-article/dispatch-capabilities.yaml
平台专属能力清单（分发中心动态读取）
author-profile.example.yaml
作者资料示例——复制至
~/.youmind/author-profile.yaml
并自定义