Remotion Captions
Guidance for captions and subtitles in Remotion videos: all captions are handled as JSON objects of the Caption type from @remotion/captions
- What
- Guidance for captions and subtitles in Remotion videos: all captions are handled as JSON objects of the Caption type from @remotion/captions
- Cost
- Free
- Needs
- Before you start: read this whole install prompt, tell me in a few lines what this skill does and what installing it involves, and wait for my go-ahead before you do anything else.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — Guidance for captions and subtitles in Remotion videos: all captions are handled as JSON objects of the Caption type from @remotion/captions, and the skill routes to its companion files for the three jobs — transcribing audio or video (Whisper running locally on the GPU through @remotion/whisper-webgpu, with a model download at use time), displaying and animating captions with the Basic Captions element, and importing existing .srt files. After the work, the SKILL.md sends the agent back to Remotion Best Practices and says to open Remotion Studio. It works on the user's own media in their own Remotion project; no licence was found anywhere in the upstream repository at the pinned commit — see the licence note on this listing. By @remotion-dev, listed here with credit to its creator. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Copy the install package below, then paste it into Muse📌 Pinned version: commit 6c67adcBefore you start: read this whole install prompt, tell me in a few lines what this skill does and what installing it involves, and wait for my go-ahead before you do anything else. Prerequisites — None to install this skill — no account, no key, no payment, and no executable code in its folder. At use time, in my own Remotion project: captions are handled as JSON Caption objects from @remotion/captions (that package is added to the project with npx remotion add), and transcribing runs Whisper locally on my GPU through @remotion/whisper-webgpu — it needs a compatible GPU and its script downloads a Whisper model. No licence was found anywhere in the upstream repository at the pinned commit, so no licence terms are stated for it. Install "Remotion Captions" for me. It gives the agent the Remotion way of working with captions and subtitles: every caption is a JSON object of the Caption type (text, startMs, endMs, timestampMs, confidence) from the @remotion/captions package, and the main file routes to three companion guides — transcribe-captions.md for generating captions from audio or video with Whisper WebGPU running locally, display-captions.md for showing them with the Basic Captions element (importing the @remotion/captions package first), and import-srt-captions.md for bringing in an existing .srt file — then sends the agent back to Remotion Best Practices and to open the Studio when the work is done. Its folder holds the main SKILL.md (frontmatter name remotion-captions), those three companion guides, its agents/openai.yaml policy file and its icon. Repository: https://github.com/remotion-dev/skills (the skill is the whole skills/remotion-captions/ folder at the pinned commit: SKILL.md plus 5 companion files, 6 files in total) Pinned version: install the code at commit 6c67adcd9cdbe6eb84d76342da89b225f9161cb2 exactly. Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Clone https://github.com/remotion-dev/skills into a temporary folder, check out commit 6c67adcd9cdbe6eb84d76342da89b225f9161cb2, and copy the skills/remotion-captions/ folder from that checkout. Then compare every file in the folder with the fingerprints recorded for this listing on 2026-10-22: [FINGERPRINTS] - SKILL.md: SHA-256 8d08dc238f3df6c6a4ed1aaa9c30bf5e4a5fde3fa4d248db29992b94f10d45ab - agents/openai.yaml: SHA-256 3b39a48bd00251cf124e80090fe1b792b73020bee858c5d48b5629256cc5f045 - assets/remotion-icon.svg: SHA-256 5007669bd0555b0f4565b4e7176fa191310ab0039b2ed09d867a9270f5b0ce58 - display-captions.md: SHA-256 12676a7250f33f126a8ccb0a2b28de22f5ccc9cad0d5baab53a736e205690a17 - import-srt-captions.md: SHA-256 e328b6845babd08ed2a747f82c59796fd1d7b85140c8eb4d36e41639779473ad - transcribe-captions.md: SHA-256 0830184ed1f634a6912536768a3aabc0092313db22796c4455e8b46dad874803 If a file does not match, it changed since the listing was prepared: do not install it yet, tell me what you found and let me decide. 2. Read SKILL.md in full, and tell me in plain words: what the skill does when used, what it connects to, whether it reads or sends any personal information or credentials, and anything that seems unusual. Stop on any red flag and tell me before going further. Confirm these points from the files: - The skill folder holds 6 files and no executable code: SKILL.md (frontmatter name remotion-captions), the three companion guides (transcribe-captions.md, display-captions.md, import-srt-captions.md), agents/openai.yaml and the assets icon (an SVG file). - Nothing is sent anywhere during installation itself; the only download at install time is the skill folder from GitHub at the pinned commit. None of my media or project files are read during installation. - At use time everything runs in my own Remotion project: captions are JSON Caption objects, transcription runs Whisper locally on my GPU (downloading a Whisper model), and the @remotion/captions package is added to my project with npx remotion add. No credentials are read and no media of mine is sent to any service by the procedures described. - The licence point from the prerequisites is part of the picture: no licence was found anywhere in the upstream repository at the pinned commit, so do not present this skill as MIT, Apache or open source. - Do not transcribe, add any package, open Studio, and do not use the skill in any way during this install: using it is a separate step that only starts when I ask for caption work later. 3. When I say "yes, install", install it as a skill: copy the whole remotion-captions folder into the agent's skills directory, in a folder named exactly "remotion-captions", keeping its 6 files in their original relative layout (SKILL.md at its root). 4. Verify with no network calls: frontmatter valid (name: remotion-captions), the 6 files in place with matching fingerprints. Do not run anything from the folder and do not use the skill to verify. 5. Report what was installed, where, and what I still need to do myself (for example: that no licence was found in the upstream repository, that transcription runs Whisper locally on my GPU (with a model download) inside my own Remotion project, and that using it is a separate step that only starts when I ask for caption work). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
- It can download and install software packages.
What the scan found — excerpts from the install prompt
- installs packages — Prerequisites — None to install this skill — no account, no key, no payment, and no executable code in its fol · - At use time everything runs in my own Remotion project: captions are JSON Caption objects, transcription run · Prérequis — Aucun pour installer ce skill — aucun compte, aucune clé, aucun paiement, et aucun code exécutable
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.