Kai root note: knowledge/, harness/, and scripts/ paths in this skill live in the Kai install, not the user's project. Resolve them against the first ancestor directory of this SKILL.md that contains a knowledge/ folder (the Kai plugin root, ~/.claude/kai, or the kai-cmo-harness repo). MARKETING.md, memory/, and any output files live in the current project. If a referenced scripts/ command is not available in this install, say so, skip it, and continue with the file-based guidance — never fabricate its output.

Motion Spot

Build studio-grade product video from code: one HTML page where every style is a pure function of time, rendered frame by frame, with a real score cut to the picture. Real UI, real screenshots, a real drop on the reveal.

Load before starting: harness/references/motion-spot-method.md (formats, page contract, score, render fixes, taste rules, watch-back QA). When the video is being sold, also load harness/references/motion-spot-service-playbook.md. When anything will be posted, load harness/references/social-automation-rules.md and the platform's harness/references/*-organic-posting-rules.md.

Engine: scripts/motion_spot/ in the Kai root. Run every script from the video project folder (workspace/video/<slug>/ in the current project) with the Kai root's path, e.g. KAI=<kai-root>/scripts/motion_spot; python "$KAI/render.py". Requirements: Python 3.10+, pip install playwright numpy scipy pillow then playwright install chromium, and ffmpeg with libx264 and libvpx-vp9.

Keys come from the environment only: ELEVENLABS_API_KEY (music) and, for publishing, UPLOAD_POST_API_KEY. Never print them, paste them into chat, or write them into a project file.

Phase 1: Brief and beat sheet

1. Read MARKETING.md. Pin down the product and its one-line promise, the format (launch spot, walkthrough set or pain-point set), 3-5 real moments to show, one accent color and the tone preset. Ask only if the product itself is unknown.
2. List what is live, what is publicly on the roadmap, and what nobody claims. Show only the first two, and list roadmap claims in the report. Never invent stats, customers or testimonials.
3. Write the beat sheet on the 120 BPM grid (2 s bars, 0.5 s beats) before any code. Every cut goes on a downbeat, every UI hit on a beat, and the drop on the reveal at 4.0 s. Each bar has to answer "why is this here?"
4. Apply the readability budget: at least 0.3 s settled per word for any line meant to be read. Stats and lists stack and stay.
5. For pain-point sets, start from the customer's own words for each pain. The first frame names the adversary.