video-use

You point the agent at a folder of raw takes; the skill has ElevenLabs Scribe transcribe each source at word level and condenses the result into a phrase-level text file, so the model reads the footage as text and pulls up filmstrip-and-waveform images only at tricky cut points. Once you approve a plain-English cut plan, it writes an edit decision list, renders each segment with an optional color grade and short audio fades, joins them, and adds overlay animations and burned-in subtitles last; sub-agents build the animations in parallel with HyperFrames, Remotion, Manim or PIL. Before showing a preview it inspects every cut boundary and the audio levels, then logs the session in project.md; its notes on music and sound effects cover ducking under speech and loudness normalization. Cuts follow speech and silence, so it fits talking heads, tutorials, interviews and montages better than scripted scenes, and it needs ffmpeg, Python dependencies and an ElevenLabs API key.

• 01From the README

  The install command quoted from the repository README.

  $ git clone https://github.com/browser-use/video-use ~/Developer/video-use ln -sfn ~/Developer/video-use ~/.claude/skills/video-useCopy

• 02skills CLI, for Claude Code, Codex and others

  The open skills CLI from Vercel Labs installs a skill from a GitHub repo into the folder each agent expects. It asks which skills and which agents you want, and it installs for the current project unless you add the -g flag, which installs for your user account. Add --list to see what a repo contains before you install anything.

  $ npx skills add browser-use/video-useCopy

• 03Claude Code, skills folder

  Copy the skill's folder, the one that holds SKILL.md, into ~/.claude/skills/ to use it in every project on your machine, or into .claude/skills/ in a repository to use it there and share it by committing it. Claude Code picks up changes to these folders during a session. If the folder did not exist when the session started, run /reload-skills.

• 04Claude Code, plugin marketplace

  Some repos publish a plugin marketplace, a .claude-plugin/marketplace.json file. Add it in Claude Code, then install a plugin from it with /plugin install plugin-name@marketplace-name. Plugins can bundle hooks and MCP servers along with skills, so read the details panel before you confirm.

  $ /plugin marketplace add browser-use/video-useCopy

• 05Codex, skills folder or $skill-installer

  Codex reads skills from .agents/skills in your working folder and its parent folders up to the repository root, and from $HOME/.agents/skills for every repository. Copy the skill's folder into one of them, or run $skill-installer inside Codex and ask it to install from the repo. Codex detects new skills automatically and needs a restart only if one does not appear.

The first command is quoted from the author's README. The others are the standard ways to install a skill from a GitHub repository. They are templates and may not apply here, for example if the repo has no plugin marketplace, so follow the README first.