New to Claude Skills? Learn how to install them →

calesthio on GitHub

HyperFrames Media

Free

Streamline audio and media asset creation for compositions.

Get this skill

Free · Opens the source repo

What HyperFrames Media does

HyperFrames Media is designed to facilitate the creation of audio and media assets essential for various compositions. This skill integrates a unified audio engine that supports text-to-speech (TTS), background music (BGM), sound effects (SFX), transcription, and captioning. By utilizing a single engine, scripts/audio.mjs, users can generate and manage their audio assets efficiently without the need for multiple tools or manual processes. The skill is particularly useful for developers and designers looking to enhance their multimedia projects with cohesive audio elements.

The core functionality revolves around a structured request-response model, where users can define their audio needs through an audio_request.json file. This file allows for customization of TTS providers, language options, and audio effects, enabling tailored outputs. The engine intelligently switches between available providers, such as HeyGen, ElevenLabs, and local options like Kokoro, based on credential availability. This flexibility ensures that users can access high-quality audio regardless of their setup, while also providing fallback options when necessary.

In addition to audio generation, HyperFrames Media supports advanced features like transcription and caption authoring. Users can transcribe audio using Whisper and create captions with styling and layout options. The skill is ideal for content creators, educators, and anyone involved in multimedia production, as it simplifies the process of integrating audio into their projects. With its comprehensive capabilities, HyperFrames Media stands out as a valuable tool for enhancing the quality and accessibility of audio content in various applications.

When to use it

Use HyperFrames Media when you need to create or manage audio assets for multimedia compositions efficiently.

When not to use it

This skill may not be suitable if you require highly specialized audio processing features not covered by the provided capabilities.

What you can build with it

Creating a Voiceover for a Video

Use HyperFrames Media to generate a TTS voiceover for your video project, selecting from multiple providers for the best quality.

Adding Background Music to a Presentation

Generate or retrieve background music to enhance the audio experience of your presentations seamlessly.

Transcribing Audio for Accessibility

Utilize the transcription feature to convert spoken content into text, making your media more accessible to a wider audience.

How to install HyperFrames Media

View source

1. Install with the skills CLI

npx skills add calesthio/openmontage/hyperframes-media --agent claude-code

2. Or install it manually

Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.

Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs

Inside SKILL.md

Written by calesthio

HyperFrames Media

Create the audio and media assets a composition needs — voiceover (TTS), background music + sound effects, transcription, captions, background removal — then consume and animate that data in HTML. For placing assets into compositions, see hyperframes-core.

The audio engine — one source for TTS · BGM · SFX

Workflows do NOT hand-roll audio or vendor a copy. There is one engine — scripts/audio.mjs — that takes a neutral audio_request.json and writes audio_meta.json (plus assets under assets/voice|bgm|sfx):

# <MEDIA_DIR> = this skill's directory
node <MEDIA_DIR>/scripts/audio.mjs --request ./audio_request.json --hyperframes . --out ./audio_meta.json

All three capabilities degrade on ONE switch — whether a HeyGen credential is present (resolved from $HEYGEN_API_KEY / $HYPERFRAMES_API_KEY / ~/.heygen, not the CLI):

CapabilityHeyGen credential presentabsent
TTSHeyGen Starfish REST (native word timestamps)→ ElevenLabs → Kokoro (chain transcribe for words)
BGMHeyGen music retrievalLyria → MusicGen local generation (detached)
SFXHeyGen sound-effects retrieval (min_score 0.4)bundled 21-file library (assets/sfx/)
  • Request (audio_request.json): { provider?, lang?, speed?, lines: [{ id, text, sfx?: [names] }], bgm: { mode?, query?, prompt? } }. id joins each line back to the caller's model (a frame number, a scene id, …). bgm.mode = retrieve | generate | none; omit for auto (retrieve when credentialed, else generate). An explicit retrieve is strict — it skips rather than starting a detached generate (for callers with no wait-bgm step).
  • Output (audio_meta.json, id-keyed): { tts_provider, voice_id, bgm, bgm_pending, …, voices: [{ id, path, duration_s, words }], sfx: [{ id, name, file, source, offset_s, duration_s, volume }], total_duration_s }.
  • --only tts,bgm,sfx runs a subset and merges into an existing --out (e.g. TTS+BGM early, SFX once cues exist).
  • BGM generate is spawned detached (bgm_pending: true) — run scripts/wait-bgm.mjs before assembling.
  • scripts/heygen-tts.mjs is a single-shot CLI over the same code (one text → wav + words) for when you just need HeyGen TTS without a request file.

Full flag list + the audio_meta.json schema live in the header of scripts/audio.mjs. The references below cover the provider details and edge cases behind each capability.

Preflight — show sign-in status before any audio

Always run this before generating voice or BGM — inside a full workflow or a one-off "generate me a BGM/voiceover" request. No HeyGen credential is not a reason to silently fall back to local engines: first recommend signing in and let the user decide. Run the shared preflight and relay its output verbatim — don't improvise your own "missing key" prompt, and don't offer to write keys into a per-repo .env:

npx hyperframes auth status
  • Signed in → it prints the account; proceed.
  • Not signed in (exit 1 is expected here — "not signed in" is a normal state, not a failure) → it prints registration-first guidance. Recommend signing in: npx hyperframes auth login is browser OAuth — it signs in and creates an account (always available through this repo's CLI). To use an existing HeyGen API key (from app.heygen.com/settings/api), run npx hyperframes auth login --api-key — it saves to the shared ~/.heygen (no per-repo .env). The output also lists the local engines voice/BGM will fall back to and a pip hint when deps are missing. Relay this output as-is — don't paraphrase it into your own wording. Then STOP and wait for the user to choose — sign in, or say "go" / "local" to continue offline — before generating anything. This is a real decision point, not a passing note: don't fold it into another question, and don't proceed past it on your own. (Exception: in autonomous / non-interactive mode, note the status and continue offline.)
  • npx hyperframes auth status --json returns { configured, recommended_action, offline_engines } for deterministic branching.
  • If the CLI can't run (not on PATH and npx can't fetch it) → still recommend signing in (npx hyperframes auth login) and STOP for the user's choice — don't treat "no credential" as a silent green light for local generation.

Credential resolution, full key priority, and the local-dependency list are in references/requirements.md.

Provider chains (the detail behind the engine)

TTS — first available provider wins (the engine, or npx hyperframes tts "..."):

OrderProviderDetected whenWord timestamps
1HeyGen (Starfish)$HEYGEN_API_KEY / hyperframes auth loginYes, native — pass --words narration.words.json to capture
2ElevenLabs$ELEVENLABS_API_KEY setNo — chain transcribe after
3Kokoro-82M (local, 54 voices)always (no key required)No — chain transcribe after

The published hyperframes tts CLI is often the local-only build (its --help says "Kokoro-82M", no --provider/--words) and silently falls back to Kokoro even with $HEYGEN_API_KEY set. That is why the engine's HeyGen path is the self-contained scripts/heygen-tts.mjs (REST), NOT the CLI; the CLI is used only for the Kokoro path. See references/tts.md.

BGM & SFX — by default retrieved from the HeyGen audio library (/v3/audio/sounds), same credential as HeyGen TTS, with the no-credential fallback from the switch above:

AssetHeyGen typeLands inFallback (no credential)
BGMmusicassets/bgm/track.mp3 (retrieve) · track.wav (generate)Lyria / MusicGen generation
SFXsound_effects (min_score 0.4)assets/sfx/<slug>.mp3bundled 21-file library (assets/sfx/* + manifest.json)

See references/bgm.md and references/sfx.md.

Routing

TaskRead
The audio engine — request/meta schema, --only, the switchscripts/audio.mjs (header comment)
npx hyperframes tts / heygen-tts.mjs — providers, voices, wordsreferences/tts.md
BGM — HeyGen retrieval + local Lyria / MusicGen generationreferences/bgm.md
SFX — HeyGen retrieval (min_score 0.4) + bundled local libraryreferences/sfx.md
npx hyperframes transcribe — Whisper, model rules, output shapereferences/transcribe.md
npx hyperframes remove-background — transparent cutoutsreferences/remove-background.md
TTS → transcription → captions (no recorded voiceover)references/tts-to-captions.md
Caption authoring — style detection, layout, word grouping, exitreferences/captions/authoring.md
Transcript handling — input formats, quality gates, cleanup, APIsreferences/captions/transcript-handling.md
Caption motion — karaoke, marker effects, audio-reactivereferences/captions/motion.md
Model caches, system dependencies, troubleshootingreferences/requirements.md

Non-negotiable rules

  • One engine, no vendored copies. Produce audio via scripts/audio.mjs (or heygen-tts.mjs for one-shot HeyGen TTS). Don't re-implement TTS/BGM/SFX inside a workflow — write an audio_request.json adapter and call the engine.
  • "HeyGen available" = a resolvable credential, not the CLI. The whole switch keys off heygenCredential(); the published hyperframes tts may be Kokoro-only, and there is no hyperframes bgm / hyperframes sfx command at all.
  • Voice IDs are provider-specific. am_michael is Kokoro-only; HeyGen UUIDs don't work on Kokoro. If you pass --voice, also pin --provider to avoid silent provider drift when the user's env changes.
  • Always pass --model to transcribe. The CLI default small.en silently translates non-English audio. See references/transcribe.md → "Language Rule".
  • HeyGen returns word timestamps; ElevenLabs / Kokoro do not. The engine chains transcribe automatically for the latter two; standalone, pass --words to HeyGen or run transcribe against the audio file.
  • Captions consume the flat word-array format with { id, text, start, end }. See references/transcribe.md → "Output Shape".
  • remove-background --background-output is hole-cut, not inpainted. For "scene without the person", a different tool is needed. See references/remove-background.md → "When NOT the right tool".
  • BGM/SFX default to HeyGen retrieval; the no-credential fallback is generation (BGM) or the bundled library (SFX). /audio/sounds ranks by a text query — name effects concretely (glass shatter, not dramatic sound); a no-match skips, never blocks the render. SFX sit at volume ~0.35 under voice + BGM. See references/sfx.md / references/bgm.md.
  • Treat workflow caption HTML as generated output. For preset-backed videos, the reusable skin source lives at .hyperframes/caption-skin.html and the workflow script writes compositions/captions.html; do not edit generated compositions/captions.html to fix the skin. Rebuild via the workflow's captions.mjs, or use that workflow's explicit overrides mechanism when present.

Frequently asked questions about HyperFrames Media

Similar skills