Skip to main content
HyperFrames skills teach coding agents the project format, animation rules, media workflow, and validation loop that generic web knowledge does not cover. The terminal output is a real run of the command. Afterwards the agent reads /hyperframes before it builds, instead of guessing at the framework’s rules. Prefer a versioned plugin when your agent supports one. This page covers standalone installs, including OpenCode. Plugin users should update through their agent’s plugin manager instead of running the commands below.

​
Install for a person

Run the interactive installer:
Run this command from your video project’s directory. If you cloned HyperFrames to contribute, use npx hyperframes skills update for a global install from that checkout, or run the project installer in a separate video project. Project-local installer targets can overlap the checkout’s tracked skills/ source and overwrite uncommitted edits. Select Core Skills. That covers every kind of video; the other skills install when a request needs them, so you do not need the full catalog up front. Start a fresh agent chat after installation, then ask it to use /hyperframes.

​
Install or refresh from an agent

For a non-interactive agent or CI environment, use:
This installs or refreshes the core set and any HyperFrames skills already present in the global install, then links those bundles into compatible installed agents. It does not add every optional skill. Updates check the Claude global store (~/.claude/skills, or the skills/ folder under CLAUDE_CONFIG_DIR) that the installer writes to. Skills found only in another agent’s directory do not make a missing core skill count as installed there, and optional skills in that other directory are not automatically added to the managed store. Name an optional skill explicitly to add it. The install record’s publisher attribution is respected even before the managed store exists. An explicit update request for a skill owned by another publisher fails without overwriting it, including when the freshness check is unavailable offline. Check freshness without changing anything:
Install or refresh one skill explicitly:

​
Use the skills in GitHub Copilot CLI

Run npx hyperframes skills update, open the project, and start Copilot:
If Copilot was already running, use /skills reload. Use /skills list or /skills info hyperframes to confirm discovery. GitHub’s current skills guide lists its project and personal skill locations. Both agents can use the same first request:
Continue in the same conversation for revisions. For hosted creation instead of a local project, use the HyperFrames MCP guide.

​
Use the skills in Google Antigravity

Install the skills from the root of the project you open in Antigravity:
Select Core Skills and Antigravity. This uses Antigravity’s supported project location, .agents/skills, and keeps the skills with the project. Start a fresh Antigravity conversation after installation. Antigravity also supports a global ~/.gemini/config/skills directory. See Google’s current skills guide before managing that directory by hand.

​
Use the skills in IBM Bob

Run npx hyperframes skills update, then open or restart Bob Shell in the project folder so it discovers the skills linked under ~/.bob/skills:
Ask Bob to use /hyperframes for the first request. Running the update again refreshes the same global skill bundles without changing the project format.

​
What the skills cover

Make any video by asking for it; the /hyperframes skill carries the contract and the references (each kind of film, story, motion, look, sound, review, captions, overlays). You can name a skill directly, but you do not need to memorize the names to start.

​
Install more only when you need it

Install the complete published set deliberately with:
npx skills add heygen-com/hyperframes --all also installs the complete published set. Repo-internal skills are excluded by default. Or install one named skill:
Use the full set for an environment that must work across many HyperFrames tasks without fetching later. For a normal project, the core set is smaller and easier to keep current.

​
If the agent cannot see a skill

  1. Start a new agent session.
  2. Confirm that the project or global skill directory belongs to the agent you are using.
  3. Run npx hyperframes skills check.
  4. Run npx hyperframes skills update when the check reports a missing or stale core skill.
The individual skill definitions remain the source of truth for agents and are available in the HyperFrames repository.

​
If an update says no installed skills match

With skills@1.7.x, npx skills update heygen-com/hyperframes treats heygen-com/hyperframes as an installed skill name. It reports No installed skills found matching even when HyperFrames skills are installed. Use the HyperFrames updater to refresh the core set and the HyperFrames skills already installed globally:
The standalone skills update command accepts skill names, such as npx skills update hyperframes -g to update only the global /hyperframes skill. The repository name belongs in skills add, as shown in the install steps above.

​
If an installed skill has a YAML parse error

A Skipped .../SKILL.md — YAML parse error warning names the installed file that cannot be read. Back up that file before editing it, especially if it contains custom instructions. A multiline description needs indented continuation lines; for example:
Keep the file’s existing description text and skill body; the example shows only the YAML format. Run npx skills list -g afterwards to verify global discovery, or npx skills list for a project install. Repo-internal skills such as seam-craft are excluded from the published set. Refreshing the core skills does not repair an old, separately installed copy of an internal skill. A YAML warning and a name-matching error can occur in the same run and need these separate fixes.