Watch the film and trace the handoffs
The Second Interview is a 4:14 fictional thriller about a crypto exchange whose promise of security unravels after it goes public. The YouTube cut combines two episodes with English and Simplified Chinese subtitles. Episode 2 begins at 2:09. The film and the production skill are linked below.
Multiple Grok Bots collaborated in Kivo Studio, Seedance 2.5 generated the footage, and Codex handled the final edit, sound mix and bilingual subtitles. The steps below turn that division of work into a workflow you can try with one scene.
1. Connect Kivo and give each Bot an output
Open the Production Skill on GitHub and keep SKILL.md and MCP_CONFIG.md together as your team’s playbook. Follow the Grok Bot connection guide to add Kivo’s remote MCP server and authorize the project in the browser. Have the platform Bot check project access, available models and current limits before any paid task.
Give the writer the versioned script and dialogue, the director the shot list and take decisions, the scene Bot the character and location references, the platform Bot the quotes and generation log, and the editor the timeline and delivery. The director can also own storyboards and prompt versions, or delegate them to a separate Bot. Pick one owner per editable artifact. Parallelize independent shots once the shared script and look are locked.
2. Lock the scene before writing shot prompts
Start with one 15–30 second scene. The writer freezes the dialogue and the director defines what the audience must understand at each cut. The scene Bot saves approved reference views in the project and records wardrobe, prop placement, eyelines, camera axis and lighting direction. Name those references consistently and bind them to each saved video prompt.
For a practice scene inspired by the film, introduce an interview room in a wide shot, cut to a close-up as the interviewee hesitates, then cut to a hand turning a phone face down. Keep the same table, wardrobe and light direction across the three shots. If a specific number or message must appear on the phone, composite it in the edit.
3. Hand off shot records, then compare Drafts
In a shared project log, give each shot an ID, an owner, a target duration, a prompt version and a review status. Ask the platform Bot to quote one or two Draft candidates per test shot and wait for the payer’s approval before submitting. Build a rough sequence that tests dialogue, geography and at least one cut. Review it with sound. A take that looks fine alone can reverse the eyeline or cut off a reply.
The director records a main take and, if useful, a backup. Record the selected Draft job and output asset in the shot log so the editor can match the exact take. Here is a starter message for the director Bot. The shot labels are examples.
Direct a three-shot interview scene. Assign the writer, scene, platform and editor Bots their deliverables. Use shot IDs S01–S03 and log each owner, prompt version and approval. Prepare the prompts and request a Draft quote. Pause for budget approval before submitting any jobs.
4. Upgrade approved takes and check the cut
For Seedance 2.5 production in Kivo, quote the upgrade from the selected, still-valid Draft and confirm the new charge. The platform Bot can submit and track approved jobs and keep their IDs for reconciliation. If a submission times out, look up the existing job before retrying. The editor replaces the approved Drafts on the timeline and checks each cut again.
Play the sequence with headphones. Check lip sync against visible speech, then listen for missing room tone, abrupt levels and drift across cuts. Align the subtitle master to the final edit and preview both languages on a small screen. Keep a clean master, timed subtitles and a brief delivery log. Use the same handoff process on the next scene once the first sequence passes review.