Team Learning Goal
Teach video as evidence-rich prompt material, not as a novelty or transcript shortcut.
By the end of this section, the room should understand:
- why video can carry context text drops
- when video is worth the overhead
- how
oracle-videorelates tooracle-packx - why Gemini browser mode is required for video
- how source hashes,
ffprobe, timestamps, keyframes, andoutput.logmake analysis checkable - why transcript, chat, visual evidence, and inference must stay separate
- how verified video analysis becomes prompts, bugs, requirements, QA, lessons, or Section 6 variation matrices
Walkthrough Depth
Essential Walkthrough
- Say: video is prompt material.
- Show the short path vs long path table.
- Show the correct Oracle/Gemini call shape.
- Show
shasum,ffprobe, andEND_OF_VIDEO_ANALYSIS. - Show evidence lanes.
- End with downstream prompt examples.
Expanded Walkthrough
Add:
- run folder shape
yt-dlpmetadata/download flow- keyframes/contact sheet
- omissions pass
- bug repro prompt shape
Deep-Dive Walkthrough
Add:
- chunking long recordings
- requirements artifact
- Section 6 variation matrix from video evidence
- exercises
Talking Points
Opening:
Video is prompt material.
On transcripts:
A transcript tells you what was said. It does not prove what was visible.
On evidence lanes:
Spoken claims, visible facts, chat messages, and inferences do different jobs. Keep them separate.
On Gemini:
Text models do not watch the video. The video-watching step belongs to Gemini through Oracle browser mode.
On source preservation:
If the original media is not preserved, every later claim gets harder to trust.
On Section 8:
Section 7 preserves evidence from video. Section 8 puts that same discipline inside live debugging with markers.
Live Demo Script
1. Create Run Folder
RUN_ID="checkout-repro"
RUN_DIR="runs/$RUN_ID"
mkdir -p "$RUN_DIR"/{inputs,receipts,analysis,final,keyframes,contact-sheets}
mkdir -p "$RUN_DIR/chunks/01"
2. Preserve Source
cp /path/to/source-video.mp4 "$RUN_DIR/inputs/source-video.mp4"
shasum -a 256 "$RUN_DIR/inputs/source-video.mp4" \
> "$RUN_DIR/inputs/source-video.sha256"
ffprobe -hide_banner -show_format -show_streams -of json \
"$RUN_DIR/inputs/source-video.mp4" \
> "$RUN_DIR/receipts/ffprobe.source.json"
3. Write Prompt With Sentinel
cat > "$RUN_DIR/chunks/01/gemini-prompt.md" <<'EOF'
Analyze this video as prompt material for a software project.
Separate transcript evidence, chat evidence, visual evidence, and inference.
Preserve timestamps.
Do not invent URLs, tools, commands, files, UI labels, or speakers.
End with END_OF_VIDEO_ANALYSIS.
END_OF_VIDEO_ANALYSIS
EOF
4. Show Correct Call Shape
mcp__oracle__consult({
prompt: "[checkout-repro-video]\n\n{contents of chunks/01/gemini-prompt.md}",
files: ["/absolute/path/to/runs/checkout-repro/chunks/01/chunk.mp4"],
engine: "browser",
model: "gemini-3-pro",
browserAttachments: "always",
slug: "checkout-repro-video"
})
5. Verify Output
rg -n "END_OF_VIDEO_ANALYSIS" ~/.oracle/sessions/checkout-repro-video/output.log
6. Bridge To Downstream Work
Show one of:
- repro steps
- implementation prompt
- design-change brief
- QA checklist
- Section 6 variation matrix
Minimal Useful Path
If 5 minutes behind, cut:
yt-dlp- contact sheet command
- long recording folder details
- omissions pass prompt
Preserve:
- video is prompt material
- Gemini browser mode
browserAttachments: "always"- source hash
ffprobe- evidence lanes
- sentinel
- downstream prompt
If 15 minutes behind, run only:
source -> hash -> ffprobe -> Gemini browser mode -> evidence lanes -> verified downstream prompt
Boundaries
From Section 6
Section 6 teaches:
one deliberate prompt -> controlled variations
Section 7 expands what can become prompt material:
video -> verified evidence -> downstream prompt or variation matrix
To Section 8
Section 8 moves the same discipline into live debugging:
mark -> capture -> explain -> review/export
Failure Paths To Preserve
Wrong Oracle mode:
If video analysis used API mode, rerun in browser mode.
Transcript-only summary:
Ask for visual evidence and an omissions pass. Do not treat transcript as full analysis.
Invented URL/tool/file:
Remove it or label it as inference. Unsupported details cannot become requirements.
No sentinel:
Inspect
output.log. If the sentinel is missing, rerun or request a focused correction.
No source hash:
Stop and preserve the source before continuing.
Long recording not chunked:
Segment/chunk before asking for a full packet.
Team Checklist
Confirm the materials include:
video is prompt material
oracle-video
Gemini
engine: "browser"
model: "gemini-3-pro"
browserAttachments: "always"
absolute file paths
yt-dlp
ffprobe
sha256
source hash
original timestamps
END_OF_VIDEO_ANALYSIS
output.log
keyframes
contact sheets
transcript evidence
chat evidence
visual evidence
inference
omissions pass
no invented URLs/tools/commands/files
bug reproduction
design feedback
app walkthrough
requirements
QA checklist
implementation prompt
Section 6 variation matrix
Section 8 agent markers bridge
Further References
- team-facing file:
cheatsheets/07-video-as-prompts.md - Exercises:
exercises/07-video-as-prompts.md oracle-videoskill reference:.agents/skills/oracle-video/SKILL.mdyt-dlp: https://github.com/yt-dlp/yt-dlp- FFmpeg documentation: https://ffmpeg.org/documentation.html
ffprobedocumentation: https://ffmpeg.org/ffprobe.html