The user wants structure pulled out of a watched video — "make chapters for this video", "where does the bug appear in this recording", "turn this screen recording into a bug report", "how strong is my intro/hook".
The user wants structure pulled out of a watched video — "make chapters for this video", "where does the bug appear in this recording", "turn this screen recording into a bug report", "how strong is my intro/hook".
Use this for deterministic extraction from the index — chapters with timestamps, a fileable bug report with the exact frame, or a scored hook analysis.
Similar popular skills
Related neighbors and high-traction skills in the same topics — useful to compare before installing.
Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.
Claude CodeNot declared
CursorNot declared
CodexNot declared
GitHub CopilotNot declared
WindsurfNot declared
Gemini CLINot declared
ClineNot declared
OpenCodeNot declared
Repository health
Stars340
LicenseLICENSE
Default branchmain
Open issues0
Status
Active
Skill metadata
Parsed from SKILL.md frontmatter.
Version1.4.0
LicenseMIT
Allowed toolsBash, Read
Package contents
Files included with this skill beyond the listing page.
skill mdSKILL.md1,976 B
docsSUMMARY.md398 B
History
First seen on skills.sh
First recorded snapshot · 249 installs
SKILL.md
Extracting structure
Three extractors turn an already-watched video into something structured. All of them answer straight from the persistent index — deterministic, no extra model calls. The video must be watched first (see watching-videos).
Chapters
watch-skill extract chapters <video_id-or-source>
Titled chapters with start/end timestamps, built from scene changes plus transcript topic shifts. Good for long tutorials, lectures, meetings — give the user the chapter list with timestamps, not a prose summary.
Pinpoints where an error appears: timestamp, the exact frame, the on-screen error text as OCR read it, and the steps that led up to it (from the transcript/actions preceding the failure). Returns found: false honestly when no error signal exists — report that as "no error found in the recording", not as an error.
Paste the output into the user's issue tracker format when they ask for a fileable report; the frame path is the attachment.
Scores the opening seconds on four measured axes — attention trigger in the opening line, speech pacing, visual change rate, on-screen text — each with an actionable critique, plus a 0–100 score and verdict. Give the user the per-axis critiques; the number alone helps nobody.