- name
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add oxbshw/watch-skill --skill video-memory -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add oxbshw/watch-skill --skill video-memory -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add oxbshw/watch-skill --skill video-memory -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add oxbshw/watch-skill --skill video-memory -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/oxbshw/watch-skill/tree/HEAD/skills/video-memoryFrom the publisher
Every video ever watched on this machine is still here — frames, OCR,
transcripts, and past answers, in one persistent index under
~/.watch-skill/. You never have to say "I don't remember that video."
Sessions don't expire it; watching more videos makes it more useful.
watch-skill list
Every indexed video: id, title, duration, when it was analyzed. Check here before watching anything — it may already be in memory from a previous session.
watch-skill search "<phrase or keywords>"
Hybrid keyword + semantic search across every video, any language (Arabic folding, CJK and Thai segmentation are handled). Hits come back with video + timestamp; follow up on a hit with:
watch-skill ask <video_id> "<the user's actual question>"
watch-skill ask <video_id> "what is on screen at <timestamp>?"
"What did we decide about the pricing page across those meetings?" — questions no single video answers go to the library synthesizer:
watch-skill library ask "<the question>"
It answers from distilled notes across every indexed video, drills into
real evidence, and cites video + timestamp for each finding. When it
says the library does not clearly answer, trust that — do not stitch a
guess together from weak search hits. watch-skill library overview
shows what the library knows (videos, note counts, entities recurring
across videos).
For "which video showed X" (locate, not synthesize), plain search is
the right tool; then ask the hit video.
A playlist or a folder of recordings goes in as one call —
watch-skill batch "<playlist-or-folder>" — and the whole set becomes
searchable memory (see watching-videos).
The user asks about videos watched in the past or across sessions — "have we watched anything about X", "which video showed that error", "what did that meeting decide", "search my videos", or a questi
---name: video-memorydescription: The user asks about videos watched in the past or across sessions — "have we watched anything about X", "which…---# skills/video-memory/SKILL.mdOverview
The user asks about videos watched in the past or across sessions — "have we watched anything about X", "which video showed that error", "what did that meeting decide", "search my videos", or a question that spans several videos. Use this to search and answer from the persistent cross-video index instead of saying you don't remember.
FAQ
Download skills/video-memory/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/oxbshw/watch-skill.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.