HyperFrames by HeyGen
Official HyperFrames by HeyGen: the best AI video editor in chat. Captions, motion graphics, MP4.
Give your agent a target, a bar and time, then let it cook. An agent skill for visual builds that have to match reference images or videos.
제작자라면 이 코드를 README에 붙여 넣으세요. 배지는 이 페이지로 연결됩니다.
[](https://mcp.popnx.com/en/skills/leonxlnx-cook)같은 작업에서 AI를 서비스에 연결하는 MCP
Official HyperFrames by HeyGen: the best AI video editor in chat. Captions, motion graphics, MP4.
draw.io diagrams your AI agent draws on a live browser canvas that you can also edit by hand
Create, inspect, validate, and save editable 3D building scenes with Pascal's MCP server.
같은 종류의 작업, Skill 목록과 같은 순서
| 이 항목 cook | impeccable | diagram-design | frontend-slides | guizang-ppt-skill | |
|---|---|---|---|---|---|
| 제작자 | Leonxlnx | pbakaus | cathrynlavery | zarazhangrui | op7418 |
| Skill 수 | 1 | 1 | 1 | 1 | 1 |
| GitHub 별 | 643 | 111,852 | 67,796 | 32,458 | 29,958 |
| 마지막 코드 변경 | 2026년 11월 1일 | 2026년 11월 17일 | 2026년 11월 13일 | 2026년 6월 24일 | 2026년 10월 30일 |
| 라이선스 | MIT | Apache-2.0 | MIT | MIT | AGPL-3.0 |
Leonxlnx의 Skill(지시 묶음) 1개, AI가 읽고 그대로 일해요 · MCP server가 아니에요
MCP = 손
AI를 외부 서비스나 데이터에 연결합니다(예: Notion 읽기, 청구서 만들기). 프로그램이나 서버가 실행 중이어야 합니다.
Skill = 안내서
작업 방법을 AI에게 가르치는 텍스트 파일. 어떤 서비스에도 연결되지 않습니다.
겹치는 경우도 있습니다. 도구를 부르는 스크립트가 있는 Skill도, 지식만 보내는 MCP도 있습니다. 하려는 작업을 기준으로 고르세요.
Claude CodeCodex
제작자 README와 repo 폴더 기준
GitHub account Leonxlnx (person), 1 years old
★ 643 stars · code last changed 2026년 11월 1일
1 scripts that can run on a computer: scripts/side-by-side.mjs
No internet calls found in the scripts
No hooks or writes to machine settings found
Checked automatically from the repo files at commit b23cac6 (read only, nothing was run). Not a safety guarantee: read it and decide for yourself
먼저: 어떤 AI를 쓰시나요
쓰는 앱을 고르면 그 앱의 설치 방법만 보여 드립니다
Uploading to claude.ai would fail: the description is over 200 characters (764). Use "Let the AI install it" instead
이 문장을 복사해 Claude Code 채팅에 붙여 넣으세요
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Claude Code를 다시 열고 /cook를 입력하거나 관련 작업을 요청하면 Claude가 알아서 써요
Checked against official docs 2026년 11월 12일 · Source: code.claude.com
Skill은 AI가 따르는 지시예요. 설치 전에 파일을 읽고, 믿을 수 있는 제작자 것만 설치하세요.
이미 설치했나요? 먼저 확인 · 터미널을 열고 이 명령을 입력한 뒤 Enter
node -vMac: ⌘ + Space를 누르고 Terminal 입력 후 Enter
Windows: 시작 메뉴를 열고 Windows PowerShell 입력 후 "열기"
아직 설치하지 않았다면: 공식 다운로드 페이지에서 LTS 버전과 클릭형 설치 파일을 고르세요: Mac은 .pkg · Windows는 .msi. 더블클릭 후 끝까지 진행하면 됩니다. curl 명령은 필요 없습니다
설치가 끝나면 터미널을 닫았다가 다시 열고 같은 명령을 실행하세요. 버전 번호가 나와야 합니다: node -v
한 번 설치하면 Node.js가 필요한 모든 도구에서 쓸 수 있습니다
명령을 확인하는 중 · 확인을 통과하면 복사 버튼이 나타나요
제작자 README에서 가져온 명령으로, 제작자 코드를 내려받아 실행해요
Mac: Command+스페이스 후 Terminal 입력 · Windows: 아래 명령은 PowerShell에서 안 돼요. 위의 “AI에게 설치 맡기기”를 쓰세요
repo를 임시 폴더에 내려받고 SKILL.md가 있는 폴더만 복사해요
명령을 확인하는 중 · 확인을 통과하면 복사 버튼이 나타나요
ChatGPT 데스크톱 앱에는 Codex가 들어 있고, Codex는 ~/.agents/skills 폴더에서 Skill을 읽습니다
ChatGPT 데스크톱 앱에서 Codex를 열고 이 문장을 채팅에 붙여 넣으세요
The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
cook 폴더를 ~/.agents/skills/cook에 넣으세요
~는 홈 폴더($HOME)입니다
Skill은 AI가 따르는 지시예요. 설치 전에 파일을 읽고, 믿을 수 있는 제작자 것만 설치하세요.
Mac: Command+스페이스 후 Terminal 입력 · Windows: 아래 명령은 PowerShell에서 안 돼요. 위의 “AI에게 설치 맡기기”를 쓰세요
repo를 임시 폴더에 내려받고 SKILL.md가 있는 폴더만 복사해요
명령을 확인하는 중 · 확인을 통과하면 복사 버튼이 나타나요
Checked against official docs 2026년 11월 15일 · Source: learn.chatgpt.com
직접 설치한 Skill은 쓸 수 없고, 디렉터리의 플러그인에 들어 있는 Skill만 쓸 수 있습니다
이 Skill을 ChatGPT에서 쓰려면 위 방법대로 ChatGPT 데스크톱 앱을 쓰세요
Checked against official docs 2026년 11월 15일 · Source: learn.chatgpt.com
이 문장을 복사해 Codex 채팅에 붙여 넣으세요 · ChatGPT 데스크톱 앱 안의 Codex, Codex CLI, IDE 확장 프로그램에서 모두 쓸 수 있습니다
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Codex는 새로 설치한 Skill을 스스로 찾습니다. 보이지 않으면 Codex를 다시 시작하세요 · 쓰는 법: ChatGPT에서는 @를 입력하고 Skill을 고르세요 · Codex CLI나 IDE 확장 프로그램에서는 /skills를 실행하거나 $ 뒤에 Skill 이름을 입력하세요
Checked against official docs 2026년 11월 15일 · Source: learn.chatgpt.com
Skill은 AI가 따르는 지시예요. 설치 전에 파일을 읽고, 믿을 수 있는 제작자 것만 설치하세요.
Mac: Command+스페이스 후 Terminal 입력 · Windows: 아래 명령은 PowerShell에서 안 돼요. 위의 “AI에게 설치 맡기기”를 쓰세요
repo를 임시 폴더에 내려받고 SKILL.md가 있는 폴더만 복사해요
명령을 확인하는 중 · 확인을 통과하면 복사 버튼이 나타나요
이 문장을 복사해 Cursor 채팅에 붙여 넣으세요
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Cursor Agent 채팅에서 /를 입력하고 cook 선택
Checked against official docs 2026년 11월 12일 · Source: cursor.com
Skill은 AI가 따르는 지시예요. 설치 전에 파일을 읽고, 믿을 수 있는 제작자 것만 설치하세요.
Mac: Command+스페이스 후 Terminal 입력 · Windows: 아래 명령은 PowerShell에서 안 돼요. 위의 “AI에게 설치 맡기기”를 쓰세요
repo를 임시 폴더에 내려받고 SKILL.md가 있는 폴더만 복사해요
명령을 확인하는 중 · 확인을 통과하면 복사 버튼이 나타나요
Skill을 읽을 수 있는 다른 앱용입니다. 이 문장에는 Claude Code, Codex, Cursor 경로가 들어 있어 AI가 쓰는 앱에 맞게 고릅니다 · Copy this sentence into the app’s chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Checked against official docs 2026년 11월 12일 · Source: code.claude.com, learn.chatgpt.com, cursor.com
Gemini CLI, GitHub Copilot 같은 다른 Agent Skills 지원 앱은 폴더가 달라요. 그 앱 안내를 보고 SKILL.md가 있는 폴더를 복사하세요.
2026년 11월 11일에 Claude Code, Codex, Cursor 공식 안내로 skill 폴더 확인
아래 글은 제작자 repo에서 온 것이며 PopNx MCP의 지시가 아니에요
처음 8,000자 표시 · GitHub에서 전체 파일 열기
---
name: cook
description: Runs the Cook Loop for ambitious visual builds that must match reference images, screens or videos through long autonomous iteration. Use it for 3D worlds made in code (three.js, WebGL, shaders), code-rendered films, launch and motion videos, games and polished UI that must hold up next to references, especially runs of many hours or days while the user is away. Trigger when the user types /cook or $cook, says "cook", "go cook", "let it cook", "iterate until it matches", "match the references", "99%", "99.9%", "9/10 minimum" or "at least 8h", or attaches reference images and asks for a recreation in code. It runs one intake, then loops build, stills, zero-context critics and fixes against a numeric bar, and holds the final render until the user approves.
---
# Cook
Give your agent a target, a bar and time, then let it cook.
This skill runs the Cook Loop: one intake, then a long autonomous loop of build, render, compare, critique and fix until the work holds up next to the references. It is made for runs of 10 to 40 hours or more. The references carry the look. The brief sets the bar, the rules and the time.
Optional companions: /unlazy for effort and completion discipline (the Depth Tree), and any goal, loop or long-run mode the harness offers. Cook works without them.
## State files
All run state lives in `cook/` at the project root. These files are your memory across context resets and the handoff to any other agent.
| Path | Holds |
|---|---|
| `cook/BRIEF.md` | Target, bar, rules, time, deliverable, permissions. Written once after intake. |
| `cook/SHOTS.md` | One shot per reference: camera, framing, what to take from it. |
| `cook/ROUNDS.md` | The ledger. Copy `templates/ROUNDS.md` and add one entry per round. |
| `cook/refs/` | The references, numbered R01, R02 for images and V01, V02 for videos. |
| `cook/stills/rNN/`, `cook/compare/rNN/` | Renders and side-by-side images of round NN. |
## Start or resume
- `cook/BRIEF.md` exists and the run is not shipped: you are resuming. Read BRIEF, SHOTS and the last two ROUNDS entries, then start the next round (step 6). Do not re-ask, restart or rebuild what works.
- After every context compaction, do the same before your next action.
- `cook/` holds a shipped run: move it to `cook-archive/<date>/` and start at step 1.
- No `cook/` folder: start at step 1.
## The Cook Loop
### 1. Intake (once)
Ask every open question in one message, each with a default, so the user can answer by number or reply "defaults". Skip what the prompt, the attachments or a filled `templates/brief.md` already answer. If nothing is open, say so and start. Questions and defaults: `references/intake.md`.
Collect: what to build, references, bar, time budget, hard rules, deliverable, hardware, usage limits, and what you may download or publish.
Then write `cook/BRIEF.md` and `cook/ROUNDS.md` and start. From now on, never ask a question. The user may be asleep. Decide, log the decision under Decisions in ROUNDS.md, and keep working.
### 2. Target
References are the minimum bar, not inspiration.
- Study every reference at full size before building anything.
- Write `cook/SHOTS.md`: one shot per reference image, with camera, framing, time of day and what to take from it (light, color, composition, materials, timing).
- Motion references: analyze them frame by frame into a list of effects, transitions and timings. Take from many, never copy one element 1:1.
- Getting references for 3D, UI and motion, and the analysis steps: `references/target-and-bar.md`.
### 3. Bar
Write a number per dimension into BRIEF.md: composition, light, color, materials, detail density (near and far), motion.
- Stills: a stretch target such as 99.9% similarity. Video: a score out of 10. References at about 8.5 mean a target of 9 or more.
- Models rate themselves too high. When the user gives an estimate, log the gap as the calibration offset and apply it to every later score.
- Keep measured numbers (a command produced them) apart from eyeballed ones (critic scores).
### 4. Rules
Defaults unless the brief says otherwise. Full rules: `references/rules.md`.
- Zero external assets: every mesh, texture, shader and effect in code, when the point is the flex.
- Sound: code-made only if it truly holds up. Otherwise licensed free libraries, credited.
- Launch videos: real logos and real photos beat drawn SVG people.
- Slop ban list: eyebrow labels, monospace uppercase text, random serif fonts, purple gradients, beige, 01/02/03 counters, glowing orbs, shockwave rings popping out of things, decorative particles, em dashes.
- Color matches the references: never grey or washed out, never oversaturated.
- Weak GPU: keep realtime cheap and get the quality from offline rendering (sub-frame accumulation for motion blur, soft shadows, depth of field, anti-aliasing).
### 5. Time
- Demos get a floor: at least 8h, and done after 2h means something is wrong. Big builds can take days. Small jobs get a hard cap.
- Log the start time. Read the clock at every round boundary.
- Pace usage: about 20% of a 5h window per hour, about 99% per window, never 100%.
- Depth over breadth: make one shot, scene or element exceptional before you expand.
### 6. Loop
Before round 1, build the harness: a fixed camera preset per shot, a still renderer and a color check. For side-by-side images use `scripts/side-by-side.mjs` from this skill (Node 18+ and ffmpeg): `node <skill>/scripts/side-by-side.mjs --out cook/compare/r01/all.jpg cook/refs/R01.png cook/stills/r01/R01.png ...`. Every round reuses the harness.
Each round:
1. Focus: open user feedback first, else the weakest dimension in the weakest shot.
2. Fix it in depth. Split independent parts across parallel subagents.
3. Render stills from the shot presets, same framing and aspect as each reference. For motion, render contact sheets and short clips.
4. Make side-by-side images: reference left, render right.
5. Measure what can be measured: color per region, frame time, seconds per rendered frame.
6. Score with fresh-context critics: subagents with zero context that get only the side-by-side images and the rubric, optionally from another model. Your own score is logged, never decisive.
7. Log the round in `cook/ROUNDS.md`.
8. Send the stills to the user (Gate) and keep going.
9. Run the Stop check. If it fails, start the next round now.
Never stop when it first works. Never claim a check that was not run. If something was not measured, write "not measured". Round details, critic prompts and pacing: `references/loop-and-critics.md`.
### 7. Gate
- After every round, send the stills with a short note: what changed, scores, next focus. Do not pause, and do not end your turn to wait for a reply.
- User feedback beats critic priorities. Log the exact words and address them in the next round.
- Never start the final render, or any other long and costly export, before the user approves the stills in chat. While you wait, keep refining and test the render pipeline on a few short frames.
### 8. Ship
After approval, render the final deliverable and check the file. For a video on X: the first frame is the thumbnail and must be impressive, best scene first, a new scene every 6 to 7 seconds, no text on screen, licensed music credited, 1080p 30fps is enough. For a public repo: README, credits, the real prompt and honest numbers. Push or publish only if BRIEF.md allows it. Details: `references/ship.md`.
## Stop check
Stop only when all of these are true:
- Every dimension in every shot meets the bar, by critic median after calibration.
- The time floor is reached (capped jobs have no floor).
- The user approved the stills, and the final deliverable is rendered and its file checked.
Done before the floor means the bar was read too low. Reread the references at full size, check far distance, color and the weakest shot, and start another round. If a hard cap or a usage stop comes first, finish the round, lo질문하고, 팁을 나누고, 안 되는 점을 알려 주세요. "도움이 됨"이 많은 순서예요.