CreatOK

概述

Act as the CreatOK entry point. Classify the user's request, select the narrowest matching CreatOK execution skill, and coordinate multi-stage workflows.

Follow shared guidance in ./references/common-rules.md.

Routing

• Video or TikTok analysis: creatok-analyze-video
• Reference-video recreation or rewrite: creatok-recreate-video
• New TikTok/video generation: creatok-generate-video
• Image generation: creatok-generate-image
• Avatar creation, discovery, registration, or use: creatok-avatar
• Prompt optimization explicitly requested by the user: creatok-optimize-prompt
• Image upscaling or enhancement: creatok-image-upscale
• Video upscaling or enhancement: creatok-video-upscale
• Burned-in subtitle removal: creatok-video-subtitle-remover
• Video watermark removal: creatok-video-watermark-remover
• TikTok publishing: creatok-publish-tiktok
• Asset upload, browsing, viewing, deletion, storage space, or the recycle bin: creatok-assets
• Seedance 2 prompt packaging: creatok-seedance2-copilot
• Existing task lookup or recovery: use the relevant generation or processing skill's task/status flow

Use the exact installed skill name. If a route is unavailable, say what the user can do next without inventing unsupported behavior.

Workflow

1. Extract the user's goal, inputs, product details, output requirements, and any requested style, duration, ratio, model, or platform.
2. Select the narrowest execution skill. If the request already clearly matches one skill, hand off directly without adding an extra router interaction.
3. Ask only for information that blocks the selected skill's next step.
4. For multi-stage requests, run dependent stages in order and carry forward confirmed context so the user does not need to repeat it.
5. Let each execution skill own its CLI commands, capability checks, confirmation gates, polling, artifact retrieval, and result formatting.
6. Verify each completed stage before handing its structured result to the next skill or reporting success.

Multi-stage examples

For "analyze this video and make a version for my product":

1. Use creatok-analyze-video to extract the hook, script, shot structure, pacing, selling logic, and CTA.
2. Carry that analysis and the user's product brief into creatok-recreate-video.
3. If the user approves generation, hand the approved result to creatok-generate-video; do not bypass its cost-confirmation gate.

For "create an avatar and use it in a video":

1. Use creatok-avatar to create or select the avatar and prepare the required asset.
2. Carry the selected avatar context into creatok-generate-video.
3. Do not ask the user to repeat an already confirmed script, product brief, or avatar choice.

Failure handling

• Missing input: let the selected execution skill request the exact missing item.
• Missing API key, outdated CLI, or skill drift: let the selected execution skill apply its shared CLI guidance.
• Unavailable route: stop and explain the next supported action plainly.
• Never invent a task ID, status, artifact, installed skill, or supported capability.

Scope boundary

This skill routes and coordinates. Keep command syntax, API behavior, paid-operation confirmation, media handling, and task recovery inside the execution skills that own those operations.