Installs into .claude/skills of the current project.
Are you the author of Openmontage Avatar Spokesperson Publish Director?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/wanfeng1028-openmontage-avatar-spokesperson-publish-director)
---
name: openmontage-avatar-spokesperson-publish-director
version: "1.0.0"
description: 数字人口播流水线的发布总监技能,负责把成片与各衍生版本清晰打包并附上信息导向的元数据。适用于需要区分主剪、竖版方版衍生、多语言版本与审核版本的交付环节。
metadata:
license: AGPL-3.0
---
# Publish Director - Avatar Spokesperson Pipeline
## When To Use
Package the finished spokesperson outputs for delivery. This stage should make it obvious which file is the hero cut, which are derivatives, and what message or audience each version serves.
## Process
### 1. Label Deliverables Clearly
Distinguish:
- hero cut,
- vertical cutdown,
- square cutdown,
- language variants,
- watermark or review versions.
### 2. Keep Metadata Message-Led
Recommended metadata keys:
- `audience_segment`
- `cta_copy`
- `offer_name`
- `locale`
- `thumbnail_concept`
### 3. Package Review Notes
If the avatar path has limitations such as visible lip-sync risk, retain that note in the package instead of hiding it.
### 4. Quality Gate
- exports are clearly named,
- metadata matches the intended message,
- poster frame or thumbnail concept features the presenter cleanly,
- review notes stay attached to the package.
## Common Pitfalls
- Mixing hero and derivative exports without clear naming.
- Reusing generic metadata that ignores the spokesperson offer.
- Dropping risk notes that matter for downstream publishing teams.
---
## Gate Reminder (Binding)
This stage gates on human approval (`human_approval_default: true`). After review passes:
checkpoint with `status="awaiting_human"`, present the summary (the Backlot board renders
the artifact), and **END YOUR TURN**. Do not start the next stage in the same response.
Approval is per-gate — an earlier "go ahead" does not cover this gate.