Viral Video Cloner — 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-758-preview.chatcut.dev/zh/viralvideocloner

Full installation guide:

# Viral Video Cloner — remake a video with ChatCut

Viral Video Cloner is a ChatCut skill that remakes an existing video (a viral trend, a UGC ad or a TV commercial) with the user's own people, products or places. It keeps the source's movement, camera work, timing and audio, and replaces only what the user asks for: motion transfer rebuilds the cast and scene from reference photos, and object swap changes only the people, products or outfits the user names while the rest of the shot stays as filmed. Each remake covers 4 to 30 seconds and uses ChatCut credits only after the user confirms the length and estimated cost. Product page: https://pr-758-preview.chatcut.dev/viralvideocloner. The steps below are for an AI agent setting this up for its user.

The user wants to install ChatCut Desktop and remake a video with ChatCut's Viral Video Cloner Skill. Their message may already give the source video (a link or a local file) and the photos or footage to use: the people, products or places to swap in, or their own footage to edit in the source's style, sometimes with other changes described in words. Keep whatever they gave through every step below and do not ask for it again. A bracketed placeholder left as written, such as `[video link or file]`, counts as not given. If the source video or what to swap in is missing, finish setup first, then ask for the missing items once, in one short message with examples: the video link or file, photos or footage of the person, product or place to swap in, and what to change in a sentence. Never pick a video yourself, and do not generate before the user replies.

The remake runs in the ChatCut Desktop app on the user's computer, which connects to this agent as the local MCP server `chatcut_desktop`. A hosted ChatCut Web connector or plugin is a different product with similarly named tools: do not use it for this, and leave it installed as it is.

## 1. Install and open ChatCut Desktop

If local Desktop tools are exposed, first call `get_active_project` from `chatcut_desktop`; agents list it as `get_active_project`, `chatcut_desktop.get_active_project` or `mcp__chatcut_desktop__get_active_project`. A result with `surface: "desktop"` means ChatCut is already installed and connected to this agent, even when `projectId` is null: go to step 2 without reinstalling.

If the tool is not there, install ChatCut now on this computer, normally the user's own, with the official command for it. This requires macOS 13+ or Windows x64 with a graphical desktop; Linux is not supported. If this agent cannot run commands on that computer, keep the request and explain how to continue in a local agent there instead. The command installs or updates ChatCut and opens it; no Node.js or npm is needed. Never build your own ChatCut app or web wrapper; if the installer cannot run, tell the user what failed.

macOS:

```sh
curl -fsSL https://pr-758-preview.chatcut.dev/install.sh | sh
```

Windows PowerShell:

```powershell
irm https://pr-758-preview.chatcut.dev/install.ps1 | iex
```

After installing and opening ChatCut, the standard shell or PowerShell script opens browser sign-in, then attempts local MCP and bundled Skill registration for supported installed agents through Desktop's own maintenance API. The user completes sign-in; the script does not wait for credentials or confirm authentication. Registration is best effort and time-limited; read the actual status in its output. Failed or skipped connection setup does not undo a successful installation, but it is not a ready connection. Do not use computer control, screenshots or UI clicks to connect MCP, or ask the user to click connection settings. If the installer reports an error, tell the user the actual error; the [ChatCut Desktop installation guide](https://pr-758-preview.chatcut.dev/desktop) covers errors and other agents. Also follow the optional installation handoff at the end of this page, if there is one.

Check this conversation's actual tools first. After successful registration, if tools are still absent, explain the host's supported reload action and carry the original request forward: Codex CLI and Claude Code may require exiting and reopening the agent session; a new or cleared conversation alone is not a verified reload. In the Codex desktop app, try a new conversation and verify its tools, asking for a restart only if needed. Show their original message word for word in a code block so they can resume it; the refreshed session picks up from step 1. Ask the user to sign in if ChatCut asks or `get_active_project` reports `signedIn: false`. Missing tools alone do not prove a sign-in issue; do not reinstall or automate connection clicks.

## 2. Load the matching Desktop Skill

For a remake that keeps the reference video's motion and timing, load Desktop's bundled `video-gen` Skill and inspect `submit_video_remake` on `chatcut_desktop`. These ship with Desktop; no separate marketplace installation is needed. Do not use a hosted Web generation tool instead. If the tool is missing, update Desktop using step 1, then recheck the live tool catalog.

If the user instead wants their own footage edited in the reference's style, or explicitly asks for the saved workflow below, load that Workflow Skill. Editing footage to match cuts and packaging does not require generatively remaking its pixels.

The optional Workflow Skill is Viral Video Cloner, catalog ID `e6bd8e47-5797-426f-ab0c-d7ea5c674078`. 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":"e6bd8e47-5797-426f-ab0c-d7ea5c674078"}`. 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.
- Otherwise, or when `install` is refused, call `{"action":"get","agentSkillId":"e6bd8e47-5797-426f-ab0c-d7ea5c674078"}` 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 on desktop or needs a newer Desktop, this ChatCut Desktop is older than the Skill requires. Tell the user so, then update it for them by running the installer from step 1 again ([ChatCut Desktop installation guide](https://pr-758-preview.chatcut.dev/desktop)); ChatCut must be closed first, so ask them to save their work and quit it if it is open. Projects and sign-in are kept. After the update, retry loading this Skill here; if it still reports the older Desktop, this conversation is holding the old connection, so continue in a new conversation as step 1 describes.

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

## 3. Start the remake

Follow the selected Skill from its first step with the user's video and changes. Decide the approach yourself and ask only for what is still missing.

Generative remakes need a ChatCut membership; editing existing footage may have different access requirements. After the user is signed in, use `chatcut_desktop.read_billing` or the available generation-quote tool to check current access and credits. A failed or unavailable check does not mean Free. Use current tool results rather than prices or plan names in the Skill.

If the signed-in user is not a member, explain that their remake needs membership and open `chatcut://billing` using this computer's URL-opening capability. Prefer a more specific Desktop billing link if a tool returned one. The same billing popup is at **profile/account row at the bottom-left of the Desktop sidebar → Upgrade**. Use that UI path if the link cannot open; if the app cannot be controlled, give those exact clicks. Let the user choose a plan and complete payment, then recheck access and continue with the video and references they already provided. Do not purchase a plan on their behalf without authorization. For an existing member who only needs more credits, use **Credits** in that menu (**Plan & credits** in Settings) and the available credit-purchase options instead of asking them to subscribe again.

When this agent submits a generation, ChatCut starts it at once and spends the user's credits; it shows no confirmation of its own. So before submitting, tell the user how long the result will be and roughly how many credits it will cost, and wait for their go-ahead. Do not create a project or start a generation just to show that setup works.