| name | Demo Generator |
| description | Generate Onto2AI demo manifests, presentation-style review videos, and future screen-recording demo skeletons. |
Demo Generator Instructions
Use this skill when the user wants to create, regenerate, or standardize Onto2AI demo production files.
Standard Demo Model
The current standard is the introduction demo:
- script-driven
- manifest-first
- presentation-rendered
- narrated with OpenAI
cedar
- final review video under
demo/video/review/
Use demo/README4DEMO as the workflow overview and demo/introduction/README.md as the reference implementation notes.
Canonical Tool
- Script:
demo/introduction/generate_introduction_video.py
- Durable script:
demo/introduction/introduction-script.md
- Manifest output:
demo/video/introduction/introduction_demo.json
- Narration output:
demo/video/introduction/introduction_narration.txt
- Audio output:
demo/audio/onto2ai_introduction_cedar.mp3
- Video output:
demo/video/review/onto2ai_introduction_template.mp4
Regenerate The Introduction Demo
Reuse the existing OpenAI cedar narration:
python3 demo/introduction/generate_introduction_video.py
Refresh the OpenAI cedar narration and rebuild the video:
python3 demo/introduction/generate_introduction_video.py --refresh-audio
Keep scratch frames and segment files for debugging:
python3 demo/introduction/generate_introduction_video.py --keep-work
Manifest Contract
Every generated demo should have exactly one canonical manifest at:
demo/video/<demo_name>/<demo_name>_demo.json
The manifest must carry:
narrative_lines[].text is authoritative narration content.narrative_lines[].start_ms / end_ms are authoritative timing values.slides[] or scene records define what is rendered.output_audio points to the narration artifact.output_video points to the review/final video artifact.
Avoid parallel script, timing, and scene files that can drift away from the manifest. It is fine to keep a long-form source script under the relevant demo source folder, but the generator must derive the production narration from the manifest.
Presentation-Style Demo Rules
- Keep durable source files under
demo/<demo_name>/.
- Keep generated narration under
demo/audio/.
- Keep the manifest and derived narration under
demo/video/<demo_name>/.
- Keep final review videos under
demo/video/review/.
- Write temporary rendered frames and video segments to the system temp directory.
- Verify final MP4 output with
ffprobe.
- For the introduction demo, expected output is
1280x720, 30fps, H.264 video, AAC audio.
Future Screen-Recording Demos
For UI walkthroughs based on raw recordings, follow the same file contract:
- raw recording:
demo/video/<demo_name>/<demo_name>.mov
- manifest:
demo/video/<demo_name>/<demo_name>_demo.json
- narration:
demo/audio/<demo_name>_cedar.mp3
- final review export:
demo/video/review/<demo_name>_synced_with_voice.mp4
When creating a new screen-recording demo, build the manifest first, then derive narration audio and mux it into the recording. Do not depend on the old recording-only helper pattern; the manifest-first workflow is now the standard path.
Preconditions
ffmpeg and ffprobe are required for video assembly and verification.OPENAI_API_KEY and network access are required only when refreshing TTS audio.- Node.js is required for the introduction deck renderer.
