Back to Details

self-media-video-publisher

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

视频发布

Video Publishing

目标

Objective

把确认过的视频成片和平台文案，准确、完整地送到用户选择的平台，并把结果记回任务卡。默认交付手动发布包；外部上传只在逐平台授权后进行，优先上传为私密或草稿，由用户自己点公开。
Deliver the confirmed final video and platform copy accurately and completely to the platforms selected by the user, and record the results on the task card. The default deliverable is a manual publishing package. External uploads are performed only after authorization is granted for each platform, preferably as private or draft content, with the user clicking Publish themselves.

前置条件

Prerequisites

  • 终稿已确认：用户完整看过、听过成片。
  • 各平台版本和发布字段已就绪，见 
    self-media-short-video
    的 video-platform-versions.md 和平台文案模块的各平台规范。
  • 有配乐或素材署名要求时，署名文本已写进各平台描述。
缺少任一项时，报告缺口并停在 
AWAITING_USER
，不带着缺口上传。
  • The final cut has been confirmed: the user has watched or listened to the entire finished video.
  • The video version and publishing fields for each platform are ready. See video-platform-versions.md in 
    self-media-short-video
    and the platform-specific guidelines in the platform copy module.
  • If music or assets require attribution, the attribution text has been added to each platform description.
If any item is missing, report the gap and stop at 
AWAITING_USER
; do not upload with unresolved gaps.

发布方式分级

Publishing Method Tiers

从低到高，每升一级都需要用户对该平台、该条视频单独授权：
级别方式谁点“发布”适用
L0 手动发布包交付文件、封面、字幕和逐字段文案，用户自己上传用户默认；任何平台
L1 填表助手浏览器扩展或已登录浏览器自动打开发布页并填好字段用户检查后亲自点想省去重复填表，又要逐个把关
L2 私密上传或草稿官方 API 或上传工具上传为私密、不公开或草稿用户在后台检查后公开YouTube 官方 API；支持草稿的平台
L3 定时发布上传并设定公开时间到点自动公开只在用户明确给出平台、视频和时间后使用
“全部发了吧”这类笼统指令不等于 L3 授权。逐平台列出将要执行的动作（平台、文件、标题、公开范围、时间），用户确认后再执行。
From lowest to highest, each increase in level requires the user to authorize that specific platform and video separately:
LevelMethodWho clicks “Publish”Use case
L0 Manual publishing packageDeliver the files, cover, subtitles, and field-by-field copy for the user to uploadUserDefault for every platform
L1 Form-filling assistantA browser extension or signed-in browser automatically opens the publishing page and fills in the fieldsUser checks the content and clicks Publish personallyAvoid repetitive form-filling while retaining individual control over each post
L2 Private upload or draftUpload as private, unlisted, or draft content through an official API or upload toolUser publishes it after checking the backendOfficial YouTube API; platforms that support drafts
L3 Scheduled publishingUpload the content and set its publication timeIt becomes public automatically at the scheduled timeOnly when the user explicitly provides the platform, video, and time
A vague instruction such as “publish them all” does not constitute L3 authorization. List the actions to be performed for each platform, including the platform, file, title, visibility, and time. Execute them only after the user confirms.

适配器发现

Adapter Discovery

先发现当前环境已有的能力，不要求用户为本 Skill 安装特定工具。常见选项和各自边界见 upload-adapters.md：
  • YouTube：优先使用官方 YouTube Data API（用户本人完成 OAuth 授权），或已登录的 YouTube Studio。
  • 抖音、视频号、小红书：通常没有面向个人创作者的公开上传 API。可选的有填表类浏览器扩展、基于浏览器自动化的开源上传工具，或用户手动上传。
  • 非官方自动化可能违反平台条款或触发风控，新账号尤其敏感。向用户说明风险，由用户选择。
没有可用适配器，或用户不想安装时，直接交付 L0 手动发布包。
First discover the capabilities already available in the current environment. Do not require the user to install a specific tool for this Skill. Common options and their respective boundaries are described in upload-adapters.md:
  • YouTube: Prefer the official YouTube Data API, with the user completing OAuth authorization personally, or use a signed-in YouTube Studio session.
  • Douyin, WeChat Channels, and Xiaohongshu: Public upload APIs for individual creators are generally unavailable. Options include form-filling browser extensions, open-source browser-automation upload tools, or manual uploads.
  • Unofficial automation may violate platform terms or trigger risk controls, especially for new accounts. Explain the risks and let the user choose.
If no adapter is available, or the user does not want to install one, deliver an L0 manual publishing package directly.

发布流程

Publishing Workflow

  1. 核对发布包：逐平台检查视频文件、画幅、时长、封面、字幕、标题、描述、话题、署名和 AI 标识字段，缺什么报什么。
  2. 列出执行计划：每个平台一行，写清发布级别、文件、标题和公开范围或时间。
  3. 取得逐平台授权：用户确认哪些平台、按哪一级执行。
  4. 执行：一次处理一个平台。登录失效、验证码、短信验证、风控提示或界面异常时立即停止，交给用户接管，不重试绕过。
  5. 回读核对：上传后打开后台或草稿，核对标题、封面、描述前两行、字幕、公开范围和定时时间。
  6. 记录结果：把发布级别、执行时间、核对结果写回任务卡和发布矩阵。用户报告公开成功后，再记录公开链接。
  1. Verify the publishing package: Check the video file, aspect ratio, duration, cover, subtitles, title, description, hashtags, attribution, and AI disclosure fields for each platform. Report every missing item.
  2. List the execution plan: Provide one line for each platform, including the publishing level, file, title, and visibility or scheduled time.
  3. Obtain per-platform authorization: Have the user confirm which platforms to publish to and the level at which each should be executed.
  4. Execute: Process one platform at a time. If the login expires, a verification code or SMS verification is required, a risk-control warning appears, or the interface behaves abnormally, stop immediately and hand control to the user. Do not retry in an attempt to bypass the issue.
  5. Perform read-back verification: After uploading, open the backend or draft and verify the title, cover, first two lines of the description, subtitles, visibility, and scheduled time.
  6. Record the results: Write the publishing level, execution time, and verification results back to the task card and publishing matrix. Record the public link only after the user reports that the content has been published successfully.

安全边界

Safety Boundaries

  • 不一键群发，不在未授权的平台上执行任何写操作。
  • 不自动点赞、评论、关注、私信，不刷量。
  • Cookie、Token、OAuth 凭据和账号密码只由用户本人或上传工具保存在本机；不读取、不回显，不写入任务卡、日志、发布包或仓库。
  • 不代用户输入密码或验证码；登录由用户本人完成。
  • 不为躲避版权识别而改变速、加噪音或裁切画面。
  • 平台要求 AI 生成或合成内容声明时，如实勾选。
  • Do not mass-publish with one click or perform write operations on any platform without authorization.
  • Do not automatically like, comment, follow, send direct messages, or artificially inflate engagement.
  • Cookies, Tokens, OAuth credentials, and account passwords must be stored locally only by the user or upload tool. Do not read or echo them, and do not write them to task cards, logs, publishing packages, or repositories.
  • Do not enter passwords or verification codes on the user's behalf. The user must complete the login personally.
  • Do not alter the speed, add noise, or crop footage to evade copyright detection.
  • If a platform requires an AI-generated or synthetic-content declaration, select it accurately and truthfully.

输出

Output

返回每个平台的：发布级别、使用的适配器、上传或填表结果、公开范围或定时时间、回读核对结果、需要用户在后台完成的动作。未执行的平台写明原因（未授权、无适配器、风控停止），并附上该平台的手动发布包路径。
可使用 video-publish-pack-template.md 生成逐平台手动发布包。
For each platform, return the publishing level, adapter used, upload or form-filling result, visibility or scheduled time, read-back verification result, and any actions the user still needs to complete in the backend. For platforms that were not processed, state the reason, such as lack of authorization, no available adapter, or stopping due to risk controls, and provide the path to that platform's manual publishing package.
Use video-publish-pack-template.md to generate a per-platform manual publishing package.