Gdc vtt to note
When the user provides a GDC VTT segment URL, run the bundled capture script to merge captions, then summarize and create an Obsidian note under gdc summary.From its SKILL.md
npx -y skills add ihybrd/my_ai_skills --skill gdc-vtt-to-noteAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
2.0 KB, 472 tokens by cl100k_base, as published. Nobody here has run it
GDC VTT To Note Skill
Purpose
Use this skill when a user wants to turn a GDC talk caption stream into:
- A merged caption file.
- A short structured summary.
- An Obsidian note in
literature notes/video notes/gdc/ai notes.
Trigger
- User provides a GDC caption
.vttsegment URL.
Required Input
- One GDC VTT segment URL, for example:
.../index_4_0_33.vtt
Do not
download the provided vtt file directly, instead, run the bundled script to process it and generate a caption file (captions.txt). Then read the generated caption file to create the summary and note.
Script Execution
run the script with the provided VTT segment URL. For example:
python3 gdc-vtt-to-note/scripts/capture_gdc_vtt.py $vtt_url_provided_by_user
Post-Processing Workflow
this section will be exectuted only when the script stops running and generates a caption file (captions.txt). If the script fails, report the error and do not proceed.
once the script successfully generates a caption file (captions.txt), do the following:
- Read the generated caption file.
- Build a concise summary including:
- Topic
- Key points
- Actionable insights
- Create an Obsidian note in
literature notes/video notes/gdc/ai notes.
Note Naming Rule
- Filename format:
YYYY-MM-DD-{summary_slug}.md - Slug rules:
- lowercase
- spaces ->
- - remove invalid filename characters
- If conflict exists, append
-2,-3, etc.
Note Content
Include:
- Title
- Source VTT URL
- Caption file path
- Summary sections
- Captions.txt full content as reference
Prefer frontmatter metadata:
source_vttcaption_filecreated_attags: [gdc, summary]
Safety
- If script execution fails, report stderr and do not create the note.
- If caption file is empty, create note with
incompletestatus. - Prefer absolute paths in command execution and output reporting.
What ships with it: 1 file
3.9 KB alongside SKILL.md, 1 of them executable
scripts/
- capture_gdc_vtt.pyruns3.9 KB