Tous les Skills / OXBSHW

oxbshw/watch-skill

configuring-vision

The user wants to connect an LLM or vision provider, already has an API key, asks "can I use OpenAI/Anthropic/Gemini/OpenRouter", wants local Ollama, or needs different cheap and strong models.

Document Skill original

Rendu depuis le dépôt source en conservant titres, exemples, code, tableaux, liens et images.

Configuring vision

Watch Skill's agent surface and model backend are separate choices. Claude Code, Codex, Cursor, OpenClaw, framework agents, and REST clients all call the same engine; the engine can send selected frames to any supported vision provider.

Supported providers

bash

watch-skill setup-vision --provider anthropic --api-key <KEY>
watch-skill setup-vision --provider openai --api-key <KEY>
watch-skill setup-vision --provider gemini --api-key <KEY>
watch-skill setup-vision --provider openrouter --api-key <KEY>
watch-skill setup-vision --provider ollama

Prefer a key the user already has. Do not claim Ollama is required, and do not ask the user to reveal a secret in chat. They can set the matching environment variable or run the command privately in their terminal.

Route bulk work and verification separately

One model can serve both tiers:

bash

watch-skill setup-vision --provider openai --api-key <KEY> --model <vision-model>

Or use a cheaper model for scene descriptions and a stronger model for uncertain answers and loop critiques:

bash

watch-skill setup-vision --provider openrouter --api-key <KEY> \
  --cheap-model <fast-vision-model> --strong-model <strong-vision-model>

Add --verify to make one live probe call. If it fails, report the structured error and its fix; never echo the key.

No provider is also valid

Without a vision API, Watch Skill still acquires video, reads captions, runs local transcription and OCR, indexes evidence, and searches it. Visual synthesis degrades to timestamped evidence instead of guessing.

du même dépôt

Autres Skills

Tous les Skills

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 appears", "what happens at 2:30", "does the video show Y". Use this to answer from the persistent index with timestamped evidence and a confidence score instead of re-watching or guessing.

installations: 1
GitHub Stars: 380
Mis à jour: 14 sept.

Voir les détails →

extracting-structure

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.

installations: 1
GitHub Stars: 380
Mis à jour: 14 sept.

Voir les détails →

the-loop

The user built or changed something visual — a UI, an animation, a game, a generated video — and wants it verified, or asks "why does my UI look wrong", "check that the fix actually worked", "does the animation glitch". Use this to record the running thing, critique the recording against plain-language pass criteria, and iterate until it passes with before/after proof.

installations: 1
GitHub Stars: 380
Mis à jour: 14 sept.

Voir les détails →

watching-videos

The user shared a video URL, a YouTube/TikTok/stream link, a local video file, a screen recording, a meeting recording, or a playlist/folder of videos — "watch this", "summarize this video", "what's in this recording". Use this to actually watch the video — download, extract frames, OCR, transcribe, and index it — instead of guessing from the title or asking the user to describe it.

installations: 1
GitHub Stars: 380
Mis à jour: 14 sept.

Voir les détails →