blender-pipeline
Skill97 starsChanged 2 months agoApache-2.0View on GitHub
Extract a tutorial or reconstruct a Blender result from video links, local videos with supporting assets, or Markdown tutorials in Codex chat. Clarify the intended output when unspecified; also route explicit showcase reproduction and independent asset edits.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- DECRUX9812/hermes-plugin-gameforgetheir own version, first seen Oct 25, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- DECRUX9812/hermes-plugin-gameforge★ 44same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository4 other files it gives its agents.
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 5 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Read references/codex-launch.md, interpret the user's natural-language inputs, and invoke this skill's scripts/launch_from_codex.py …
- Distinctive: line 25
Use the user's requested output location or established data root.
- Very specific: line 40
Read reproduction/SKILL.md only for an explicitly requested catalog recipe or hybrid-delivery workflow.
- Very specific: line 51
Read generation/SKILL.md, then load knowledge/generation.md, knowledge/evidence-and-routing.md, and only the relevant sections of
- Distinctive: line 59
Use editing for a standalone change request on an existing asset, without a video/tutorial reconstruction workflow.
- Very specific: line 63
Read editing/SKILL.md, then load knowledge/editing.md and only the relevant sections of knowledge/rendering-and-dynamics.md.
- Distinctive: line 69
Keep mode-specific code, tests, manifests, and outputs separate.
- Distinctive: line 73
Use explicit input/output paths and environment-backed credentials.
- Distinctive: line 77
Start knowledge lookup at knowledge/index.md.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Blender Pipeline
Start from the Codex client
This is the user-facing Codex launcher. If the requested output is unclear, ask whether the user wants only a tutorial or a complete Blender reconstruction; wait for their choice before launching. Do not ask again when the goal is explicit.
Read references/codex-launch.md, interpret the
user's natural-language inputs, and invoke this skill's
scripts/launch_from_codex.py yourself. It calls the same maintained pipeline
as the API entrypoint. Tutorial-only stops after preparation; full reconstruction
continues through knowledge retrieval → Blender generation → render and review.
A video with an accompanying .blend, preview, texture, or dependency bundle
retains those inputs in either selected route; it is not an independent edit.
A supplied Markdown tutorial skips video extraction: prepare it for tutorial-only,
or continue knowledge-backed generation for reconstruction. No RW1 is required.
Use the user's requested output location or established data root. Ask only for
missing information needed to run, not command-line flags or API credentials.
The Codex path uses the signed-in Codex CLI; the user need not run a Python
launcher manually. run_codex.py remains a compatibility entrypoint, not the
client interaction. Requests to explain, inspect, or dry-run do not authorize
an actual reconstruction.
Extract a tutorial from video
For tutorial-only, pass --extract-only and do not start reconstruction. Read
tutorial-extraction/SKILL.md for illustrated
Markdown, learner inputs and the separate rubric; both replay routes reuse it.
Reproduce a maintained showcase
Read reproduction/SKILL.md only for an explicitly requested catalog recipe or hybrid-delivery workflow. A tutorial's subject also appearing on the showcase does not change ordinary replay routing. Public previews do not authorize downloading the underlying assets.
Generate from zero
For ordinary video/tutorial requests use the client launcher above. Use the specialized generation mode for an explicit from-zero reference/text task or low-level generation work, with no authoritative starting project.
Read generation/SKILL.md, then load knowledge/generation.md, knowledge/evidence-and-routing.md, and only the relevant sections of knowledge/rendering-and-dynamics.md.
Edit an existing asset
Use editing for a standalone change request on an existing asset, without a video/tutorial reconstruction workflow. A generated replacement object within that scoped change remains part of the edit.
Read editing/SKILL.md, then load knowledge/editing.md and only the relevant sections of knowledge/rendering-and-dynamics.md.
Shared rules
- Keep mode-specific code, tests, manifests, and outputs separate. Share only stable utilities and contracts.
- Preserve verified source intent and non-target dimensions. A successful file write is not a visual or semantic pass.
- Use explicit input/output paths and environment-backed credentials; never embed workstation, mounted-volume, or server paths in committed code.
- Load knowledge/operations-and-knowledge.md only for orchestration, paid calls, knowledge maintenance, or publication.
- Start knowledge lookup at knowledge/index.md; do not load every reference for an ordinary single-mode task.
Package maintenance uses scripts/validate_package.py, not every ordinary launch.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.