asking-with-evidence
The user asks a question about a video that was already watched or indexed — "what did they say about X", "what error code…
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
$ npx -y skills add oxbshw/watch-skill --skill extracting-structure --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/extracting-structureContext preview
The summary Claude sees to decide when to auto-load this skill.
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
name: extracting-structure version: "1.4.3" description: 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. license: MIT user-invocable: true allowed-tools: Bash, Read
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`).
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.
watch-skill extract bug-report <video_id-or-source>
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.
watch-skill extract hook <video_id-or-source> [--seconds 15]
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.
Give AI agents eyes, ears, and verifiable results. Watch Skill turns video, audio and screen activity into searchable, timestamped evidence, and answers did that actually work? with a deterministic contract rather than a model's opinion.
The user asks a question about a video that was already watched or indexed — "what did they say about X", "what error code…
The user wants to connect an LLM or vision provider, already has an API key, asks "can I use OpenAI/Anthropic/Gemini/OpenRouter",…
The user corrected an answer about a video — "no, it actually says X", "that's the wrong timestamp", "you misread the error code"…
A Watch Skill command failed, video download broke, ffmpeg or yt-dlp is missing, a provider returned an error, local vision…
The user wants to share or hand off what was found in a video — "send this analysis to my team", "make a page I can share",…