Creator Publish Package

View saved version →

---
name: creator-publish-package
description: Create a platform-native publishing package for any user-selected combination of YouTube, Bilibili, and REDnote from a video script supplied as a Markdown file or Notion page plus one clean base cover image. Use when a creator asks to package, publish, or adapt a video across one or more of these platforms, including titles, descriptions or posts, tags, and platform-specific covers.
---

# Creator Publish Package

Generate a complete multi-platform publishing package from a video script and clean base cover image. Understand the content once, then adapt the title, copy, and cover to each platform instead of copying or merely translating one package.

## Inputs

Require exactly two primary inputs: one script source and one cover image.

```text
script.md OR a Notion page/link
cover.png
```

Accept an optional platform selection containing any combination of `YouTube`, `Bilibili`, and `REDnote`. Generate only the selected platforms. If the user does not specify platforms, default to all three. Never require the user to select all three.

```text
Platforms: YouTube, REDnote
```

Accept the script as either a local/uploaded `script.md` file or an accessible Notion page or link. For Notion input, retrieve and read the complete page content, including relevant headings, lists, callouts, and child content that forms part of the script. If the page cannot be accessed, ask the user to connect Notion, grant access, or paste/upload the script; do not continue from a partial preview.

Treat the retrieved script content as the source of truth. It may contain Chinese, English, mixed language, headings, timestamps, or notes. Read it in full. Never invent claims, experiences, numbers, results, credentials, experiments, time periods, or conclusions unsupported by the script.

Treat `cover.png` as the visual source of truth. It may contain the creator, product UI, screenshots, a background, an existing composition, or negative space.

If either primary input is missing, ask the user to provide it before producing the package.

### Preserve portraits

If the base cover contains the creator's real face, extract the creator once from the original image as a transparent-background portrait, preserving the original face, hair, clothing, pose, and visible body pixels. Reuse this exact same portrait cutout across all selected platforms. Do not separately regenerate, redraw, beautify, relight, reshape, or reinterpret the creator for each platform.

Use generative AI only for non-person elements such as the background, product UI, supporting imagery, lighting outside the portrait, depth, and graphic accents. Assemble each final cover by deterministically compositing the shared portrait cutout onto the platform-specific generated design. This keeps the creator identical across all selected covers while allowing native layouts and backgrounds.

The transparent portrait is an internal working asset. Do not include it in the final publishing package unless the user explicitly requests it.

Allowed edits include brightness, contrast, hierarchy, text, arrows, icons, highlights, glow, shadow, simple graphics, emphasis on existing UI or screenshots, and extension or modification of non-person background areas. Keep the creator recognizable as the person in the original.

## Final output

Create `publish.md` plus one cover image for each selected platform. For example, when all three platforms are selected:

```text
publish-package/
├── publish.md
├── youtube.png
├── bilibili.png
└── rednote.png
```

Omit images for unselected platforms, and omit their sections from `publish.md`. Do not include separate title, description, tag, analysis, prompt, or metadata files unless explicitly requested. Temporary working files may be used internally but must not appear in the final package.

## Workflow

### 1. Understand the content

Read the entire script before generating titles or covers. Internally identify the main topic,

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 4 — file references are metadata, not package contents.