Agent skill · creative production · aiskillstore
embedded-captions
Add captions or subtitles to an existing single-subject talking-head video without editing the footage. Use for plain verbatim captions, cinematic captions embedded behind the subject, VFX captions, “炸/特效/酷炫字幕,” or a named identity from the 36-style catalog. Route by visual identity, not by backend engine. The quiet `anchor` rail is the default; embed every word only when the user explicitly wants a fully cinematic treatment. The workflow runs locally end to end, including transcription and subject matting; split multi-shot footage before applying it.
Why this skill is useful
Adds a detailed workflow for embedding captions in videos, including specific scripts and JSON configurations that the AI wouldn't generate on its own.
What it needs
Requires node installed locally. About 11k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
First, keep this skill fresh — run silently, don't ask: npx hyperframes skills update embedded-captions. A fast no-op when everything is current; otherwise it refreshes this skill plus the core domain skills it depends on before you rely on them. Embedded Captions One catalog, picked up front (CATALOG.md — 36 identities; the engines behind it are backend detail). Standard (default) builds a clean verbatim rail (lower-third subtitle carrying most text) + an embed climax composited into the scene behind the subject at the peak. Cinematic is pure embed — no rail, every caption composited behind the subject (hero typography, accumulation, occlusion as the effect). Theme is a complete themed constitution — body paradigm × hero setpiece × front fx × plate reaction, composed from registries (themes/README.md): ordnance terminal neonsign stardust stomp. Most explainer / voiceover is Standard; embed is the scarce, earned peak — embedding every word is the common mistake; Theme is for VFX-grade asks ("炸", "特效", "像 AE 做的"). --- Operational flow (TL;DR) Routed through /hyperframes, the intent layer confirms only the input (which clip) and announces the identity pick as a deferred ask — the shortlist needs the probed clip, so it stays at step 1 below; the layer's run-shape questions don't apply (the footage is untouched, there is no storyboard to review). A BRIEF.md, when present, carries the confirmed input and any user notes — read it first. The craft prose below is long; the pipeline itself is short — and everything deterministic is computed or compiled, never hand-written: 1. Decision gate (refuse bad clips) → pick ONE identity from CATALOG.md (36 identities; engine/compiler derived by lookup — never surface a mode/category question) 2. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/embedded-captions