hyperframes-studio skillA
hyperframes-studio is agent-read markdown (skill) from heygen-com/hyperframes: Use when building or editing a HyperFrames project that people open in Studio: how the timeline should be laid out so it reads well (one caption track, one element kind per track, every scene a sub-composition) and where captions and key content may sit (safe zones). Don't use for how to perform an individual edit (split, trim, retime, volume, copy, swap): that is `creator-editing-recipes.md` in `/hyperframes-core`..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# HyperFrames Studio conventions Studio draws one timeline row per top-level element. A project that follows the rules below opens as a short, readable timeline; one that does not opens as a wall of unlabeled rows the user cannot edit. These are conventions for what to build. For how to change a clip, follow `/hyperframes-core` `references/creator-editing-recipes.md` and never invent a different form of the same edit. ## 1. Every scene is a sub-composition The root composition holds only timed hosts, media and audio. Any scene with nested structure (a div containing children, a title with a subtitle, a chart) is its own file loaded with `data-composition-src`, wiring in `references/sub-compositions.md`. Nested markup left inside the root does not become a row of its own. It hides inside one opaque row that cannot be trimmed or moved part by part. Author as if a structure lint rejects any violation. ## 2. One caption track - All captions live on one track: a single sub-composition host (one `data-track-index`) marked `data-track-kind="captions"` that carries every caption group in order. - Never one row per caption group, and never captions mixed onto a track with …
Read the whole file at its exact version.
How to install
mdr add heygen-com/hyperframes/hyperframes-studio@git:20260919.2db126dmdr add heygen-com/hyperframes/hyperframes-studio@sha256:a3925932d2f38cbfPin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_ogveftawbquglx4q)
1 badge views in 30 days
Versions
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (3661 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
heygen-com/hyperframes · 52,820 stars · license Apache-2.0 · pushed 2026-09-24 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ogveftawbquglx4q GET https://markdownregistry.com/api/v1/resolve?ref=heygen-com/hyperframes/hyperframes-studio GET https://markdownregistry.com/api/v1/blob/a3925932d2f38cbf3423ca7232003423c171f607c2e105084e0b3fff61189103
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.