REA
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
你的随身 AI 剪辑搭档 | Pocket AI co-editor for video montage — AI video editing plugin & MCP server for Claude Code, Codex, Hermes & OpenCode
제작자라면 이 코드를 README에 붙여 넣으세요. 배지는 이 페이지로 연결됩니다.
[](https://mcp.popnx.com/en/skills/cassette-editor-oh-my-cassette)같은 작업에서 AI를 서비스에 연결하는 MCP
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
Codebase intelligence for TypeScript and JavaScript, exposed as structured MCP analysis tools.
MCP server for terminal commands, file operations, and process management
같은 종류의 작업, Skill 목록과 같은 순서
| 이 항목 oh-my-cassette | rea | andrej-karpathy-skills | graphify | MoneyPrinterTurbo | |
|---|---|---|---|---|---|
| 제작자 | Cassette-Editor | morluto | multica-ai | Graphify-Labs | harry0703 |
| Skill 수 | 1 | 1 | 1 | 1 | 1 |
| GitHub 별 | 219 | 468,733 | 234,332 | 150,287 | 144,566 |
| 마지막 코드 변경 | 2026년 11월 19일 | 2026년 11월 19일 | 2026년 4월 20일 | 2026년 11월 18일 | 2026년 11월 18일 |
| 라이선스 | MIT | MIT | – | Apache-2.0 | MIT |
Cassette-Editor의 Skill(지시 묶음) 1개, AI가 읽고 그대로 일해요 · MCP server가 아니에요
MCP = 손
AI를 외부 서비스나 데이터에 연결합니다(예: Notion 읽기, 청구서 만들기). 프로그램이나 서버가 실행 중이어야 합니다.
Skill = 안내서
작업 방법을 AI에게 가르치는 텍스트 파일. 어떤 서비스에도 연결되지 않습니다.
겹치는 경우도 있습니다. 도구를 부르는 스크립트가 있는 Skill도, 지식만 보내는 MCP도 있습니다. 하려는 작업을 기준으로 고르세요.
Claude CodeCodexOpenCode
제작자 README와 repo 폴더 기준
GitHub account Cassette-Editor (organization) is only 4 months old: take extra care
★ 219 stars, few users so far · code last changed 2026년 11월 19일
No, plain text files the AI reads and follows
No scripts, so it does not go online by itself
No hooks or writes to machine settings found
Checked automatically from the repo files at commit 1747ebb (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 (511). 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를 다시 열고 /cassette-video-edit를 입력하거나 관련 작업을 요청하면 Claude가 알아서 써요
Checked against official docs 2026년 11월 12일 · Source: code.claude.com
Skill은 AI가 따르는 지시예요. 설치 전에 파일을 읽고, 믿을 수 있는 제작자 것만 설치하세요.
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
cassette-video-edit 폴더를 ~/.agents/skills/cassette-video-edit에 넣으세요
~는 홈 폴더($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 채팅에서 /를 입력하고 cassette-video-edit 선택
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의 지시가 아니에요
7,977자 · GitHub에서 전체 파일 열기
---
name: cassette-video-edit
license: MIT
description: Edit, trim, cut, caption, retime, combine, or export video, audio, and image files through Cassette. Use this skill whenever the user asks to change, preview, or render media in the project, even if they never say "Cassette" or name a tool, for example "trim the intro off demo.mp4", "add subtitles to this clip", "make a 30-second cut", "put a title on it", "export the video". Drives the tools of the `cassette` MCP server (oh-my-cassette), which relays a running conversation with the Cassette editing agent.
---
# Oh My Cassette
The `cassette` MCP server is a local bridge to the Cassette video editor. Its editing tools come
from the Cassette MCP service and change as Cassette evolves, so this skill deliberately names none
of them. **The server's instructions and each tool's description are the source of truth**: read
them, and when they disagree with anything you remember, they win.
## Rules that hold for every version
1. **Follow the server.** Which tool to call, in what order, and how to route on a result are in the
server instructions and the tool descriptions. Route on typed fields such as `status`, never on
prose.
2. **Relay the user's words.** When a tool takes the user's editing request, pass it exactly as the
user wrote it: no rewriting, summarizing, translating, or expanding. The Cassette agent reads the
project media itself.
3. **Ground every claim in a tool result.** What is on the timeline, which version it is, and where
the editor link points come from the latest result, not from memory.
4. **Render only when asked.** Export or render only when the user asks to export, render, download,
or finish.
5. **Say where the media goes.** When the user has not asked for Cassette by name in this
conversation, tell them before the first upload that the files they named go to the Cassette
service for editing, and go on once they agree.
## Local files
- Pass file paths as the user gave them, absolute or relative to the workspace. The bridge prepares
and uploads them and hands Cassette references in their place.
- Only files the user named or that sit in the workspace. Never search the filesystem for media.
- Files outside the workspace are refused unless the user adds their directory to
`CASSETTE_ALLOWED_ROOTS`. Only video, audio, and image files upload.
- Video is transcoded on this machine with ffmpeg before it uploads, and audio or images Cassette
does not take as they are get converted. Long footage can take minutes.
- Exported files are downloaded into `cassette-exports/` in the workspace. Use the local path the
result gives you; never invent one. When the result says a file is still downloading, the download
goes on in the background and the file appears where the result says: tell the user that, and do not
export again to get it.
## Long waits
Long work never fails just for taking long. A tool waits a bounded time and then returns a normal,
non-error result that says the work is still going:
- **`status: "preparing"`** comes from the bridge: the local files are still being prepared or
uploaded, and that work continues in the background. Tell the user the progress it reports, then
call the same tool again with exactly the same arguments to keep waiting; it picks up the same
work instead of starting over. Never keep calling for longer than the user is willing to wait:
ask before you continue a long wait.
- **`running`, `processing` and similar statuses** come from Cassette. How to continue (usually the
same tool with the id the result returns) is in the server instructions and the tool description.
- Cancelling a call only stops waiting; the work goes on. Stop the work itself only when the user
asks, with the tool the server provides for that.
## When the bridge itself reports a problem
Errors whose code starts with `bridge.` come from the local bridge, not from Cassette. Any other
error code is Cassette's own: follow its message and the tool description.
| Code | What to do |
| --- | --- |
| `bridge.backend_unreachable` | A tool that names its request in an argument has already been sent again by the bridge while the call's wait lasted. If the message says the connection broke during the call, the work may still be running: call the same tool again with the same arguments to pick it up. If it says Cassette did not take the call, retry after `retry_after_seconds` when the error gives it. Otherwise call `cassette_bridge_status` once, tell the user the service is not reachable and at which URL, and retry only after it reports connected. |
| `bridge.rate_limited` | Cassette is taking too many requests and did not run the call. Wait `retry_after_seconds` (from the error), then call the same tool again with the same arguments; do not retry sooner. |
| `bridge.forbidden` | This account or grant cannot access Cassette. Ask the user to check that they signed in with the account of their projects. Do not repeatedly trigger login. |
| `bridge.auth_unavailable` | Online authentication or secure credential storage is unavailable. Tell the user to restore the connection, or relay the keyring steps the message gives for their system, then retry. |
| `bridge.unauthorized` | The service refused the token. Tell the user to run `oh-my-cassette login`. The browser handles email verification and consent. Restart the MCP host only if it cannot refresh tools. Do not repeatedly trigger login. |
| `bridge.upgrade_required` | Tell the user to update the oh-my-cassette version their MCP host runs (the message links the steps: bump the `oh-my-cassette==` pin, or update the plugin). Do not retry. |
| `bridge.protocol_unsupported` | The service at that URL is too old for this plugin (it does not speak MCP 2026-07-28). Tell the user the Cassette service must be updated. Do not retry. |
| `bridge.file_not_found` | Ask the user for the correct path. |
| `bridge.file_outside_workspace` | Ask the user to copy the file into the workspace, or to add its directory to `CASSETTE_ALLOWED_ROOTS`. When the message says the host started the bridge in a folder too wide to read from (the whole disk or the home folder), ask them to set `CASSETTE_WORKSPACE` to the project folder. |
| `bridge.file_type_rejected` | Tell the user which types this tool accepts (the message lists them). |
| `bridge.file_empty` | The file has no content (0 bytes). Tell the user which file it is; do not retry it unchanged. |
| `bridge.file_too_large` | Tell the user about the size limit (`CASSETTE_MAX_UPLOAD_MB`). |
| `bridge.ffmpeg_unavailable` | Video needs ffmpeg on this machine. Relay the install hint from the message, or ask the user to set `CASSETTE_FFMPEG` and `CASSETTE_FFPROBE`. Do not retry until it is installed. |
| `bridge.prepare_failed` | ffmpeg could not read or convert the file. Tell the user which file failed and what the message says; do not retry the same file unchanged. |
| `bridge.private_address` | The storage host resolved to a private address on this machine's network, usually through a VPN, proxy or DNS setting. Relay the message; retry only after the user changes that setting. |
| `bridge.upload_failed` | Retry once, then report it. |
| `bridge.invalid_argument` | Fix the arguments: file parameters take a path or a list of paths. |
| `bridge.contract_violation` | A Cassette service bug. Report it to the user as is; do not retry. |
A failed export download (`bridge.download_failed`) does not fail the call: the result says so and
keeps the original URL, which you can give the user.
## When only `cassette_bridge_status` is listed
The service is offline, refused the sign-in, or needs a newer plugin. Call `cassette_bridge_status`
once and tell the user what it reports (URL, `error_code` and reason). Do not poll it. When the
service comes back, its tools appear by themselves; if this host does not refresh tool lists, ask
the user to restart the MCP server.
질문하고, 팁을 나누고, 안 되는 점을 알려 주세요. "도움이 됨"이 많은 순서예요.