Produce a Tech Explainer Video
First, read the root AGENTS.md — it is the sole overarching rule for production. This skill provides the technical steps.
- Read template.md to confirm the style and capability boundaries. When resuming a task, first read task-state.md and check the root work/task.json along with actual files.
- Only when starting production, run
python3 .agents/skills/make-video/scripts/pipeline.py init --install. It copies the real project, preserves any existing modifications, and generates programmatic sound effects. If no theme is provided, gather requirements first — do not treat the default example as the user's final video. - In
work/project/content.json, replace text, metrics, annotations, news, code, and covers shot by shot. Scenes can be reordered, duplicated, or their duration changed; configuration is validated against the real Zod schema and timeline constraints. If a new visual subject exceeds existing scenes, modify the current src rather than just changing the title. For parameter and media operations, see remotion.md. - Store raw assets in work/input; place derived assets actually used in work/project/public and refer to them with relative paths. Add voiceover, sound effects, and subtitles as needed; use default programmatic sound effects — no TTS or auto-alignment. First verify the voiceover semantics, then arrange the timeline.
- Run
validate,check,preview --frames 0-59, and check each scene's start/middle/end frames along with any audio clips; adjust clip ranges if necessary. Then runrenderandverify. Technical reports will not claim audio-visual approval. - Actually inspect keyframes, transitions, the final video, and the three covers; listen to the audio preview; then record acceptance and task status according to the root rules. Re-render relevant deliverables after modifications.
- Default deliverables are
work/delivery/video.mp4,cover-4x3.png,cover-3x4.png, andcover-16x9.png. If the user requests a different manifest, first align task.deliverables with actual rendering capabilities.
When maintaining the template, modify assets/project-template and use isolated tests from the root tests directory; do not run the root init for maintenance. See readme-format.md for the template metadata protocol.