opus-skills

A skill marketplace for OpusClip — adds video clipping, social posting, and more to your AI coding agent. The existing OpusClip package contains three skills: opusclip for clipping and publishing through the bundled API CLI; copy-video-style for reference-driven local editing, with optional OpusClip MCP video understanding; and opusclip-media-generation for generating voiceovers, music and short video clips through OpusClip MCP.

BETA — features and pricing are subject to change. API pricing may diverge from web pricing.

Install

**Install OpusClip: **

Point your agent at the repo above and ask it to install the skill — most agents can fetch, zip, and wire it up from a URL. If yours needs a specific command, use the per-host shortcuts below.

For the clipping CLI, export your key (from , Enterprise, Pro, or Max plan required) in the shell that launches your agent:

export OPUSCLIP_API_KEY=sk_...

curl and jq must be on PATH for the clipping CLI. Its optional storyboard, trim, and preview commands need ffmpeg. Copy Video Style needs a local renderer such as FFmpeg; styled captions need an FFmpeg build with libass and freetype (on macOS, Homebrew ffmpeg-full, which is keg-only, so the skill calls it by its full path), and linked references need yt-dlp.

What’s in the box

• skills/opusclip/SKILL.md — when and how to call OpusClip. Triggers on “clip this video”, “make shorts”, “post to YouTube”, etc.
• skills/opusclip/scripts/opusclip — bash CLI wrapping the OpusClip REST API + ffmpeg local utilities.
• skills/opusclip/references/api-reference.md — endpoint schemas, request/response shapes.
• skills/opusclip/skills/copy-video-style/SKILL.md — reference-driven local editing, with optional video understanding through OpusClip MCP.
• skills/opusclip/skills/opusclip-media-generation/SKILL.md — voiceover, music and video generation through OpusClip MCP, with a quote and your approval before each paid call.

Copy Video Style

Copy Video Style is a separate skill inside the existing OpusClip package, alongside the opusclip clipping skill and opusclip-media-generation. All three share one package installation; no additional plugin or marketplace is needed. Give your agent your footage and a reference video or link. It scans the reference’s frames, cuts and loudness locally, shows you what defines the style, and asks once which elements to copy, whether to add OpusClip video understanding for a few credits, and where any missing music or other assets should come from. Then it creates and reviews the video locally. It does not require an OpusClip editor project.

Install or update the OpusClip package using the installation methods above. To install the skills directly (Node.js and the agent must be available):

npx --yes skills add opus-pro/opus-skills --skill opusclip copy-video-style opusclip-media-generation --agent codex --global --yes
# For Claude Code, replace codex with claude-code.

Connect MCP separately:

# Codex CLI/App
codex mcp add opusclip --url https://mcp.opus.pro/mcp
codex mcp login opusclip

# Claude Code
claude mcp add --transport http --scope user opusclip https://mcp.opus.pro/mcp
# Open Claude Code and run /mcp to authenticate OpusClip.

Complete OAuth sign-in and select your organization in the agent’s connection flow. An API key for the existing clipping CLI does not authenticate this MCP connection. Restart the agent session after installing. Video understanding is optional and uses OpusClip credits; local editing uses your agent and local tools. The connected backend and account must expose opusclip_analyze_reference_media. If you choose understanding and authentication is required or expired, the agent should help you sign in and retry. If understanding stays unavailable, the agent explains the blocker and continues from its local scan, noting that sound and music were not analyzed.

Anonymous usage events. The skill’s scripts/telemetry.mjs sends two events to OpusClip per run: run_started after the local scan (whether preflight passed, which tool was missing, file or link reference) and delivered each time the agent hands over a video (feedback rounds, output length bucket, aspect ratio, the chosen elements, whether you chose understanding, the generation budget and whether OpusClip generated assets). Both carry a random run ID, the skill version, the agent’s name and a random install ID kept in ~/.opusclip/telemetry.json. When you used OpusClip understanding, delivered also sends that job’s ID, which links the run to the analysis on your OpusClip account. It never sends file paths, file names, URLs, prompts, captions, transcripts or media, and your IP address is not stored. It is off in CI and with NODE_ENV=development; turn it off anywhere with OPUSCLIP_NO_TELEMETRY=1, DO_NOT_TRACK=1 or node /scripts/telemetry.mjs disable.

Example request:

Use copy-video-style with my footage and this reference. Borrow its caption treatment, pacing and framing, keep my message intact, and deliver a local MP4 plus an editable project.

OpusClip Media Generation

opusclip-media-generation generates a voiceover or narration (Gemini 3.8 Flash TTS), a music track (Lyria 3.5) or, when your connected server offers it, a short video clip (MiniMax H3 or Seedance 2.5) through the OpusClip MCP connection above. Each generation uses OpusClip credits at a fixed price. The agent quotes every request for free first and runs nothing until you approve its cost, asks for a total when several generations are planned and gets your yes for the planned list, and records every job in generation.json. It gives you a playable link for every result, because the agent cannot listen or watch, then downloads and checks the files locally. copy-video-style hands off to it when you choose to generate missing music, voiceover or shots.

It ships in the same OpusClip package. The npx skills add command above installs it with the other two skills. Generation needs the MCP connection above and a plan with API access; the OpusClip connector in the claude.ai directory does not include it.

Example request:

Use opusclip-media-generation to make a 30-second instrumental bed for my product video: upbeat, light percussion, about 110 BPM, with a clear build at 0:15. Quote it before you run it.

Develop

git clone https://github.com/opus-pro/opus-skills.git
cd opus-skills
export OPUSCLIP_API_KEY=sk_...
skills/opusclip/scripts/opusclip project create --url "https://youtube.com/watch?v=..."
node --test   # tests in tests/

Contributing

CODEOWNERS lists current maintainers. Open a PR and a maintainer will review.

License

MIT — see LICENSE.