3D Cinematic Titles — ChatCut Desktop Skill setup

This plain text version is returned because this request does not look like a browser page navigation.
Browser page: https://pr-824-preview.chatcut.dev/zh-hant/skills/3d-cinematic-titles

Full installation guide:

# 3D Cinematic Titles — create an editable title with ChatCut

The user wants to use ChatCut's 3D Cinematic Titles Skill. Keep the title text, duration, format, material, mood, reference images or other brief they already gave. Finish setup before asking once for anything still missing. If they have given no creative brief, ask for the exact title text and the look they want; do not invent a project just to demonstrate installation.

This Skill is currently published to the beta catalog. Production availability and the public fresh-install journey are pending. The standard production installer does not prove access to this beta Skill. Continue only with an existing beta connection that can read this exact Skill. Do not install or switch the user's app/channel/catalog to bypass that gate.

## 1. Connect ChatCut Desktop

If this conversation exposes local `chatcut_desktop` tools, call `get_active_project` first. A result with `surface: "desktop"` means the app is installed and connected, even if `projectId` is null. Continue to step 2 without reinstalling.

If local Desktop tools are absent, explain that public setup for this beta Skill is pending and preserve the user's title request. The [ChatCut Desktop installation guide](https://pr-824-preview.chatcut.dev/desktop) describes the standard production app; do not run it as a claimed way to obtain this beta Skill. A hosted Web connector is a different execution surface; it is not proof that Desktop is connected.

## 2. Load the title workflow

The Workflow Skill is 3D Cinematic Titles, catalog ID `9fe33a39-4272-44c6-bb37-e3cb1adca02e`. Load it with `chatcut_desktop.manage_skill` and use it in this conversation; do not start a new one for it.

- If the tool's action list offers `install` (Desktop offers it to Codex), call it with `{"action":"install","agentSkillId":"9fe33a39-4272-44c6-bb37-e3cb1adca02e"}`. Desktop saves the complete Skill in this agent's own Skill folder, so later conversations find it by name. The receipt can say `nativeDiscovery: pending`: this conversation listed its Skills before the install. Read `SKILL.md` in the receipt's `directory` now and follow it; its references and scripts are in the same folder.
- If this host does not support the `install` action, call `{"action":"get","agentSkillId":"9fe33a39-4272-44c6-bb37-e3cb1adca02e"}` and follow the returned `SKILL.md`. Its other files come back with it; save a script to a working folder before running it.

If the call says the Skill is not available or requires a newer Desktop, report the actual error and follow this page's availability instructions. Do not infer which catalog the app uses from its hostname, switch the user's channel, or substitute a different Skill.

For any other error, tell the user the actual error. Do not substitute a similarly named Skill or copy one from elsewhere.

## 3. Make the title from the user's brief

Follow the returned Workflow Skill, including the current bundled Motion Graphics instructions it references, with the user's title and creative brief. That current package owns the authoring, verification and export process. Reuse the user's text, logo and reference assets. Ask only for missing information that affects the result; do not create a project merely to prove setup works.