What this prompt does
This prompt uses Gemini's video understanding to analyze a [video_type] video and turn it into reusable content. It produces an executive summary of [summary_length] words, timestamped chapter markers, key takeaways and action items, explanations of technical concepts mentioned, accurate transcription of any code snippets shown, the questions the video answers, a [content_format] for blog or documentation repurposing, an SEO-optimized title and description for [platform], social posts (a Twitter thread and a LinkedIn post), and follow-up topics. It concentrates on your [focus_areas] and captures step-by-step processes from any demos.
The structure works because watching every minute of a talk or tutorial to extract its value is slow. Gemini gives you timestamps, transcripts, and takeaways you can edit down fast, turning one recording into a blog post, docs, and social content. The explicit "transcribe code accurately" and [focus_areas] instructions keep the output grounded, though technical claims and code still need a fact-check before anything is published.
When to use it
- You want to repurpose a technical talk or tutorial into a blog post or docs.
- You need timestamped chapters and a summary instead of rewatching the whole video.
- You want code snippets shown on screen transcribed rather than paused and retyped.
- You're producing social posts (Twitter thread, LinkedIn) from a single recording.
- You need an SEO-friendly title and description for
[platform]. - You want follow-up topics and the questions a video answers for content planning.
Example output
Expect a structured breakdown: a [summary_length]-word executive summary, timestamped chapter markers, takeaways and action items, explanations of technical concepts, transcribed code, the questions answered, a [content_format] draft ready to edit, an SEO title and description for [platform], and ready-to-post social copy. Demos are captured as step-by-step sequences so a reader can follow the process without the video.
Pro tips
- Always fact-check the technical claims and any transcribed code before publishing; video understanding can mishear terms or garble a snippet shown briefly.
- Set
[summary_length]to the use — a tight summary for a teaser, a longer one if it's becoming the article's backbone. - Point
[focus_areas]at what you actually care about (technical accuracy, practical steps) so the output emphasizes that over filler. - Choose
[content_format]to match the destination — a Markdown blog post with code blocks differs from documentation, and saying so improves the draft. - Treat the SEO title and description for
[platform]as candidates to refine, not final copy, since the model can't see your live ranking data. - Use the timestamped chapters to jump back to the source video and verify anything the summary makes you uncertain about.
