Podcast
zarazhangrui/personalized-podcast
Generate a podcast episode from content you provide. An agent skill from zarazhangrui/personalized-podcast.
Convert physical-state-planner outputs into standalone Blender Python preview videos.
Install Physical Video Blender Implementer
$ npx skills add micky-li-hd/VideoCoCo --skill physical-video-blender-implementer -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install micky-li-hd/VideoCoCo physical-video-blender-implementer --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/micky-li-hd/VideoCoCo.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skill/physical-video-blender-implementer .claude/skills/physical-video-blender-implementer && 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 "physical-video-blender-implementer" agent skill from https://github.com/micky-li-hd/VideoCoCo/tree/main/skill/physical-video-blender-implementer into .claude/skills/physical-video-blender-implementer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "physical-video-blender-implementer", 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/micky-li-hd/VideoCoCo/tree/main/skill/physical-video-blender-implementerType 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 micky-li-hd/VideoCoCo --skill physical-video-blender-implementer -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install micky-li-hd/VideoCoCo physical-video-blender-implementer --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/micky-li-hd/VideoCoCo.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skill/physical-video-blender-implementer .agents/skills/physical-video-blender-implementer && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "physical-video-blender-implementer" agent skill from https://github.com/micky-li-hd/VideoCoCo/tree/main/skill/physical-video-blender-implementer into .agents/skills/physical-video-blender-implementer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "physical-video-blender-implementer", 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 micky-li-hd/VideoCoCo --skill physical-video-blender-implementer -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install micky-li-hd/VideoCoCo physical-video-blender-implementer --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/micky-li-hd/VideoCoCo.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skill/physical-video-blender-implementer .cursor/skills/physical-video-blender-implementer && 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 "physical-video-blender-implementer" agent skill from https://github.com/micky-li-hd/VideoCoCo/tree/main/skill/physical-video-blender-implementer into .cursor/skills/physical-video-blender-implementer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "physical-video-blender-implementer", 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/micky-li-hd/VideoCoCo.git --path skill/physical-video-blender-implementer--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 micky-li-hd/VideoCoCo --skill physical-video-blender-implementer -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install micky-li-hd/VideoCoCo physical-video-blender-implementer --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/micky-li-hd/VideoCoCo.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skill/physical-video-blender-implementer .gemini/skills/physical-video-blender-implementer && 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 "physical-video-blender-implementer" agent skill from https://github.com/micky-li-hd/VideoCoCo/tree/main/skill/physical-video-blender-implementer into .gemini/skills/physical-video-blender-implementer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "physical-video-blender-implementer", 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 micky-li-hd/VideoCoCo physical-video-blender-implementerInstalls 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 micky-li-hd/VideoCoCo --skill physical-video-blender-implementer -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/micky-li-hd/VideoCoCo.git skills-src && mkdir -p .github/skills && cp -r skills-src/skill/physical-video-blender-implementer .github/skills/physical-video-blender-implementer && 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 "physical-video-blender-implementer" agent skill from https://github.com/micky-li-hd/VideoCoCo/tree/main/skill/physical-video-blender-implementer into .github/skills/physical-video-blender-implementer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "physical-video-blender-implementer", 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 micky-li-hd/VideoCoCo --skill physical-video-blender-implementer -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install micky-li-hd/VideoCoCo physical-video-blender-implementer --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/micky-li-hd/VideoCoCo.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skill/physical-video-blender-implementer .opencode/skills/physical-video-blender-implementer && 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 "physical-video-blender-implementer" agent skill from https://github.com/micky-li-hd/VideoCoCo/tree/main/skill/physical-video-blender-implementer into .opencode/skills/physical-video-blender-implementer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "physical-video-blender-implementer", 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
physical-video-blender-implementer- GitHub stars
- 118
- Token cost
- ~1.3k tokens
- SKILL.md length
- 571 words
- Files
- 5 (incl. references)
- Skills in repo
- 3
- Repo updated
- First seen
- Licence
- None found
At a glance
Convert physical-state-planner outputs into standalone Blender Python preview videos.
- Works in 6 steps: Read the plan and preserve its structure → Design the Blender scene → Implement causal visibility → …
- Codex needs to implement semantic keyframes and transitions as Blender scene objects
- SKILL.md covers Purpose, Inputs, Workflow and Output Contract, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Physical Video Blender Implementer is an agent skill from micky-li-hd/VideoCoCo. Convert physical-state-planner outputs into standalone Blender Python preview videos. Use when Codex needs to implement semantic keyframes and transitions as Blender scene objects, materials, animations, visibility timing, preview rendering, and preview-sheet extraction while preserving physical causality and avoiding listed anti-patterns.
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including reference files (for example `agents/openai.yaml`, `references/blender-script-guidelines.md` and `references/implementation-output-schema.json`).
It sits in Media & Creative. It works with Blender and FFmpeg. The repository describes itself as: Code-as-CoT for Physically-Consistent Video Generation via an Agentic Dual-Engine System.
When your agent uses it
- Codex needs to implement semantic keyframes and transitions as Blender scene objects
- Visibility timing
- Preview rendering
- Preview-sheet extraction while preserving physical causality and avoiding listed anti-patterns
Example prompts
- “/physical-video-blender-implementer”
Requirements
- Python 3
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Read the plan and preserve its structure
- Design the Blender scene
- Implement causal visibility
- Write a standalone Blender Python script
- Render and audit a preview
- Return concrete artifacts
What it can do on your machine
Read from SKILL.md and the folder at commit 4afce26. 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 json).
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
Physical Video Blender Implementer loads about 1.3k tokens when it runs, and up to ~2.7k if it reads all its reference files. Until then it costs about 94 tokens; SKILL.md has 571 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
Without a licence we can't republish the file, so here is its outline and opening line. It has 571 words (~1,264 tokens).
“Use this skill after a physical state plan exists. Convert the plan's scene, semantic keyframes, transitions, causal constraints, must_show, and must_avoid into a runnable Blender Python script and a low-cost preview.”
- name
- physical-video-blender-implementer
Files
SKILL.md and 4 other files (references) in skill/physical-video-blender-implementer of micky-li-hd/VideoCoCo.
- SKILL.md
- agents/openai.yaml
- references/blender-script-guidelines.md
- references/implementation-output-schema.json
- references/preview-rendering.md
Open the folder on GitHubat commit 4afce26
Compare with similar skills
Physical Video Blender Implementer 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 |
|---|---|---|---|---|---|---|
| Physical Video Blender Implementer this skillmicky-li-hd/VideoCoCo | 118 | — | ~1.3k | Automated safety check: Pass | None | |
| Podcastzarazhangrui/personalized-podcast | 438 | — | ~2.3k | Automated safety check: Notes | None | |
| Book Sales VideoKianzzz/book-sales-video | 218 | — | ~3.2k | Automated safety check: Pass | MIT | |
| Frames CLIviticci/frames-cli | 405 | — | ~6.1k | Automated safety check: Pass | MIT | |
| Video Assemblezenstory-ai/video-recap-skills | 561 | — | ~1.7k | Automated safety check: Pass | MIT | |
| Extract Video Framesqdhenry/Claude-Command-Suite | 1.3k | — | ~1.6k | Automated safety check: Pass | None |
Similar skills
Book Sales Video
Kianzzz/book-sales-video
从书名或飞书多维表格中的成稿文案出发，结合微信读书资料与公开点评创作图书带货/书评短视频，并用豆包 TTS、Pexels、Codex 生图和本机 OpenChatCut 完成配音、配图、双语字幕、音效、动效、BGM、可编辑初稿与按需导出。用户提出“根据一本书做带货视频”“读取飞书文案制作图书视频”“写书评口播并自动剪成抖音视频”“仿参考样式做图书推荐短视频”时使用；仅查书、仅写普通书评或无关剪辑…
Frames CLI
viticci/frames-cli
Frame screenshots and screen recordings with the frames CLI.
Video Assemble
zenstory-ai/video-recap-skills
合成视频解说最终成片：把旁白音频铺到源视频上，按旁白窗口压低原声，生成 SRT / ASS 字幕并可烧录， 最后做响度标准化。作为最终合成阶段使用。输入源视频、ttsmeta.json 与旁白位置； 输出 recap 成片和字幕。触发词：视频合成、混音、字幕、压字幕、assemble video、mux、ducking、subtitles、成片。
Extract Video Frames
qdhenry/Claude-Command-Suite
Extracts frames and timestamped audio segments from video files (GIF, MP4, MOV) at configurable intervals and stores them in a directory with a manifest file.
Video Cut
zenstory-ai/video-recap-skills
把长视频按 Agent 选择的原片区间剪成短片。作为两阶段创作流程中的剪辑环节，读取 clipplan.json 与源视频， 输出 editedsource.mp4；随后 Agent 按输出时间线写 narration.json。支持单视频与多视频（sources manifest）拼剪， 本工具不读取、不映射旁白。
More from micky-li-hd/VideoCoCo
Physical State Planner
micky-li-hd/VideoCoCo
Create concise, dataset-agnostic physical state plans from video prompts.
Blender MCP Video
micky-li-hd/VideoCoCo
A skill your agent uses for Blender MCP or Blender CLI video-generation work, especially when rendering scripted Blender scenes, debugging MCP port 9876, checking why blender is not on PATH…
Related
Categories
Questions about Physical Video Blender Implementer
What does Physical Video Blender Implementer do?
Convert physical-state-planner outputs into standalone Blender Python preview videos. Physical Video Blender Implementer is an agent skill from micky-li-hd/VideoCoCo. Convert physical-state-planner outputs into standalone Blender Python preview videos.
When should I use Physical Video Blender Implementer?
Physical Video Blender Implementer fits situations like: Codex needs to implement semantic keyframes and transitions as Blender scene objects; visibility timing; preview rendering; preview-sheet extraction while preserving physical causality and avoiding listed anti-patterns.
How do I install Physical Video Blender Implementer in Claude Code?
Run `npx skills add micky-li-hd/VideoCoCo --skill physical-video-blender-implementer -a claude-code`. Or copy the skill folder (skill/physical-video-blender-implementer in micky-li-hd/VideoCoCo) into .claude/skills/physical-video-blender-implementer in your project. Claude Code loads it when a task matches its description.
How do I install Physical Video Blender Implementer in Codex?
Run `npx skills add micky-li-hd/VideoCoCo --skill physical-video-blender-implementer -a codex`. Or copy the skill folder (skill/physical-video-blender-implementer in micky-li-hd/VideoCoCo) into .agents/skills/physical-video-blender-implementer in your project. Codex loads it when a task matches its description.
Can I use Physical Video Blender Implementer 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 micky-li-hd/VideoCoCo --skill physical-video-blender-implementer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/physical-video-blender-implementer, .gemini/skills/physical-video-blender-implementer, .github/skills/physical-video-blender-implementer and .opencode/skills/physical-video-blender-implementer in your project.
What does Physical Video Blender Implementer need to run?
SKILL.md names no scripts, command-line tools or credentials: Physical Video Blender Implementer is instructions for the agent only. Our summary lists: Python 3.
Does Physical Video Blender Implementer 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 Physical Video Blender Implementer 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 Physical Video Blender Implementer use?
No licence was found for Physical Video Blender Implementer or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Physical Video Blender Implementer use?
About 1.3k tokens (SKILL.md is roughly 5.1k 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.4k tokens, read only when the agent opens those files.
What are the alternatives to Physical Video Blender Implementer?
Skills that share tags, products or a category with Physical Video Blender Implementer: Podcast (zarazhangrui/personalized-podcast, 438 stars), Book Sales Video (Kianzzz/book-sales-video, 218 stars), Frames CLI (viticci/frames-cli, 405 stars) and Video Assemble (zenstory-ai/video-recap-skills, 561 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Physical Video Blender Implementer?
micky-li-hd (a GitHub user) maintains it in micky-li-hd/VideoCoCo, which has 118 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on August 6, 2026.
Source: micky-li-hd/VideoCoCo on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.