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.
A skill your agent uses when developing a content-driven video from a topic, research bundle, article, or draft, or when routing an existing script or non-argument video into HyperFrames production.
Install Boring Video
$ npx skills add sugarforever/boring-video-studio --skill boring-video -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install sugarforever/boring-video-studio boring-video --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/sugarforever/boring-video-studio.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/boring-video/boring-video .claude/skills/boring-video && rm -rf skills-srcUse ~/.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/
Install the "boring-video" agent skill from https://github.com/sugarforever/boring-video-studio/tree/main/skills/boring-video/boring-video into .claude/skills/boring-video/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "boring-video", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/sugarforever/boring-video-studio/tree/main/skills/boring-video/boring-videoType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add sugarforever/boring-video-studio --skill boring-video -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install sugarforever/boring-video-studio boring-video --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sugarforever/boring-video-studio.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/boring-video/boring-video .agents/skills/boring-video && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "boring-video" agent skill from https://github.com/sugarforever/boring-video-studio/tree/main/skills/boring-video/boring-video into .agents/skills/boring-video/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "boring-video", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add sugarforever/boring-video-studio --skill boring-video -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install sugarforever/boring-video-studio boring-video --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sugarforever/boring-video-studio.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/boring-video/boring-video .cursor/skills/boring-video && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "boring-video" agent skill from https://github.com/sugarforever/boring-video-studio/tree/main/skills/boring-video/boring-video into .cursor/skills/boring-video/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "boring-video", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/sugarforever/boring-video-studio.git --path skills/boring-video/boring-video--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add sugarforever/boring-video-studio --skill boring-video -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install sugarforever/boring-video-studio boring-video --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sugarforever/boring-video-studio.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/boring-video/boring-video .gemini/skills/boring-video && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "boring-video" agent skill from https://github.com/sugarforever/boring-video-studio/tree/main/skills/boring-video/boring-video into .gemini/skills/boring-video/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "boring-video", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install sugarforever/boring-video-studio boring-videoInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add sugarforever/boring-video-studio --skill boring-video -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/sugarforever/boring-video-studio.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/boring-video/boring-video .github/skills/boring-video && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "boring-video" agent skill from https://github.com/sugarforever/boring-video-studio/tree/main/skills/boring-video/boring-video into .github/skills/boring-video/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "boring-video", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add sugarforever/boring-video-studio --skill boring-video -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install sugarforever/boring-video-studio boring-video --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sugarforever/boring-video-studio.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/boring-video/boring-video .opencode/skills/boring-video && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "boring-video" agent skill from https://github.com/sugarforever/boring-video-studio/tree/main/skills/boring-video/boring-video into .opencode/skills/boring-video/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "boring-video", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
boring-video- GitHub stars
- 168
- Token cost
- ~1.2k tokens
- SKILL.md length
- 566 words
- Files
- 2 (incl. references)
- Skills in repo
- 11
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when developing a content-driven video from a topic, research bundle, article, or draft, or when routing an existing script or non-argument video into HyperFrames production.
- Works in 4 steps: Presentation: faceless, footage, screen… → Collaboration: storyboard reviews or… → Voice: HyperFrames voice, ListenHub TTS,… → …
- Developing a content-driven video from a topic
- SKILL.md covers Intake, Chain, Handoff and Done
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Boring Video is an agent skill from sugarforever/boring-video-studio. Use when developing a content-driven video from a topic, research bundle, article, or draft, or when routing an existing script or non-argument video into HyperFrames production.
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/hyperframes-review-project.md`).
It sits in Media & Creative, covering Motion graphics. It works with HeyGen. The repository describes itself as: 小木头的个人视频流水线 Agent Skill - VerySmallWoods Video. The licence is MIT.
When your agent uses it
- Developing a content-driven video from a topic
- Research bundle
- Routing an existing script
- Non-argument video into HyperFrames production
Example prompts
- “/boring-video”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Presentation: faceless, footage, screen capture, talking head, or mixed media?
- Collaboration: storyboard reviews or agent-executed production with final preview?
- Voice: HyperFrames voice, ListenHub TTS, user recording, or no narration?
- Design: existing design truth, named direction, or agent-proposed direction?
What it can do on your machine
Read from SKILL.md and the folder at commit f3445d6. 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
No scripts in the folder and no shell commands in SKILL.md (its code samples are yaml).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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
Boring Video loads about 1.2k tokens when it runs, and up to ~2.3k if it reads all its reference files. Until then it costs about 48 tokens; SKILL.md has 566 words of instructions outside code blocks.
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 sugarforever/boring-video-studio at commit f3445d6, republished under its MIT licence (© sugarforever). 566 words, ~1,227 tokens.
Download SKILL.mdSave it as
.claude/skills/boring-video/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- boring-video
- description
- Use when developing a content-driven video from a topic, research bundle, article, or draft, or when routing an existing script or non-argument video into HyperFrames production.
Boring video
Orchestrate content development and a progressively refined HyperFrames project as one chain. Content is established before it is adapted for speech or visuals; scene direction begins the renderable project, storyboard turns it into an animatic, and production continues it.
Intake
Resolve existing decisions from the request and project files. First classify the input:
- Content-driven: research, evaluation, analysis, opinion, tutorial, news, profile, or another narrated work whose value depends on a complete argument and may also become a blog article.
- Direct-production: a locked script, product promo, UI demonstration, music-led piece, short motion graphic, or another work that does not need an article to establish its meaning.
For content-driven work, locate the first missing approved content artifact. A supplied article counts only when the user explicitly confirms it as the content master. Store or adapt it as content/ARTICLE.md with this provenance:
---
source: external
origin: <URL or path>
origin_revision: <Git revision, source digest, or captured-at timestamp>
status: approved
approved_at: YYYY-MM-DD
approved_digest: sha256:<digest>
voice:
language: ...
skills: []
documents: []
unavailable: []
status: resolved | assumed
---Compute approved_digest as SHA-256 of the complete file after removing only the approved_digest: line. Do not manufacture an article merely to satisfy the chain for direct-production work; load /hyperframes and let its current intent layer own intake and workflow selection.
When this intake creates or adapts content/ARTICLE.md, REQUIRED SUB-SKILL: Use artifact-preview for that file and satisfy its completion criterion for content/ARTICLE.preview.html before starting /to-spec-beats.
For content-driven work, ask one compact question for any missing production choices:
- Presentation: faceless, footage, screen capture, talking head, or mixed media?
- Collaboration: storyboard reviews or agent-executed production with final preview?
- Voice: HyperFrames voice, ListenHub TTS, user recording, or no narration?
- Design: existing design truth, named direction, or agent-proposed direction?
Record the answers in the HyperFrames BRIEF.md. In agent-executed work, propose and record a design direction when the user leaves it open. Direct-production work skips this wrapper intake because /hyperframes owns that brief.
Show full SKILL.md (274 more words)Show less
Chain
Before /to-scenes starts the renderable project, read references/hyperframes-review-project.md. Pass its project identity and review state forward through SCENES.md, STORYBOARD.md, and the HyperFrames project manifest; downstream skills consume those artifacts rather than this internal reference.
For content-driven work, start at the first missing or explicitly revised artifact:
/develop-topic→content/RESEARCH.md, experiment reports, and approvedcontent/TOPIC.md/to-article→ approvedcontent/ARTICLE.md/to-spec-beats→BEATS.md/to-narration→NARRATION.md/to-scenes→SCENES.md, shared HyperFrames project, and visual direction board/to-storyboard→STORYBOARD.mdand a full animatic in that project/to-video→ production continuation in that project
Finish each skill's completion criterion before advancing. A downstream finding returns to the artifact that owns the decision, then propagates forward.
When the user begins with an approved complete article, recompute its digest before starting at /to-spec-beats. When they begin with later content-driven artifacts, recompute every present artifact digest, require each child to carry the current digest of its immediate parent, and verify that the chain traces to an approved content/ARTICLE.md; then resume at the first missing stage. Artifact existence alone is not resumable state. Direct-production inputs bypass this content chain and begin at /hyperframes; never reinterpret a locked script as permission to invent an article, thesis, or claims.
Handoff
Presentation and workflow are separate decisions. Collect the presentation intent without selecting a workflow from memory. /to-video reads the current /hyperframes contract and performs the route.
Done
Content-driven planning is complete when the applicable approved content artifacts, four planning artifacts, direction board, and seekable animatic agree and satisfy their owners. The wrapper run is complete when /to-video continues the reviewed HyperFrames project with the confirmed voice branch through the selected production workflow.
© sugarforever, MIT. 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 1 other file (references) in skills/boring-video/boring-video of sugarforever/boring-video-studio.
- SKILL.md
- references/hyperframes-review-project.md
Open the folder on GitHubat commit f3445d6
Compare with similar skills
Boring Video 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Boring Video this skillsugarforever/boring-video-studio | 168 | — | ~1.2k | Automated safety check: Pass | MIT | |
| HyperFrames Animationheygen-com/hyperframes | 60k | 3 repos | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| Faceless Explainer Videoheygen-com/hyperframes | 60k | 3 repos | ~7.7k | Automated safety check: Notes | Apache-2.0 | |
| Figma to HyperFramesheygen-com/hyperframes | 60k | 3 repos | ~4.5k | Automated safety check: Notes | Apache-2.0 | |
| HyperFrames Video Entry Pointheygen-com/hyperframes | 60k | 3 repos | ~5.2k | Automated safety check: Pass | Apache-2.0 | |
| Media Useedenfunf/reelmimic | 1.9k | 1 repos | ~2k | Automated safety check: Pass | MIT |
Similar skills
Faceless Explainer Video
heygen-com/hyperframes
Turns an article, notes or a topic brief into an explainer video whose visuals are invented per scene, built frame by frame in HyperFrames with no footage.
Figma to HyperFrames
heygen-com/hyperframes
Imports Figma assets, brand tokens, components and motion into a HyperFrames video composition, using the Figma REST API with a connector or native export for shaders.
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.
Media Use
edenfunf/reelmimic
Agent Media OS, the single skill for every media need in a HyperFrames project.
Hyperframes
boraoztunc/skills
Create video compositions, animations, title cards, overlays, captions, voiceovers, audio-reactive visuals, and scene transitions in HyperFrames HTML.
More from sugarforever/boring-video-studio
All 12 skills in this repoDevelop Topic
sugarforever/boring-video-studio
A skill your agent uses when a content-driven video has a candidate topic but still needs research, experiments, a defensible thesis, or user-approved scope before an article or video beats can be…
Setup Boring Video Skills
sugarforever/boring-video-studio
A skill your agent uses when installing, validating, or repairing the Boring Video planning skill set before its first use.
To Article
sugarforever/boring-video-studio
A skill your agent uses when an approved content topic, research bundle, and evidence need to become a complete platform-independent article before video beats or publication adaptation.
Artifact Preview
sugarforever/boring-video-studio
A skill your agent uses when an artifact-owning skill requires a durable Markdown file to be presented for user review in a coding agent.
To Narration
sugarforever/boring-video-studio
A skill your agent uses when writing or revising spoken narration from complete, lineage-valid video beats, including scripts that must remain open to later visual direction.
To Spec Beats
sugarforever/boring-video-studio
A skill your agent uses when an approved content article needs to be reorganized into the factual and narrative architecture for a narrated video.
Related
Works with
Categories
Questions about Boring Video
What does Boring Video do?
A skill your agent uses when developing a content-driven video from a topic, research bundle, article, or draft, or when routing an existing script or non-argument video into HyperFrames production. Boring Video is an agent skill from sugarforever/boring-video-studio. Use when developing a content-driven video from a topic, research bundle, article, or draft, or when routing an existing script or non-argument video into HyperFrames production.
When should I use Boring Video?
Boring Video fits situations like: developing a content-driven video from a topic; research bundle; routing an existing script; non-argument video into HyperFrames production.
How do I install Boring Video in Claude Code?
Run `npx skills add sugarforever/boring-video-studio --skill boring-video -a claude-code`. Or copy the skill folder (skills/boring-video/boring-video in sugarforever/boring-video-studio) into .claude/skills/boring-video in your project. Claude Code loads it when a task matches its description.
How do I install Boring Video in Codex?
Run `npx skills add sugarforever/boring-video-studio --skill boring-video -a codex`. Or copy the skill folder (skills/boring-video/boring-video in sugarforever/boring-video-studio) into .agents/skills/boring-video in your project. Codex loads it when a task matches its description.
Can I use Boring Video 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 sugarforever/boring-video-studio --skill boring-video -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/boring-video, .gemini/skills/boring-video, .github/skills/boring-video and .opencode/skills/boring-video in your project.
What does Boring Video need to run?
SKILL.md names no scripts, command-line tools or credentials: Boring Video is instructions for the agent only.
Does Boring Video access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Boring Video 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 Boring Video use?
Boring Video is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Boring Video use?
About 1.2k tokens (SKILL.md is roughly 4.9k 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 1.1k tokens, read only when the agent opens those files.
What are the alternatives to Boring Video?
Skills that share tags, products or a category with Boring Video: HyperFrames Animation (heygen-com/hyperframes, 60k stars), Faceless Explainer Video (heygen-com/hyperframes, 60k stars), Figma to HyperFrames (heygen-com/hyperframes, 60k stars) and HyperFrames Video Entry Point (heygen-com/hyperframes, 60k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Boring Video?
sugarforever (a GitHub user) maintains it in sugarforever/boring-video-studio, which has 168 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on October 9, 2026.
Source: sugarforever/boring-video-studio on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.