v0.9.42

hyperframes-audio

heygen-com@heygen-com⭐ 83.9k stars· last commit 2d ago· 105 open issues

>

Choose how to use this skill

You do not need every option. Choose the path your AI client supports. The stable page stays the same; versioned files are immutable.

1. Native installer

This listing has no registered native installer command. Use the complete package or source fallback below, depending on what your client supports.

Do not guess an installer command or replace an existing version without reviewing the diff.

2. Complete package recommended

Download the ZIP when available. It includes SKILL.md plus the references, security notes and version metadata.

No complete ProSkills package is published for this listing yet.

3. Prompt-only

Copy the prompt above when the agent can read the stable page or when you want to adopt the workflow without installing a skill.

Need only the instruction file?

Download SKILL.md only if your client requires a single file. The complete ZIP is safer for a full installation because it preserves the references and release context.

No path installs or executes anything by itself. Your agent still needs access to the project files. Before updating, compare the installed version and review the diff.

7.6/10
Verified
Oct 8, 2026

// RATINGS

⭐GitHub Stars
⭐⭐⭐⭐⭐ 83.9k on GitHubGitHub ↗

Very popular

🟢ProSkills ScoreAI Verified
7.6/10
📍

Not yet listed on ClawHub or SkillsMP

// README

HyperFrames is a free, open-source framework for turning HTML, CSS, media, and seekable animations into deterministic MP4 videos. Use it locally with the CLI, from AI coding agents with skills, or as the rendering core behind hosted authoring workflows.

The HyperFrames Studio app is free to use as well; its Pro plan adds HeyGen's top video, image, voice and music models.

Using Claude Code, Codex, Cursor, or another coding agent? Run npx hyperframes skills update once, then ask your agent to make a video.

Quick Start

With an AI coding agent

For Claude Code, install the versioned plugin:

claude plugin marketplace add heygen-com/hyperframes
claude plugin install hyperframes@hyperframes

To enable auto-update for the hyperframes marketplace, run claude in a terminal in your project. In Claude Code's terminal UI, run /plugin, then select Marketplaces → hyperframes → Enable auto-update. Afterward, use /hyperframes:hyperframes. See the plugin guide for Copilot, VS Code, Cursor, Gemini CLI, updates, and migration.

For standalone skills (including OpenCode), use:

npx skills add heygen-com/hyperframes

The picker opens with nothing pre-selected — the Core Skills group is all you need; /slideshow, /remotion-to-hyperframes and /figma install on demand. Without the picker (a script or a CI job), npx hyperframes skills update installs exactly the core set, whereas skills add --all installs all 9 published skills. The six repo-internal skills under .claude/skills / .agents/skills are excluded by default. For the full published set use npx hyperframes skills.

skills add resolves the skills.sh registry blob, which can lag main by hours. npx hyperframes skills update installs the skills from the release tag that matches your CLI version, so they match the CLI that runs them.

Run project-local installs from your video project's directory. From a HyperFrames checkout, use npx hyperframes skills update for a global install instead: a project-local installer target can overlap the tracked skills/ source and overwrite uncommitted edits. See contributor setup.

Try a prompt like:

Using /hyperframes, create a 10-second product intro with a fade-in title, a background video, and subtle background music.

The skills teach agents the HyperFrames production loop: plan the video, write valid HTML, wire seekable animations, add media, lint, preview, and render. They work with Claude Code, Codex, Cursor, Gemini CLI, IBM Bob, and other coding agents that support skills.

Skills

HyperFrames ships 9 skills. Make any video by asking for it; the /hyperframes skill carries the contract and the references (film, captions, overlays, motion, look). Read it first.

For standalone installation, default to the core set (/hyperframes, /hyperframes-cli, /hyperframes-registry, /media-use, /reverse-any-video, /style-sampling). npx hyperframes skills update installs exactly that from anywhere; the interactive picker (npx skills add heygen-com/hyperframes) lists it as the "Core Skills" group, nothing pre-selected. The picker is interactive-only — a non-interactive or agent run without --skill installs all 9. Use npx skills add heygen-com/hyperframes --all to install the complete published set deliberately (skips the picker), or npx skills add heygen-com/hyperframes --skill <name> for just one (bare name, no leading /).

Standalone installs stay lean after that: npx hyperframes init installs the core set only when it is missing and never touches a skill you already have (npx hyperframes skills update refreshes them, and never removes one); /figma, /slideshow and /remotion-to-hyperframes install on demand with npx hyperframes skills update <name>. Nothing re-pulls the full set behind your back.

Plugin packages

Plugins bundle the full skill catalog and use their agent's update manager. bun run package:agent-plugin builds the committed portable ZIP, source metadata, and SHA-256 checksum. See the maintainer checklist.

Upload to Codex

Build the upload-ready Codex plugin archive from the committed HEAD version of the manifest, brand assets, and skills:

bun run package:codex-plugin

This writes dist/hyperframes-plugin.zip with a hyperframes/ root folder and fails if the archive exceeds Codex's 100 MB upload limit.

Core set

SkillUse when

// HOW IT'S BUILT

// FILES

2 files shipped with this skill. Inline text is the catalog copy. The upstream link is the source repository.

  • skills/hyperframes-audio/SKILL.md7.8 KBupstream ↗
    ---
    name: hyperframes-audio
    description: >
      Use when audio already placed in a HyperFrames composition needs to be mixed:
      fade-in/fade-out, crossfade, track gain or volume, volume automation, ducking,
      a music bed that fights a voiceover (voiceover carve), effects on a track
      (EQ, compressor, limiter, gate, saturation, delay, reverb, chorus, phaser,
      bitcrush), automation envelopes drawn on a track's volume or any effect
      parameter, or one submix bus carrying a chain, a fader and an automation clock
      for several tracks at once (`<hf-audio-group>`).
      Don't use for sourcing or generating audio — finding BGM, SFX, or making a
      voiceover is `/media-use`. Don't use for clip timing or track layout, which is
      `/hyperframes-core`.
    ---
    
    **Plugin installs:** Before setup or freshness commands, follow [plugin execution rules](../hyperframes/references/plugin-installation.md) when this skill is inside a HyperFrames plugin. Standalone installs keep the update instructions below.
    
    # HyperFrames Audio
    
    A mix is a set of relationships, not a stack of processors. Two tracks that each
    sound right alone can be unlistenable together, and the fix is almost never "turn
    one down" — it is finding what they are fighting over and giving it to whichever
    one needs it. Every tool here exists to express one of those relationships.
    
    Effects live on the element as `data-fx-chain`, and preview and render run the
    same Web Audio graph — the studio in a live context, the engine in an offline one
    inside the browser it already drives. There is one implementation of each effect,
    so what you hear while scrubbing is what gets written. You never tune twice.
    
    Clip timing remains `/hyperframes-core`: audio/video trims and source ranges use
    `data-start`, `data-duration`, and `data-media-start`, and crossfades overlap
    clips on different tracks. This skill owns placed-track fade-in/fade-out,
    crossfade envelopes, track gain/track volume, volume and effect automation,
    ducking/voiceover carve, and the effect chain. `/media-use` owns sourcing,
    generation, and preprocessing.
    
    Constant `data-playback-rate` (`0.1..10`) is render-safe for picture and
    pitch-preserved sound when matching audio/video elements use the same timing,
    source offset, and rate. A speed ramp is a `rate` lane in `data-automation`
    (see `docs/reference/speed-ramps`); it wins over the constant and keeps pitch
    in preview and render. HyperFrames does not
    provide automatic waveform sync or drift correction.
    For copyable cut/crossfade/retime recipes, use `/hyperframes-core` → `references/creator-editing-recipes.md`.
    
    Three attributes carry everything, on the audio/video element itself — or, for
    the first two, on an `<hf-audio-group>` bus (see "One bus for many tracks"):
    
    | Attribute         | Holds                                                     |
    | ----------------- | --------------------------------------------------------- |
    | `data-fx-chain`   | the effects, in signal order                              |
    | `data-automation` | envelopes on this track's volume or its effect parameters |
    | `data-fx-carve`   | the carve's own settings, so it can be re-derived         |
    
    The shipped effect families are gain, EQ (highpass, lowpass, peaking, shelves),
    compressor, limiter, gate, saturate, delay, reverb, chorus, phaser, and bitcrush.
    
    Exact JSON for each, and the rules a lane must satisfy: `references/attributes.md`.
    Every effect with its parameters, ranges and units: `references/fx-registry.md`.
    How to work out what is wrong with a file you cannot hear:
    `references/diagnosis.md`.
    **Presets, named jobs and one-knob profiles, plus a symptom-to-fix table:
    `references/presets.md`** — read that before hand-building a chain, because one
    of the presets or named jobs usually already names the problem.
    
    ## How it fits together
    
    Two authoring surfaces write those attributes; two runtimes read them through the
    same builders. That shared middle is why preview predicts the render.
    
    ```mermaid
    flowchart TB
      voice["voice track<br/>media file"]
      bed["music bed<br/>media file"]
    
      subgraph AUTHOR["Authoring — the only things that write attributes"]
        panel["Studio<br/>Voiceover carve control"]
        script["scripts/carve.mjs<br/>detects the pair, dynamic by default"]
        analysis["core/audioCarve.ts<br/>carveProfile · analyseCarveBands<br/>analyseCarveDuck · analyseCarveDynamics"]
        panel --> analysis
        script --> analysis
      end
    
      voice --> analysis
      bed --> analysis
    
      subgraph ATTRS["Written onto the bed element"]
        carveAttr["data-fx-carve<br/>source · strength · dynamic"]
        chainAttr["data-fx-chain<br/>peaking xN + gain, tagged fromCarve"]
        autoAttr["data-automation<br/>a lane per carved parameter"]
      end
    
      analysis --> carveAttr
      analysis --> chainAttr
      analysis --> autoAttr
    
      subgraph SHARED["One implementation, read by both"]
        build["audioFxGraph.ts · buildFxChain"]
        sched["audioFxAutomation.ts · scheduleChainAutomation"]
      end
    
      chainAttr --> build
      autoAttr --> sched
    
      build --> preview["Preview<br/>live AudioContext<br/>attachElementFxChain"]
      sched --> preview
      build --> render["Render<br/>OfflineAudioContext in the headless browser<br/>applyAudioFxChain"]
      sched --> render
    
      preview --> heard["what you hear while scrubbing"]
      render --> wav["processed WAV<br/>+ chainTailSeconds so the mix lets the tail through"]
      wav --> mix["engine · audioMixer<br/>volume lane baked into the PCM here, not in the graph"]
      mix --> out["the rendered mix"]
    
      edit["editing the attribute mid-playback"] -.->|MutationObserver| preview
    ```
    
    The carve's own settings are never read at playback — the chain and lanes it
    produced are what play. `data-fx-carve` exists so strength can be changed on an
    existing carve instead of guessed back out of the filters.
    
    Inside a carved bed the signal runs through the dips first, then the level match,
    then anything you built yourself — which is why a limiter you add still acts as
    the last ceiling:
    
    ```mermaid
    flowchart LR
      src["decoded bed"] --> p1["peaking<br/>400 Hz"]
      p1 --> p2["peaking<br/>1 kHz"]
      p2 --> p3["peaking<br/>1.6 kHz"]
      p3 --> g["gain<br/>level match"]
      g --> hand["your own effects<br/>e.g. limiter"]
      hand --> dest["track gain, then out"]
    
      l1["lane fx.n1.gain"] -.->|"envelope of the voice's<br/>level in that band"| p1
      l4["lane fx.n4.gain"] -.->|"how far the bed<br/>ducks overall"| g
    ```
    
    A static carve is the same graph with fixed values and no lanes at all.
    
    ## First, work out what is wrong
    
    The table below starts from "it sounds boomy" — which presumes somebody already
    listened and said so. Handed a file and "fix this", you have no such sentence
    and you cannot listen, so you have to measure. One rule governs all of it:
    
    > **The absolute spectrum of a single unknown voice cannot be diagnosed.**
    > Formants are ±10 dB, fundamentals run 85–255 Hz, and sentences decline 5–6 dB
    > as they end. Every one of those reads as a defect on its own, and every one of
    > them is the speaker.
    
    So compare, and compare against something **inside the same file**: the clean
    original if it exists, otherwise the pauses — whatever is audible in a gap is
    additive, and the gap's spectrum is the channel rather than the voice. Comparing
    against a published average spectrum or a synthesised control voice does not
    work: two speakers differ by more than most defects, and both wrong answers in
    the evaluation behind this guidance came from exactly that.
    
    When there is no original and no usable silence, a static tonal defect is
    genuinely under-determined. Say so and offer the readings that fit, rather than
    picking one and building a chain on it.
    
    Commands, traps and worked recipes: **`references/diagnosis.md`**. Read it
    before diagnosing a file nobody has described.
    
    ## Start from the symptom
    
    Once you know the band and the kind, name what is wrong with the audio. Most bad audio is
    one or two of these, and each has a shipped answer:
    
    | It sounds like                     | Reach for               
  • README.mdupstream ↗

    Contents are not inlined in the catalog. Open the upstream file.

Plain-text copy, no login: /skill-bundles/heygen-com-hyperframes-skills-hyperframes-audio.md

// REPO STATS

83.9k stars
105 open issues
Last commit: 2d ago