HyperFrames Studio
Conventions for working with a person on a HyperFrames film project in Studio — talk before you build, timeline layout rules, storyboards
- What
- Conventions for working with a person on a HyperFrames film project in Studio — talk before you build, timeline layout rules, storyboards
- Cost
- Free
- Needs
- a HyperFrames Studio project to work on; the companion hyperframes-core references for individual edit recipes
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — the official HeyGen HyperFrames skill for studio collaboration: conventions for working with a person on a film project — talk before you build (questions and loose ideas get answers and plans, not edits), timeline layout rules (one caption track, one element kind per track, every scene a sub-composition), safe zones, and the storyboard workflow the HyperFrames launch films follow. By @heygen-com, listed here with credit to its creator. Honest caveats: conventions for what to build, not how to perform individual edits (that lives in the companion editing-recipes reference); only for HyperFrames Studio projects. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Prerequisites: a HyperFrames Studio project to work on; the companion hyperframes-core references for individual edit recipes Install "HyperFrames Studio" for me. Conventions for working with a person on a HyperFrames film project in Studio — talk before you build, timeline layout rules, storyboards Repository: https://github.com/heygen-com/hyperframes 1. Fetch the SKILL.md file for the heygen-com-hyperframes-studio skill from the repository into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "heygen-com-hyperframes-studio". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. any accounts, API keys, or CLI tools mentioned in the prerequisites above). 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. Never ask me to paste secrets in chat — credentials go through the secure vault or environment variables. If anything looks off, stop and ask me.
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.