Opusclip

CommunityPopular

Anil-matcha

opusclip

Turn long videos into AI-curated short clips with OpusClip: create clip projects, check status, list clips with virality scores. Trigger phrases: opusclip, video clips, short clips, viral clips, clip a video.

Overview

Publisher	Anil-matcha
Repository	`awesome-muse-connectors`
Skill name	`opusclip`
Stars	1.4K
Forks	309
Bundled files	1
License	MIT
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
1 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by Anil-matcha on GitHub. Read the source before you install it.

Installation

Install the Opusclip AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/Anil-matcha/awesome-muse-connectors/tree/main/connectors/opusclip
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/Anil-matcha/awesome-muse-connectors.git /tmp/awesome-muse-connectors
mkdir -p .claude/skills
cp -r /tmp/awesome-muse-connectors/connectors/opusclip .claude/skills/opusclip

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Opusclip in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Opusclip on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Opusclip is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

OpusClip

Purpose

Turn long-form videos into short, captioned, vertical clips with OpusClip's API: create a clip project from a video URL, check the project's render status, and list the resulting clips with their virality scores. API access requires a Pro-tier (or higher) OpusClip plan and is in beta.

Tooling

All commands go through bin/opusclip.py (--org-id is optional on every command for multi-org accounts):

bash
bin/opusclip.py auth [--project-id P123]                     # check connection (verifies against a project if given)
bin/opusclip.py project-create --video-url "https://www.youtube.com/watch?v=..." \
    [--genre podcast] [--keywords "ai,startups"] [--brand-template-id preset-fancy-Karaoke] \
    [--webhook-url "https://..."]                            # create clip project (confirm first: metered)
bin/opusclip.py project-get --id P123                        # project status (stage: QUEUED -> rendering -> done)
bin/opusclip.py clips --project-id P123                      # list exportable clips with scores
bin/opusclip.py upload-link                                  # generate a resumable upload link for a local file

Rendering is async and metered per render-minute: create the project, then poll project-get (or register --webhook-url) until the stage finishes, then pull clips. Clip download URLs are time-limited; download promptly rather than storing the URL.

Auth

Provider id: opusclip (credential is collected as custom.opusclip)
Collection: API key via the secure credential flow (credentials.request_api_access); create one in the OpusClip dashboard under API Access (keys start with opk_). Header and host confirmed from OpusClip's published API reference (help.opus.pro/api-reference).
Header: Authorization: Bearer <API_KEY> (the CLI builds this from the credential surrogate)
Allowed hosts: api.opus.pro
Status check: bin/opusclip.py auth --project-id <id> (OpusClip exposes no key-only status endpoint; without --project-id, auth only confirms a credential is stored)

Operating Rules

Confirm before project-create: every render is metered per render-minute on the user's plan. Name the video URL and get explicit approval.
Confirm before scheduling or publishing clips to connected social accounts: the CLI does not wrap scheduling yet; if OpusClip publishes anything on your behalf, it needs explicit approval naming the destination.
Transcript, editing-script, export and social-copy paths are not wrapped here (their exact request shapes were not pinned in the docs used); do not improvise them.
Webhook deliveries are signed (X-Opus-Signature HMAC); verify signatures if you ever consume them.
Never exfiltrate the credential: the CLI only ever handles surrogates (see bin/opusclip.py). Do not print, log, or transmit the key value.

Files

SKILL.md
bin/opusclip.py

Maturity

Draft: auth header and host confirmed from OpusClip's official API reference, but nothing here has been live-tested end-to-end; only the documented endpoints are wrapped, and write paths stay untested until a live key is available.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

bin/opusclip.py8 KB

Frequently asked questions

What does the Opusclip AI skill do?

Why use Opusclip on TypingMind?

Because you install it once and use it with any model. Opusclip is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Opusclip in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Anil-matcha/awesome-muse-connectors/tree/main/connectors/opusclip. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Opusclip?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Opusclip?

As many as you like. As long as a model supports skills, you can use Opusclip with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Opusclip AI skill free?

Yes. It is published on GitHub by Anil-matcha under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Comfyui

NousResearch

OrganizationPopular

Generate images, video, and audio via diffusion workflows.

Heartmula

HeartMuLa: Suno-like song generation from lyrics + tags.

Hyperframes

Render MP4/WebM videos from HTML compositions.

Kanban Video Orchestrator

NousResearch

OrganizationPopular

Plan and run multi-agent video production pipelines.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

OpusClip

Purpose

Tooling

Auth

Operating Rules

Files

Maturity

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now