videodb
Installation
SKILL.md
VideoDB: setup and the Python SDK
VideoDB runs video work on its servers: ingest, understand, index, search, clip, subtitle, compose, stream. This skill covers setup and the Python SDK. Five smaller skills cover the common jobs and should be used first when they match:
| Job | Skill |
|---|---|
| Find a moment, ask a video, count what appears | video-search |
| Clips, highlight reels, vertical cuts, MP4s | video-clips |
| Transcripts, subtitles, translation | video-subtitles |
| Music, overlays, captions, compositions | video-edit |
| Cameras, live streams, meetings, screen capture | video-live |
Which path
- VideoDB connector tools present (names such as
upload_media,search_video,generate_clip): use them. This is the path in Claude chat on web, desktop and mobile, and in Cowork. No install, no API key. - No VideoDB tools, but you have a shell (Claude Code, Cowork, any agent that can run Python): ask for the VideoDB API key in one friendly line (free at https://console.videodb.io, $20 of credits, no card). When the user gives it, save it yourself to the project's
.env(Setup, below), never print it, and continue with the SDK. In Claude Code,/mcpthen authorizing the bundled videodb server also works. - No VideoDB tools and no shell: you are in Claude chat. Reply with only this, adapted to the request: "VideoDB isn't connected yet. Open Settings → Connectors, find VideoDB, click Connect and log in (free, no card). Then send this request again and I'll take it from there." Do not mention API keys,
.env, shells, Claude Code or/mcphere; none of them apply in chat, and a key pasted into chat cannot be used because nothing runs code there.
The SDK path is also the only path for code, scripts, notebooks, desktop capture, AI generation, dubbing and sandbox compute, which the connector does not do. Talking to the user: never write "index", "indexed" or "indexing" in a reply; say "searchable".