Video Note Writer
Overview
Turn evidence into a tutorial-style Markdown note, not just a plain summary. The target output is a titled Markdown study note with clear structure, simple explanations, chapter images, optional formulas or tables, and explicit separation between "video said this" and "external expansion".
Workflow
- Read all input artifacts first:
- video title and URL
sectioned.md
subtitles.json or another raw subtitle file
- keyframe images and timestamps, if already provided
- optional web search results
- Determine the exact video title and use it as the output filename stem.
Display name stays as the true video title even if the filesystem filename must be sanitized.
- Build an evidence map before drafting:
- subtitle evidence
- keyframe evidence
- external-source evidence
- unresolved items
- If chapter keyframes are missing or insufficient, note the gap before drafting.
For each chapter, choose one main timestamp that best represents the teaching point of that section.
If formulas, tables, diagrams, maps, or slides appear, optionally choose one additional figure timestamp for that chapter.
- Consume frame artifacts that already exist.
If a chapter is missing a useful screenshot, continue writing the note and leave an image placeholder or omit the image line.
- Draft the note in tutorial layers:
- what the video is saying
- what that means in simple language
- why it matters
- how a beginner should understand it
- what to be careful not to misunderstand
- Only use web research when you need:
- extra background knowledge
- formula verification
- table completion
- terminology clarification
- fact checking
- Keep "video content" and "external expansion" separate.
External facts must never be presented as if they were said in the video.
- If formulas or tables appear, write them in Markdown only when they are reliable.
If they are incomplete or ambiguous, mark them as
pending-review.
- Run a final multi-check pass:
- factual consistency
- chapter/image alignment
- image evidence quality
- formula/table reliability
- source boundary
- tutorial clarity
- Markdown rendering safety
If the required evidence artifacts are missing, stop and call the evidence layer first instead of inventing content.
Hard Rules
- Output one Markdown file body unless the user explicitly asks for extra artifacts.
- Default filename rule: use the video title as the file stem and apply the note suffix shown in the output template reference.
- Prioritize clarity over polish.
- Use short paragraphs, short sentences, and direct explanations.
- Avoid unexplained jargon. If a term is necessary, explain it the first time it appears.
- Every important conclusion should be attributable to subtitles, keyframes, external sources, or be explicitly marked as uncertain.
- Do not invent formulas, tables, dates, names, values, or causal explanations.
- If extra knowledge is added, make it obvious that it is external expansion.
- If image paths are provided or generated by the evidence layer, use standard Markdown image syntax.
- Prefer one main image per chapter, placed directly under the chapter heading.
- If a formula/table/diagram needs its own image, place that image inside the "Formula and Table" or equivalent visual subsection, not at random.
- If formulas are used, use
$...$ or $$...$$.
- If tables are used, use standard Markdown tables.
- Do not silently fetch subtitles or screenshots from the source platform inside this skill. Consume existing artifacts or clearly state that evidence is missing.
Teaching Bias
When the evidence allows it, prefer notes that feel like a beginner tutorial:
- start each chapter with "what this section is teaching"
- explain "why it matters"
- give a plain-language version
- if possible, add one intuitive example or analogy
- point out one common misunderstanding or likely confusion point
Do not force examples or analogies when the evidence is too weak.
References
- Read references/prompt-blueprint.md for the recommended master prompt.
- Read references/output-template.md for the target note structure.
- Read references/keyframe-selection.md for how to pick and place screenshots.
- Read references/verification-checklist.md for the final multi-check pass.
1---2name: video-note-writer3description: Write a checked Markdown study note from existing video evidence such as `sectioned.md`, `subtitles.json`, and optional `frames/*.png`. Use when Codex already has subtitle and screenshot artifacts and needs a tutorial-style note, chapter summary, study guide, or beginner-friendly Markdown writeup without re-running the evidence collection layer.4---56# Video Note Writer78## Overview910Turn evidence into a tutorial-style Markdown note, not just a plain summary. The target output is a titled Markdown study note with clear structure, simple explanations, chapter images, optional formulas or tables, and explicit separation between "video said this" and "external expansion".1112## Workflow13141. Read all input artifacts first:15 - video title and URL16 - `sectioned.md`17 - `subtitles.json` or another raw subtitle file18 - keyframe images and timestamps, if already provided19 - optional web search results202. Determine the exact video title and use it as the output filename stem.21 Display name stays as the true video title even if the filesystem filename must be sanitized.223. Build an evidence map before drafting:23 - subtitle evidence24 - keyframe evidence25 - external-source evidence26 - unresolved items274. If chapter keyframes are missing or insufficient, note the gap before drafting.28 For each chapter, choose one main timestamp that best represents the teaching point of that section.29 If formulas, tables, diagrams, maps, or slides appear, optionally choose one additional figure timestamp for that chapter.305. Consume frame artifacts that already exist.31 If a chapter is missing a useful screenshot, continue writing the note and leave an image placeholder or omit the image line.326. Draft the note in tutorial layers:33 - what the video is saying34 - what that means in simple language35 - why it matters36 - how a beginner should understand it37 - what to be careful not to misunderstand387. Only use web research when you need:39 - extra background knowledge40 - formula verification41 - table completion42 - terminology clarification43 - fact checking448. Keep "video content" and "external expansion" separate.45 External facts must never be presented as if they were said in the video.469. If formulas or tables appear, write them in Markdown only when they are reliable.47 If they are incomplete or ambiguous, mark them as `pending-review`.4810. Run a final multi-check pass:4950- factual consistency51- chapter/image alignment52- image evidence quality53- formula/table reliability54- source boundary55- tutorial clarity56- Markdown rendering safety5758If the required evidence artifacts are missing, stop and call the evidence layer first instead of inventing content.5960## Hard Rules6162- Output one Markdown file body unless the user explicitly asks for extra artifacts.63- Default filename rule: use the video title as the file stem and apply the note suffix shown in the output template reference.64- Prioritize clarity over polish.65- Use short paragraphs, short sentences, and direct explanations.66- Avoid unexplained jargon. If a term is necessary, explain it the first time it appears.67- Every important conclusion should be attributable to subtitles, keyframes, external sources, or be explicitly marked as uncertain.68- Do not invent formulas, tables, dates, names, values, or causal explanations.69- If extra knowledge is added, make it obvious that it is external expansion.70- If image paths are provided or generated by the evidence layer, use standard Markdown image syntax.71- Prefer one main image per chapter, placed directly under the chapter heading.72- If a formula/table/diagram needs its own image, place that image inside the "Formula and Table" or equivalent visual subsection, not at random.73- If formulas are used, use `$...$` or `$$...$$`.74- If tables are used, use standard Markdown tables.75- Do not silently fetch subtitles or screenshots from the source platform inside this skill. Consume existing artifacts or clearly state that evidence is missing.7677## Teaching Bias7879When the evidence allows it, prefer notes that feel like a beginner tutorial:8081- start each chapter with "what this section is teaching"82- explain "why it matters"83- give a plain-language version84- if possible, add one intuitive example or analogy85- point out one common misunderstanding or likely confusion point8687Do not force examples or analogies when the evidence is too weak.8889## References9091- Read [references/prompt-blueprint.md](references/prompt-blueprint.md) for the recommended master prompt.92- Read [references/output-template.md](references/output-template.md) for the target note structure.93- Read [references/keyframe-selection.md](references/keyframe-selection.md) for how to pick and place screenshots.94- Read [references/verification-checklist.md](references/verification-checklist.md) for the final multi-check pass.