About this skill
HyperFrames turns HTML compositions into video by rendering a paused timeline frame by frame. The skill describes the composition format, timing and media requirements, and a work loop for making the result editable in the HyperFrames desktop app. Reach for it when you want to create or change a HyperFrames video, including launch films, explainers, music videos, charts, maps, vertical clips, title cards, captions, or overlays. It also routes requests to other workflows when a slideshow, Remotion conversion, or another specialized skill fits better.
What it does
- For a new video, gathers intent and, for a fresh creation, prepares a brief before choosing a workflow.
- Routes the request to guidance for the relevant video type, format, motion, captions, overlays, or media.
- Sets up or works with an HTML composition made of a root page, scene compositions, and assets.
- Follows timing, timeline, media, and layout requirements intended to keep compositions deterministic and editable.
- For an existing project, checks its timeline and the person's changes before editing.
- After editing, runs the prescribed checks and reviews snapshots of a film or small edit.
- Previews the result and renders when the person approves, asks for the file, or requests no stops.
Who it's for
- People using coding agents to create or edit videos with HyperFrames.
- Video makers working on explainers, launch films, music videos, charts, maps, vertical clips, captions, overlays, or motion graphics.
- People who want to edit the resulting composition in the HyperFrames desktop app.
How to use it
Use the skill for requests to make, edit, animate, or render a video with HyperFrames. Describe the video or the changes you want; for a new film, the workflow may begin by gathering intent and proposing storylines before building.
Create a short product launch video from this brief using HyperFrames. Start by proposing three distinct storylines, then wait for me to choose one.
Good to know before you use it
- Contains runnable script files (scripts/bake-basemap.mjs, scripts/lib/main-module.mjs, scripts/lib/main-module.test.mjs, scripts/locate.mjs, …); review them before use.
- Uses the HyperFrames CLI and routes some work to other skills, such as slideshow and Remotion workflows.
- New projects default to 1920×1080 at 30 fps unless the request or source calls for another aspect ratio.
- For a new film over about 15 seconds that tells a story, the workflow presents three storyline options for the person to choose unless they ask for the file or no stops.
- Renders after the person approves the preview, asks for the file, or asks for no stops; otherwise it stops at the preview.
Before you installA skill's instructions steer your AI agent, so a few minutes of checking is worth it.
Security checklistSix checks before you add a skill to your agent
Skills are not only code. A harmful skill can be written in plain sentences that a code scanner does not flag. Research on public skill registries has found skills with malicious instructions and scripts.
- Read the skill itself. A skill is a folder with a SKILL.md file and sometimes scripts. The SKILL.md is not just documentation: it is text your AI agent follows. Read it, and read every script, before you install. Be wary of instructions that do not fit the stated task, such as reading keys or .env files, sending data elsewhere, or fetching code from the internet while it runs.
- Look for scripts. A skill that only contains text is far less risky than one that runs scripts on your computer. Check which files the folder contains and what each script does.
- Check the source. Make sure the repository belongs to the author or vendor you expect, and beware of lookalike names. Install the exact version (commit) you reviewed, and read changes before you upgrade.
- Use the least access that works. Run a new skill in a test project or sandbox first, without your production credentials, and keep your agent’s confirmation prompts switched on for actions that write, delete, send or spend.
- Have it scanned. Several tools check skills for known risks before you install: the security audits shown on each skill’s page on skills.sh (from partners such as Snyk and Socket), Snyk’s Skill Inspector, and the open-source Cisco Skill Scanner. Use them as one layer, not as proof.
- Ask an AI model to review it, with care. Asking an LLM to read the skill and report anything suspicious before you install it is a useful extra check, and it is what many people do. It is not a guarantee: the reviewer reads text that may have been written to manipulate it, so give it the skill as data to analyse, never let it run anything, and combine it with a scanner and your own reading. A pass is not proof that a skill is safe.
Scanners to try: skills.sh audits, Snyk Skill Inspector and Cisco Skill Scanner (open source).
Who published this skill?Pinned source: heygen-com/hyperframes
The pinned source is the GitHub repository heygen-com/hyperframes. Check that this is the author or company you expect.
- Published by the vendor
- Written and maintained by the company or project behind the service the skill works with. It is usually kept in step with that service, but this describes who maintains it, not that it has been audited by us.
- Community skill
- Written and maintained by an independent developer or group, not by the company behind the service it works with. It can be excellent and widely used, but the company has not reviewed it and updates depend on its author, who can stop at any time.
How installing a skill works
A skill is a folder. Your agent finds it in a skills folder: for example, Claude Code reads skills from a skills folder in your project or in your home folder, and other agents have their own location, so check your agent's documentation for the exact place.
In general you either copy the skill folder from its source (at the commit pinned on this page) into that folder, or use your agent's own command for adding skills. After installing, ask your agent to list its skills to confirm it was picked up.
We do not show a ready-made install command for each skill: a command that is copied wrongly or changed is a way to install something else, so take it only from the source itself, after you have read the checklist above.
This page is general information, not security or legal advice, and listing a skill is not an endorsement or a security review. We do not create, host, install or run skills, and listing details can be out of date, so check the source. You use skills at your own risk. See the section on third-party products in our Terms of Service.