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.
The standard for writing new skills for the AI Edit Video system - file structure, frontmatter, tone of voice, and how to accumulate production lessons into skills.
Install Skill Authoring
$ npx skills add notivn/AIEV --skill skill-authoring -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install notivn/AIEV skill-authoring --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/notivn/AIEV.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/skill-authoring .claude/skills/skill-authoring && 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 "skill-authoring" agent skill from https://github.com/notivn/AIEV/tree/main/.claude/skills/skill-authoring into .claude/skills/skill-authoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-authoring", 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/notivn/AIEV/tree/main/.claude/skills/skill-authoringType 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 notivn/AIEV --skill skill-authoring -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install notivn/AIEV skill-authoring --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/notivn/AIEV.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/skill-authoring .agents/skills/skill-authoring && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "skill-authoring" agent skill from https://github.com/notivn/AIEV/tree/main/.claude/skills/skill-authoring into .agents/skills/skill-authoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-authoring", 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 notivn/AIEV --skill skill-authoring -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install notivn/AIEV skill-authoring --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/notivn/AIEV.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/skill-authoring .cursor/skills/skill-authoring && 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 "skill-authoring" agent skill from https://github.com/notivn/AIEV/tree/main/.claude/skills/skill-authoring into .cursor/skills/skill-authoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-authoring", 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/notivn/AIEV.git --path .claude/skills/skill-authoring--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 notivn/AIEV --skill skill-authoring -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install notivn/AIEV skill-authoring --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/notivn/AIEV.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/skill-authoring .gemini/skills/skill-authoring && 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 "skill-authoring" agent skill from https://github.com/notivn/AIEV/tree/main/.claude/skills/skill-authoring into .gemini/skills/skill-authoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-authoring", 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 notivn/AIEV skill-authoringInstalls 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 notivn/AIEV --skill skill-authoring -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/notivn/AIEV.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/skill-authoring .github/skills/skill-authoring && 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 "skill-authoring" agent skill from https://github.com/notivn/AIEV/tree/main/.claude/skills/skill-authoring into .github/skills/skill-authoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-authoring", 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 notivn/AIEV --skill skill-authoring -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install notivn/AIEV skill-authoring --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/notivn/AIEV.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/skill-authoring .opencode/skills/skill-authoring && 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 "skill-authoring" agent skill from https://github.com/notivn/AIEV/tree/main/.claude/skills/skill-authoring into .opencode/skills/skill-authoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-authoring", 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
skill-authoring- GitHub stars
- 126
- Token cost
- ~925 tokens
- SKILL.md length
- 471 words
- Files
- 1
- Skills in repo
- 14
- Repo updated
- First seen
- Licence
- MIT
At a glance
The standard for writing new skills for the AI Edit Video system - file structure, frontmatter, tone of voice, and how to accumulate production lessons into skills.
- Works in 6 steps: The description decides everything.… → Write for the next use, not as a… → Every fix needs its recognition… → …
- Asks to create a new skill (via chat
- SKILL.md covers Required structure, Writing rules, When to CREATE a new skill vs… and Creating a skill from the web UI, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Skill Authoring is an agent skill from notivn/AIEV. The standard for writing new skills for the AI Edit Video system - file structure, frontmatter, tone of voice, and how to accumulate production lessons into skills. Read when the user asks to create a new skill (via chat or from the Skills page in the web UI) or when updating a skill after finishing a video.
Its SKILL.md is about 930 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Media & Creative, covering Skill authoring, Video production and Frontend development. It works with Remotion. The repository describes itself as: Automatic AI video editing. Claude directs HyperFrames (HTML + GSAP motion graphics) and Remotion (timeline assembly) to turn raw footage into a finished MP4 - transcript… The licence is MIT.
When your agent uses it
- Asks to create a new skill (via chat
- From the Skills page in the web UI)
- Updating a skill after finishing a video
Example prompts
- “/skill-authoring”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- The description decides everything. Claude only sees the description when choosing a skill - it must spell out the trigger situation…
- Write for the next use, not as a souvenir. Every section must answer "what do I do differently next time". Do not transcribe debugging…
- Every fix needs its recognition condition. The standard template for a lesson
- Specific beats exhaustive. A runnable command > a general description. Concrete numbers (CRF 28, volume 0.3, stroke 1.5px) > adjectives…
- Write skills in English; keep code/commands/technical names as-is. Do not translate technical terms (frame, render, timeline...)…
- One skill, one topic. Split a skill once it grows past ~200 lines. Reference other skills by name (see the remotion-assemble skill)…
What it can do on your machine
Read from SKILL.md and the folder at commit 1a4c2b0. 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 markdown).
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
Skill Authoring loads about 925 tokens when it runs. Until then it costs about 81 tokens; SKILL.md has 471 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 notivn/AIEV at commit 1a4c2b0, republished under its MIT licence (© notivn). 471 words, ~925 tokens.
Download SKILL.mdSave it as
.claude/skills/skill-authoring/SKILL.md (or your agent's skills folder).- name
- skill-authoring
- description
- The standard for writing new skills for the AI Edit Video system - file structure, frontmatter, tone of voice, and how to accumulate production lessons into skills. Read when the user asks to create a new skill (via chat or from the Skills page in the web UI) or when updating a skill after finishing a video.
Skill Authoring - writing skills the right way
Skills are where production know-how accumulates. A good skill makes the next video automatically better than the last one without having to repeat anything in chat.
Required structure
.claude/skills/<name-kebab-case>/
└── SKILL.md---
name: <matches the folder name, kebab-case>
description: <1-2 sentences: what the skill does + WHEN to use it. Claude decides whether to load the skill from this line alone - be specific, include keywords>
---
# Title
<skill body>Writing rules
- The description decides everything. Claude only sees the description when choosing a skill - it must spell out the trigger situation: "Read when...", "Use when the user provides...". A vague description = a skill that never gets used.
- Write for the next use, not as a souvenir. Every section must answer "what do I do differently next time". Do not transcribe debugging history - keep only the conclusion + how to apply it.
- Every fix needs its recognition condition. The standard template for a lesson:
- Symptom: Vietnamese gradient text loses its diacritics on the reveal frame
- Cause:
background-clip: textclips the diacritics that sit outside the line-box - Fix: add enough
padding-top+line-heightto contain the diacritics, then check the first/last frame of the reveal
- Specific beats exhaustive. A runnable command > a general description. Concrete numbers (CRF 28, volume 0.3, stroke 1.5px) > adjectives ("appropriate", "moderate").
- Write skills in English; keep code/commands/technical names as-is. Do not translate technical terms (frame, render, timeline...). Vietnamese strings that are literal data (sample captions, UI labels, on-screen text) stay verbatim.
- One skill, one topic. Split a skill once it grows past ~200 lines. Reference other skills by name (
see the remotion-assemble skill) instead of copying content across files.
Show full SKILL.md (230 more words)Show less
When to CREATE a new skill vs UPDATE an existing one
| Situation | What to do |
|---|---|
| A new repeatable video format (e.g. product comparison video) | Create a new skill, cloned from the closest existing one |
| Fixing a bug in a workflow that already has a skill | Update that skill, in its "Known issues" section |
| A new aesthetic/brand rule | Update webui-design (UI) or the relevant video format skill (video) |
| Knowledge that only applies to one specific video | DO NOT put it in a skill - write it in that project's NOTES.md |
Creating a skill from the web UI
When the user creates a skill through the Skills page (describing it in their own words, often in Vietnamese):
- Read this skill plus the closest existing skill of the same kind as a template.
- Write a full
SKILL.mdin English, with complete frontmatter, following the rules above. - If the skill relates to Vietnamese-language video: inherit the verified fixes (Vietnamese diacritics, ffmpeg PATH) by reference, do not copy them.
- Return it to the UI as a draft for the user to approve before writing the file.
After every finished video
Ask yourself: is there a new symptom -> cause -> fix? Was there a step done manually more than twice (the sign it should become a skill)? If so, update the skill in that same session - do not defer it to the next one.
© notivn, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .claude/skills/skill-authoring of notivn/AIEV.
Open the folder on GitHubat commit 1a4c2b0
Compare with similar skills
Skill Authoring 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 |
|---|---|---|---|---|---|---|
| Skill Authoring this skillnotivn/AIEV | 126 | — | ~925 | Automated safety check: Pass | MIT | |
| HyperFrames Video Entry Pointheygen-com/hyperframes | 59k | 3 repos | ~5.2k | Automated safety check: Pass | Apache-2.0 | |
| Create Remotion GeistMarve10s/Better-Fullstack | 752 | — | ~1.4k | Automated safety check: Pass | MIT | |
| Remotion Toolkit Extensionsdigitalsamba/claude-code-video-toolkit | 2.2k | 1 repos | ~1.5k | Automated safety check: Pass | MIT | |
| Stitch to Remotion Walkthrough Videosgoogle-labs-code/stitch-skills | 8.4k | 6 repos | ~3.2k | Automated safety check: Notes | Apache-2.0 | |
| Video ShotcraftVincentwei1021/video-shotcraft | 11k | — | ~2.6k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Create Remotion Geist
Marve10s/Better-Fullstack
Create Remotion videos using the Geist design system aesthetic.
Remotion Toolkit Extensions
digitalsamba/claude-code-video-toolkit
Toolkit-specific Remotion pieces for video projects: shared scene components, custom transitions such as glitch and light leak, and project conventions beside the official skill.
- Official
Stitch to Remotion Walkthrough Videos
google-labs-code/stitch-skills
Builds walkthrough videos from Stitch design projects using Remotion, with transitions, zoom effects and text overlays on each screen.
Video Shotcraft
Vincentwei1021/video-shotcraft
Makes cinematic product videos with Remotion from shot recipe cards, a ready template, real page screenshots, camera moves and sound design, or builds a single animated shot.
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.
More from notivn/AIEV
All 14 skills in this repoBackground Music
notivn/AIEV
Pick background music from the assets/music/ library and configure auto-ducking (music dips automatically under speech) via meta.json audio.music for the Remotion assembly layer.
Color Grading
notivn/AIEV
Color grading video in the AI Edit Video system - delog/tonemap HDR-HLG-log footage, apply the color preset the user approved in the UI, and the visual verification workflow.
Noti Tiktok Full Text
notivn/AIEV
Build a Vietnamese vertical TikTok explainer in the "MỔ XẺ PAPER AI" (AI paper dissection) format with HyperFrames (HTML/CSS/GSAP → MP4), Noti.vn style.
Noti Tiktok Vn
notivn/AIEV
Edit a Vietnamese vertical TikTok video (9:16) with HyperFrames following the Noti.vn/GĐT standard - talking-head + kinetic typography + karaoke captions + zoom/punch-in camera + timestamp-synced…
Noti Youtube Edit
notivn/AIEV
Build a Vietnamese landscape 16:9 YouTube video (1920×1080) with HyperFrames (HTML/CSS/GSAP → MP4), keeping the Noti.vn/GĐT branding inherited from noti-tiktok-vn.
Short Form Video
notivn/AIEV
Build and iterate short-form vertical (9:16) videos in Hyperframes - TikTok/Reels/Shorts style.
Related
Works with
Categories
Questions about Skill Authoring
What does Skill Authoring do?
The standard for writing new skills for the AI Edit Video system - file structure, frontmatter, tone of voice, and how to accumulate production lessons into skills. Skill Authoring is an agent skill from notivn/AIEV. The standard for writing new skills for the AI Edit Video system - file structure, frontmatter, tone of voice, and how to accumulate production lessons into skills.
When should I use Skill Authoring?
Skill Authoring fits situations like: asks to create a new skill (via chat; from the Skills page in the web UI); updating a skill after finishing a video.
How do I install Skill Authoring in Claude Code?
Run `npx skills add notivn/AIEV --skill skill-authoring -a claude-code`. Or copy the skill folder (.claude/skills/skill-authoring in notivn/AIEV) into .claude/skills/skill-authoring in your project. Claude Code loads it when a task matches its description.
How do I install Skill Authoring in Codex?
Run `npx skills add notivn/AIEV --skill skill-authoring -a codex`. Or copy the skill folder (.claude/skills/skill-authoring in notivn/AIEV) into .agents/skills/skill-authoring in your project. Codex loads it when a task matches its description.
Can I use Skill Authoring 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 notivn/AIEV --skill skill-authoring -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/skill-authoring, .gemini/skills/skill-authoring, .github/skills/skill-authoring and .opencode/skills/skill-authoring in your project.
What does Skill Authoring need to run?
SKILL.md names no scripts, command-line tools or credentials: Skill Authoring is instructions for the agent only.
Does Skill Authoring 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 Skill Authoring 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 Skill Authoring use?
Skill Authoring 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 Skill Authoring use?
About 925 tokens (SKILL.md is roughly 3.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Skill Authoring?
Skills that share tags, products or a category with Skill Authoring: HyperFrames Video Entry Point (heygen-com/hyperframes, 59k stars), Create Remotion Geist (Marve10s/Better-Fullstack, 752 stars), Remotion Toolkit Extensions (digitalsamba/claude-code-video-toolkit, 2.2k stars) and Stitch to Remotion Walkthrough Videos (google-labs-code/stitch-skills, 8.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Skill Authoring?
notivn (a GitHub organization) maintains it in notivn/AIEV, which has 126 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on October 8, 2026.
Source: notivn/AIEV on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.