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://chatcut.io/es/viralvideocloner Full installation guide: # Viral Video Cloner — remake a video with ChatCut The user wants to 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. Check the Desktop connection This needs an agent running on the user's own computer, such as Codex or Claude Code. In a browser-only chat or a cloud sandbox, tell the user to open a local Codex or Claude Code session and send the same message there, then stop. If `chatcut_desktop` is available in this conversation, call its `get_active_project`. A result with `surface: "desktop"` means Desktop is connected, even when `projectId` is null. Go to step 2. ```text Tool: chatcut_desktop.get_active_project Connected: { "projectId": null, "surface": "desktop" } ``` If the tool is missing or the call fails, Desktop may be not installed, closed, signed out or not yet connected to this agent; a missing tool does not prove the app is absent. Follow the [ChatCut Desktop installation guide](https://chatcut.io/desktop). Its `app` command reuses an installed app and installs one only when none is found, and Desktop then connects this agent. Ask the user to sign in only when the app asks for it. Only in this case, also follow the installation handoff at the end of this page, if there is one. This conversation loaded its tools when it started, so it cannot use Desktop even after setup: do not rerun setup or keep trying to make the tools appear. When setup is done, tell the user to start a new conversation in this agent app and send their original message again, unchanged, and give them that message ready to copy. If a step failed, say which one, with the actual error, and what the user needs to do. Stop there; the new conversation picks up from step 1. ## 2. Load the Skill The 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 neither call returns the Skill, tell the user the actual error. Do not substitute a similarly named Skill or copy one from elsewhere. ## 3. Start the remake Follow the Skill from its first step with the user's video and changes. Decide the approach yourself and ask only for what is still missing. 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.