How do I install the Video Digest Segment skill?

Run npx skillmds@latest add simonlee2/video-digest-segment in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Video Digest Segment safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Video Digest Segment?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Video Digest Segment free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Video Digest Segment?

simonlee2 (@simonlee2) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Video Digest Segment by simonlee2 — Agent Skill

Name: Video Digest Segment
Author: simonlee2

Video Digest Segment

Segment a long multi-talk video (conference stream, all-day recording) into individual talks by reading its transcript timeline - produces talks.json for the video-digest pipeline. Stage 2; skip for single-talk videos (video-digest-ingest's vd_single.py handles those). Use when a digest source video contains multiple talks/sessions.

simonlee2 fcb1439 2 files · 4.4 KB Updated Sep 17, 2026

File contents

video-digest-segment

LLM stage — no scripts. Input: <item_dir>/transcript/timeline_30s.txt (from ingest). Output: <item_dir>/talks.json.

This is the fragile stage — read this before running

A single pass over a braided feed (stream cutting between stages, re-shows, MC filler) drops real talks. Always run the verification pass below.

Procedure

If an authoritative schedule exists (conference program page, description chapters, chapters.txt), save it to <item_dir>/schedule.txt — titles/speakers/times in order. It's reconciliation ground truth. No schedule → derive talks purely from content.
Run the segmentation prompt: references/segment-prompt.md (fill {ITEM_DIR}, {CONTEXT}, paste schedule facts). One agent for the whole stream.
VERIFY (mandatory): walk the schedule (or the talk list you produced) in order; for EACH expected talk, grep transcript/transcript.tsv for the speaker's self-intro or a distinctive title phrase and confirm a matching entry exists in talks.json. A scheduled talk braided with cutaways must still appear (kind main/talk) even if windows overlap. Timestamps drift — trust transcript CONTENT over scheduled clock times.
Sanity-check output: talks ordered by start; start/end "HH:MM:SS"; leading applause trimmed; kinds valid.

talks.json schema

{"talks":[{"id":1,"start":"00:12:30","end":"00:31:05","slug":"kebab-slug",
  "title":"...","speaker":"Name · Org","kind":"main",
  "official_time":"9:15am|","confidence":"high|med|low","note":"self-intro quote / ambiguity"}]}

kinds: main/keynote (headline), fireside, track/talk (regular), cutaway (feed cut to other content — excluded from digest), nonspeech (excluded). Exclude pure breaks/pre-roll entirely; dedupe re-shows.

---name: video-digest-segmentdescription: Segment a long multi-talk video (conference stream, all-day recording) into individual talks by reading its transcript timeline - produces talks.json for the video-digest pipeline. Stage 2; skip for single-talk videos (video-digest-ingest's vd_single.py handles those). Use when a digest source video contains multiple talks/sessions.---# video-digest-segmentLLM stage — no scripts. Input: `<item_dir>/transcript/timeline_30s.txt` (from ingest). Output: `<item_dir>/talks.json`.## This is the fragile stage — read this before runningA single pass over a braided feed (stream cutting between stages, re-shows, MC filler) **drops real talks**. Always run the verification pass below.## Procedure1. If an authoritative schedule exists (conference program page, description chapters, `chapters.txt`), save it to `<item_dir>/schedule.txt` — titles/speakers/times in order. It's reconciliation ground truth. No schedule → derive talks purely from content.2. Run the segmentation prompt: `references/segment-prompt.md` (fill `{ITEM_DIR}`, `{CONTEXT}`, paste schedule facts). One agent for the whole stream.3. **VERIFY (mandatory)**: walk the schedule (or the talk list you produced) in order; for EACH expected talk, grep `transcript/transcript.tsv` for the speaker's self-intro or a distinctive title phrase and confirm a matching entry exists in talks.json. A scheduled talk braided with cutaways must still appear (kind main/talk) even if windows overlap. Timestamps drift — trust transcript CONTENT over scheduled clock times.4. Sanity-check output: talks ordered by start; `start`/`end` "HH:MM:SS"; leading applause trimmed; kinds valid.## talks.json schema```json{"talks":[{"id":1,"start":"00:12:30","end":"00:31:05","slug":"kebab-slug", "title":"...","speaker":"Name · Org","kind":"main", "official_time":"9:15am|","confidence":"high|med|low","note":"self-intro quote / ambiguity"}]}```kinds: `main`/`keynote` (headline), `fireside`, `track`/`talk` (regular), `cutaway` (feed cut to other content — excluded from digest), `nonspeech` (excluded). Exclude pure breaks/pre-roll entirely; dedupe re-shows.

Frequently asked questions