New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Hyperframes CLI

by chmonitor in chmonitor/chmonitor

HyperFrames CLI dev loop. An agent skill from chmonitor/chmonitor.

GPL-3.0Auto-check passedMedia & Creative

Install Hyperframes CLI

skills CLI
$ npx skills add chmonitor/chmonitor --skill hyperframes-cli -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install chmonitor/chmonitor hyperframes-cli --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/chmonitor/chmonitor.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/hyperframes-cli .claude/skills/hyperframes-cli && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
hyperframes-cli
GitHub stars
299
Used in
2 other repos
Token cost
~2.3k tokens
SKILL.md length
893 words
Files
7 (incl. references)
Skills in repo
53
Repo updated
First seen
Licence
GPL-3.0

At a glance

HyperFrames CLI dev loop. An agent skill from chmonitor/chmonitor.

  • Works in 7 steps: Scaffold — npx hyperframes init my-video… → Write — author HTML composition (see the… → Lint — npx hyperframes lint → …
  • Running npx hyperframes init
  • SKILL.md covers Workflow, Agent Conventions, Routing and Cross-Skill Hand-Offs, plus 2 more sections
  • Calls npx, jq and ffprobe

What it does

Hyperframes CLI is an agent skill from chmonitor/chmonitor. HyperFrames CLI dev loop. Use when running npx hyperframes init, add, catalog, capture, lint, validate, inspect, layout, snapshot, preview, play, render, publish, lambda, doctor, browser, info, upgrade, skills, compositions, docs, benchmark, telemetry, transcribe, tts, or remove-background, or when troubleshooting the HyperFrames build/render environment. Entry point for AWS Lambda cloud rendering (hyperframes lambda deploy / render / progress / destroy / policies).

Its SKILL.md is about 2.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including reference files (for example `references/doctor-browser.md`, `references/init-and-scaffold.md` and `references/lambda.md`).

It sits in Media & Creative, covering Motion graphics. It works with HeyGen and AWS Lambda. The repository describes itself as: Open-source operational advisor for ClickHouse — real-time monitoring plus AI-driven index/partition/materialized-view recommendations. The licence is GPL-3.0.

When your agent uses it

  • Running npx hyperframes init
  • Remove-background
  • Troubleshooting the HyperFrames build/render environment

Example prompts

  • “Use the hyperframes-cli skill to hyperframe CLI dev loop. An agent skill from chmonitor/chmonitor”
  • “/hyperframes-cli”

Requirements

  • Node.js
  • Docker

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. Scaffold — npx hyperframes init my-video (or capture from a URL)
  2. Write — author HTML composition (see the hyperframes-core skill)
  3. Lint — npx hyperframes lint
  4. Validate — npx hyperframes validate (runtime errors + contrast)
  5. Visual inspect — npx hyperframes inspect
  6. Preview — npx hyperframes preview opens Studio, the timeline editor where the user can manually edit anything (not just watch). Review…
  7. Render — pick the variant

What it can do on your machine

Read from SKILL.md and the folder at commit fc39ef0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • npx
    • jq
    • ffprobe

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use npx, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Hyperframes CLI loads about 2.3k tokens when it runs, and up to ~14k if it reads all its reference files. Until then it costs about 122 tokens; SKILL.md has 893 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~122
When it runs · the whole SKILL.md, loaded when a task matches
~2.3k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~14k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from chmonitor/chmonitor at commit fc39ef0, republished under its GPL-3.0 licence (© chmonitor). 893 words, ~2,327 tokens.

Download SKILL.mdSave it as .claude/skills/hyperframes-cli/SKILL.md (or your agent's skills folder). This skill also uses 6 other files; get the full folder from GitHub.
name
hyperframes-cli
description
HyperFrames CLI dev loop. Use when running npx hyperframes init, add, catalog, capture, lint, validate, inspect, layout, snapshot, preview, play, render, publish, lambda, doctor, browser, info, upgrade, skills, compositions, docs, benchmark, telemetry, transcribe, tts, or remove-background, or when troubleshooting the HyperFrames build/render environment. Entry point for AWS Lambda cloud rendering (`hyperframes lambda deploy / render / progress / destroy / policies`).

HyperFrames CLI

Everything runs through npx hyperframes unless project instructions specify a local wrapper. Obey the local wrapper exactly. Requires Node.js >= 22 and FFmpeg.

Workflow

  1. Scaffold — npx hyperframes init my-video (or capture from a URL)
  2. Write — author HTML composition (see the hyperframes-core skill)
  3. Lint — npx hyperframes lint
  4. Validate — npx hyperframes validate (runtime errors + contrast)
  5. Visual inspect — npx hyperframes inspect
  6. Preview — npx hyperframes preview opens Studio, the timeline editor where the user can manually edit anything (not just watch). Review there, then ask before rendering.
  7. Render — pick the variant:
    • Iterate: npx hyperframes render --quality draft
    • Deliver: npx hyperframes render --quality high --output out.mp4
    • CI / cross-host repro: npx hyperframes render --docker --strict --output out.mp4
    • Cloud (long / large): npx hyperframes lambda render ./my-project --width 1920 --height 1080 --wait (see Lambda below)

Run lint, validate, and inspect before preview. lint catches missing data-composition-id, overlapping tracks, and unregistered timelines. validate loads the composition in headless Chrome and reports runtime console errors plus WCAG contrast issues. inspect seeks through the timeline and reports text spilling out of bubbles/containers or off the canvas — and, when a *.motion.json sidecar is present, verifies motion intent (entrances firing under seek, stagger order, in-frame, liveness) against that same seeked timeline.

For motion-heavy work, prefer snapshot-driven iteration and a *.motion.json sidecar — see references/lint-validate-inspect.md for the discipline and motion-verification spec.

Agent Conventions

Cross-cutting rules that hold for every command:

  • --json is available on every command except render, preview, and play. Use it for any agent / CI invocation of the supported commands; output includes a _meta envelope (cli version, latest available, update advice). render reports status via stdout + exit code only — verify success with the post-render check below; preview / play are servers, no JSON.
  • doctor --json always exits 0, even when the environment is broken. Gate on the payload's ok field: npx hyperframes doctor --json | jq -e '.ok' > /dev/null. This insulates pipelines from CLI release churn.
  • Non-TTY mode is auto-detected. When stdout is not a TTY (CI, agents, piped output) the CLI auto-switches to non-interactive; init then requires --example. Pass --non-interactive to force this mode even on a TTY.
  • CI gating on render: --strict fails on lint errors, --strict-all fails on warnings too, --strict-variables fails on undeclared --variables keys.
  • Paths in --json are redacted — $HOME becomes the literal $HOME so output is safe to paste into bug reports and agent contexts.
  • Render is user-gated. Never auto-render once the checks pass. Pause at preview, tell the user the video is editable in Studio, and render only after they approve.
  • Post-render verification. After render returns exit 0, confirm the output file exists and has plausible size before reporting success: [ -s "$OUTPUT" ] || echo "render produced no output". The CLI prints ◇ <path> on success; for long renders also sanity-check duration with ffprobe -i "$OUTPUT" -show_format -v error.

Routing

Want to…Read
Scaffold a project (init, capture, skills)references/init-and-scaffold.md
Check correctness (lint, validate, inspect, snapshot)references/lint-validate-inspect.md
Preview or render (preview, play, render, publish)references/preview-render.md
Diagnose the environment (doctor, browser)references/doctor-browser.md
Cloud render on AWS Lambda (lambda deploy / sites / render / progress / destroy / policies)references/lambda.md
Everything else (info, upgrade, compositions, docs, benchmark, telemetry, asset preprocessing)references/upgrade-info-misc.md
Show full SKILL.md (371 more words)Show less

Cross-Skill Hand-Offs

  • Tailwind projects (init --tailwind) → use hyperframes-core (Tailwind reference) before editing classes or theme tokens.
  • Registry blocks/components (hyperframes add, hyperframes catalog) → use hyperframes-registry for install paths, sub-composition wiring, and snippet merging.
  • Asset preprocessing (tts, transcribe, remove-background) → use hyperframes-media for voice selection, Whisper model rules, captions, and TTS-to-captions chain.
  • Parametrized renders (--variables) → declared via data-composition-variables on <html>; see hyperframes-core for the full schema.

Lambda (Cloud Rendering)

hyperframes lambda deploys distributed rendering to AWS Lambda and drives renders from your laptop or CI. End-to-end is three commands:

bash
npx hyperframes lambda deploy                                             # provision SAM stack (Lambda + Step Functions + S3)
npx hyperframes lambda render ./my-project --width 1920 --height 1080 --wait
npx hyperframes lambda destroy                                            # tear down (S3 bucket is retained)

Use Lambda when a render is too long / too large for one host (multi-minute videos, 4K, large parallel batches) and you have AWS credentials configured. For dev-loop iteration stay on local render.

See references/lambda.md for prerequisites, all 6 subcommands (deploy, sites create, render, progress, destroy, policies), IAM policy validation, state files, and cost / cleanup rules.

Minimum Completion Gate

Static gates
bash
npx hyperframes lint
npx hyperframes validate

Add inspect for layout-sensitive work and render --strict in CI to fail on lint errors.

Visual smoke test — required when the project uses sub-compositions

lint / validate / inspect evaluate each composition in isolation. They never load index.html and mount sub-compositions via data-composition-src, so they cannot catch cross-file mount failures (see hyperframes-core → references/sub-compositions.md, "Common pitfalls"). The only gate that catches them is one that actually loads index.html and seeks the timeline.

Use hyperframes snapshot — it loads the project the same way render does (so it exercises the same mount path) but only captures the timestamps you request, so it's seconds instead of a full render:

bash
# Capture one frame at the midpoint of every sub-composition.
# Midpoints = data-start + data-duration/2 for each host slot in index.html.
npx hyperframes snapshot --at <t1>,<t2>,<t3>,...

# Or, if you don't need per-scene targeting, an evenly-spaced sample:
npx hyperframes snapshot --frames 9

Output lands in snapshots/frame-NN-at-Xs.png. Eyeball each frame against the scene plan.

Per-frame red flags (each maps to a specific failure mode the static gates miss):

What you seeRoot cause
Text shows up tiny + unstyled in the top-left corner<style> block left in <head> outside <template> (Pitfall 1) — no CSS reached live DOM
SVG/icon elements blown up to canvas-sizeSame as above — no width/height constraints applied
Hero element of the scene is missing entirely; only background + watermark visibleHost-id ≠ template id (Pitfall 2) — timeline never ran, frame captured at initial state
Snapshot command logs Sub-composition timelines not registered after 45000msPitfall 2 — direct confirmation

snapshots/ can be deleted after eyeballing; the user-facing final render is a separate pass with npx hyperframes render.

© chmonitor, GPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 6 other files (references) in .agents/skills/hyperframes-cli of chmonitor/chmonitor.

  • SKILL.md
  • references/doctor-browser.md
  • references/init-and-scaffold.md
  • references/lambda.md
  • references/lint-validate-inspect.md
  • references/preview-render.md
  • references/upgrade-info-misc.md

Open the folder on GitHubat commit fc39ef0

Used in 2 other repositories

We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 2 other GitHub owners. This page covers the copy in chmonitor/chmonitor, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Hyperframes CLI next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Hyperframes CLI compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Hyperframes CLI this skillchmonitor/chmonitor2992 repos~2.3kAutomated safety check: PassGPL-3.0
HyperFrames CLI Workflowheygen-com/hyperframes59k1 repos~6kAutomated safety check: PassApache-2.0
Hyperframes CLIaiskillstore/marketplace4301 repos~2.7kAutomated safety check: PassNone
HyperFrames Animationheygen-com/hyperframes59k3 repos~2.1kAutomated safety check: PassApache-2.0
HyperFrames Video Entry Pointheygen-com/hyperframes59k3 repos~5.2kAutomated safety check: PassApache-2.0
Remotion to HyperFrames Porterheygen-com/hyperframes59k3 repos~2.8kAutomated safety check: PassApache-2.0

Similar skills

  • HyperFrames CLI Workflow

    heygen-com/hyperframes

    Guides the HyperFrames command-line loop for video projects: scaffold, lint, check, preview and render locally or on HeyGen cloud, AWS Lambda or Cloud Run.

    59k GitHub starsUsed in 1 repo~6k tokens
    Media & CreativeAuto-check passed

  • Hyperframes CLI

    aiskillstore/marketplace

    Use the HyperFrames CLI development loop: init, add, catalog, capture, lint, check, snapshot, compare, grade-compare, preview, play, present, beats, keyframes, single or batch render, publish…

    430 GitHub starsUsed in 1 repo~2.7k tokens
    Media & CreativeAuto-check passed

  • HyperFrames Animation

    heygen-com/hyperframes

    Collects motion rules, scene blueprints, transitions and runtime adapters for HyperFrames video compositions, with GSAP as the default animation runtime.

    59k GitHub starsUsed in 3 repos~2.1k tokens
    Media & CreativeAuto-check passed

  • HyperFrames Video Entry Point

    heygen-com/hyperframes

    Entry point for making, editing and rendering videos from HTML compositions with HyperFrames, routing each request to the right workflow.

    59k GitHub starsUsed in 3 repos~5.2k tokens
    Media & CreativeAuto-check passed

  • Remotion to HyperFrames Porter

    heygen-com/hyperframes

    Ports an existing Remotion (React) composition to HyperFrames HTML with GSAP, one way, and grades the result against a tiered set of reference fixtures.

    59k GitHub starsUsed in 3 repos~2.8k tokens
    Media & CreativeAuto-check passed

  • Reference Video Replica Qc

    Pluviobyte/video-production-skills

    Analyze, recreate, align, and verify reference-video motion.

    667 GitHub stars~1.8k tokensUpdated 2 mo ago
    Media & CreativeAuto-check passed

More from chmonitor/chmonitor

All 53 skills in this repo

  • Hyperframes Creative

    chmonitor/chmonitor

    Non-animation creative direction for HyperFrames videos. An agent skill from chmonitor/chmonitor.

    299 GitHub starsUsed in 5 repos~1.3k tokens
    Auto-check passed

  • Hyperframes Media

    chmonitor/chmonitor

    Audio and media assets for HyperFrames compositions, produced by one shared audio engine (scripts/audio.mjs) — multi-provider TTS (HeyGen / ElevenLabs / Kokoro local), background music + sound…

    299 GitHub starsUsed in 1 repo~2.8k tokens
    Auto-check: notes

  • Remotion To Hyperframes

    chmonitor/chmonitor

    Port an existing Remotion (React) composition to HyperFrames HTML.

    299 GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed

  • Music To Video

    chmonitor/chmonitor

    A skill your agent uses when the user has a music track (an audio file, or a video to pull audio from) and wants a beat-synced HyperFrames video, calm to hard-hitting.

    299 GitHub starsUsed in 1 repo~4k tokens
    Auto-check: notes

  • Hyperframes Animation

    chmonitor/chmonitor

    All animation knowledge for HyperFrames — atomic motion rules, multi-phase scene blueprints, scene transitions, broader motion-design techniques, AND the seven runtime adapters (GSAP default, plus…

    299 GitHub starsUsed in 2 repos~1.8k tokens
    Auto-check passed

  • Faceless Explainer

    chmonitor/chmonitor

    turn arbitrary text — an article, notes, a topic, a brief — into a faceless explainer video, up to ~3 min (sweet spot 30-90s), where every visual is invented (typography, abstract graphics…

    299 GitHub stars~4.5k tokensUpdated 2 days ago
    Auto-check: notes

Works with

Categories

Questions about Hyperframes CLI

What does Hyperframes CLI do?

HyperFrames CLI dev loop. An agent skill from chmonitor/chmonitor. Hyperframes CLI is an agent skill from chmonitor/chmonitor. HyperFrames CLI dev loop.

When should I use Hyperframes CLI?

Hyperframes CLI fits situations like: running npx hyperframes init; remove-background; troubleshooting the HyperFrames build/render environment.

How do I install Hyperframes CLI in Claude Code?

Run `npx skills add chmonitor/chmonitor --skill hyperframes-cli -a claude-code`. Or copy the skill folder (.agents/skills/hyperframes-cli in chmonitor/chmonitor) into .claude/skills/hyperframes-cli in your project. Claude Code loads it when a task matches its description.

How do I install Hyperframes CLI in Codex?

Run `npx skills add chmonitor/chmonitor --skill hyperframes-cli -a codex`. Or copy the skill folder (.agents/skills/hyperframes-cli in chmonitor/chmonitor) into .agents/skills/hyperframes-cli in your project. Codex loads it when a task matches its description.

Can I use Hyperframes CLI in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add chmonitor/chmonitor --skill hyperframes-cli -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/hyperframes-cli, .gemini/skills/hyperframes-cli, .github/skills/hyperframes-cli and .opencode/skills/hyperframes-cli in your project.

What does Hyperframes CLI need to run?

Going by SKILL.md and its folder, Hyperframes CLI needs the command-line tools its instructions call (npx, jq and ffprobe). Our summary lists: Node.js; Docker.

Does Hyperframes CLI access the network?

SKILL.md contains no URLs. Its commands use npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Hyperframes CLI safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Hyperframes CLI use?

Hyperframes CLI is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Hyperframes CLI use?

About 2.3k tokens (SKILL.md is roughly 9.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 11k tokens, read only when the agent opens those files.

What are the alternatives to Hyperframes CLI?

Skills that share tags, products or a category with Hyperframes CLI: HyperFrames CLI Workflow (heygen-com/hyperframes, 59k stars), Hyperframes CLI (aiskillstore/marketplace, 430 stars), HyperFrames Animation (heygen-com/hyperframes, 59k stars) and HyperFrames Video Entry Point (heygen-com/hyperframes, 59k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Hyperframes CLI?

chmonitor (a GitHub organization) maintains it in chmonitor/chmonitor, which has 299 GitHub stars. The repository holds 53 skills in this directory. The repository was last updated on October 5, 2026.

Source: chmonitor/chmonitor on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.