- name
SKILL.md
स्किल फ़ाइल पब्लिशर की रिपॉज़िटरी में ही रहती है।
कॉपी की गई कमांड टर्मिनल में पेस्ट करें। यह इस SKILL.md को उस एजेंट में इंस्टॉल करती है।
npx skills add oxbshw/watch-skill --skill watch -a cursor -yकॉपी की गई कमांड टर्मिनल में पेस्ट करें। यह इस SKILL.md को उस एजेंट में इंस्टॉल करती है।
npx skills add oxbshw/watch-skill --skill watch -a claude-code -yकॉपी की गई कमांड टर्मिनल में पेस्ट करें। यह इस SKILL.md को उस एजेंट में इंस्टॉल करती है।
npx skills add oxbshw/watch-skill --skill watch -a codex -yकॉपी की गई कमांड टर्मिनल में पेस्ट करें। यह इस SKILL.md को उस एजेंट में इंस्टॉल करती है।
npx skills add oxbshw/watch-skill --skill watch -a grok -yकॉपी किया गया संदेश Grok Bot चैट में भेजें। Bot यह SKILL.md GitHub से लाता है और उसे उन स्किल में जोड़ देता है जो आपके सभी Bot साझा करते हैं।
Install this skill: https://github.com/oxbshw/watch-skill/tree/HEAD/skills/watchपब्लिशर से
You don't have a video input; this skill gives you one. It is a thin wrapper
around the watch-skill CLI — all logic lives in the engine, so this skill
works identically on every harness (Claude Code, Codex, Cursor, ...).
This is a drop-in upgrade of the classic claude-video /watch skill:
same invocation shape, plus a persistent index (ask answers follow-ups
without re-processing), OCR on frames, scene-aware sampling with perceptual
dedup, local Whisper (offline by default, no API key needed), and THE LOOP
(capture -> critique -> fix -> re-capture) for iterating on your own output.
watch-skill doctor --json
fix. doctor
auto-bootstraps ffmpeg and yt-dlp into a managed bin dir on Windows/macOS/
Linux; re-run once after it reports fixes. Only involve the user when a
check still fails after remediation.watch-skill itself is not on PATH: pip install watch-skill (or
uv tool install watch-skill), then re-run the doctor.No API key is required for acquisition, transcription, OCR, indexing, or
search: transcription falls back to local faster-whisper. Visual synthesis
and verification can use the user's existing Anthropic, OpenAI, Gemini, or
OpenRouter key, or an optional local Ollama model. The agent and provider are
independent; see the configuring-vision skill. Cloud STT is opt-in
(--cloud-stt) and only ever uploads extracted mono audio — the video file
never leaves the machine.
Parse the user input into source + optional question, then:
watch-skill watch "<source>" [--start T --end T] [--max-frames N] [--transcript-only]
--duration 60 bounds live streams), and local files all work.--start / --end (SS, MM:SS, HH:MM:SS) switch to dense focused
sampling of that window — use for "what happens at 2:30?" questions and for
any video over ~10 minutes when the user cares about one section.--timestamps T1,T2,... pins frames at transcript-flagged moments
("look here", "as you can see") that visual selection may miss.--transcript-only skips frames entirely (fastest; no video download when
captions exist).--max-frames N tightens the token budget (default: duration-tiered,
hard cap 100, max 2 fps).The report prints an Indexed: video_id ... line, frames with t=MM:SS
timestamps, OCR text, and the transcript.
Read every frame path the report lists, in a single message (parallel Read calls), so you see them together in chronological order.
Answer from frames + OCR + transcript, citing timestamps. No question → summarize structure, key moments, notable visuals, spoken content.
The video is already indexed. For any follow-up question in this or a LATER session:
watch-skill ask <video_id> "<question>" # self-healing answer + evidence
watch-skill search "<phrase>" # across every video ever watched
ask (v0.6) answers text-first with timestamped evidence, a confidence
score, and a ~N tokens saved line. It escalates on its own when unsure
(dense re-sampling, zoom-crop re-OCR) and states plainly when the video
does not clearly show the answer — trust that refusal; do NOT invent an
answer past it. Frame paths are listed only when the engine wants you to
look yourself (or pass --frames); Read them then. Never re-run watch
for a follow-up on an already-indexed video.
If the user corrects one of your video answers, report it so the system learns (locally):
watch-skill lessons add <video_id> "<question>" "<your wrong answer>" "<the correction>"
When the user asks you to fix UI/visual output and verify the fix:
watch-skill loop start "<url-or-screen:-or-file>" "<pass criteria>" [--script '<json steps>']
# ... you apply the suggested fixes ...
watch-skill loop iterate <loop_id>
The critique returns structured issues with timestamps and suggested fixes.
YOU change the code; the loop only observes. On pass it renders a
before/after MP4+GIF proof. watch-skill capture "<target>" records without
critiquing.
--cloud-stt..env; they are never logged or echoed.~/.watch-skill/cache (LRU, size-capped).Watch any video (URL, stream, or local path) via Watch Skill. Downloads, extracts scene-aware deduped frames, OCRs them, transcribes (captions first, then local Whisper — offline by default), indexes
---name: watchdescription: Watch any video (URL, stream, or local path) via Watch Skill. Downloads, extracts scene-aware deduped frames…---# skills/watch/SKILL.mdओवरव्यू
Watch any video (URL, stream, or local path) via Watch Skill. Downloads, extracts scene-aware deduped frames, OCRs them, transcribes (captions first, then local Whisper — offline by default), indexes everything, and hands the result to the agent. Follow-up questions are answered from the persistent index without re-processing.
FAQ
पब्लिशर से skills/watch/SKILL.md डाउनलोड करें, या पाथ कॉपी करके रिपॉज़िटरी खोलें। PlugMCP स्किल को सूचीबद्ध करता है, फ़ाइल होस्ट नहीं करता।
पब्लिशर इसे https://github.com/oxbshw/watch-skill पर रखता है।
Claude, Cursor, Codex और Grok Build वह SKILL.md पढ़ सकते हैं जिसे आप पब्लिशर की रिपॉज़िटरी से जोड़ते हैं। जब आप चैट में स्किल के GitHub फ़ोल्डर का लिंक भेजते हैं, तो Grok Bot उसे इंस्टॉल कर देता है।