Traction scoreGitHub stars can be faked, so popularity alone can be misleading. Traction Score looks for broader signs of recent attention, adoption, and active maintenance.
This collection provides specialized guidance for technical directors and 3D artists managing complex Blender pipelines. It bridges the gap between raw software capability and production-ready output, focusing on precise technical execution across diverse visual styles.
From orchestrating AAA production workflows to implementing specific aesthetics like analog horror and found-footage cinematography, these skills structure the process of creating high-fidelity assets and cinematic sequences.
WHO IT'S FOR
Game developers
creating game-ready animations and character cycles
3D environment artists
producing architectural visualizations and interior renders
Stylized 3D artists
implementing cel-shaded and anime art directions
Digital filmmakers
creating analog horror and found-footage aesthetics
Compatible AgentsThe repository documents support for these agents. The skills may also work with other agents that can load SKILL.md files, but they may need some setup or small changes.
Follow the documented setup, then try a first task.
I’m using
Claude Code project installation
Installs: Complete Blender Skills pack, documented as 94 skills, copied into a project's Claude skills directory. The listed paths are a bounded selection. · Claude Code
Before you start
Git available to clone the repository.
For live execution: Blender with the BlenderMCP addon enabled and connected, uv available on PATH, and the agent configured for Blender MCP.
From the directory containing the clone, run this terminal command. Replace /path/to/your/project with your project's actual path. Restart Claude Code after copying.
cp -r blender-skills/.claude/skills /path/to/your/project/.claude/skills/
# Restart Claude Code after copying
Installs: Complete Blender Skills pack, documented as 94 skills, copied from the repository's Claude skill folders into Cursor project skills. The listed paths identify source files and are a bounded selection. · Cursor
Before you start
Git available to clone the repository.
For live execution: Blender with the BlenderMCP addon enabled and connected, uv available on PATH, and the agent configured for Blender MCP.
Platform: Windows PowerShell
Run from: Target project root
Run this complete block in PowerShell from the target project root.
Installs: Complete Blender Skills pack, documented as 94 skills, copied from the repository's Claude skill folders into Cursor project skills. The listed paths identify source files and are a bounded selection. · Cursor
Before you start
Git available to clone the repository.
For live execution: Blender with the BlenderMCP addon enabled and connected, uv available on PATH, and the agent configured for Blender MCP.
Installs: Complete Blender Skills pack, documented as 94 skills, copied into the project or user skills directory selected by the user's Kiro setup. The listed paths are a bounded selection. · Kiro
Before you start
Git available to clone the repository.
The location of your Kiro project or user skills directory.
For live execution: Blender with the BlenderMCP addon enabled and connected, uv available on PATH, and Kiro configured for the same BlenderMCP server.
From the directory containing the clone, run this terminal block. Replace /path/to/kiro/skills/ with your actual Kiro skills directory. For live execution, configure Kiro's Blender MCP connection to use the running BlenderMCP addon session.
# Example: copy into your Kiro skills directory
cp -r blender-skills/.claude/skills/* /path/to/kiro/skills/
# Point Blender MCP at the same BlenderMCP addon session
Installs: Complete Blender Skills pack, documented as 94 skills, linked into the user's Codex skills path. The listed paths are a bounded selection. · Codex
Before you start
Git available to clone the repository.
The location of your Codex skills path.
For live execution: Blender with the BlenderMCP addon enabled and connected, uv available on PATH, and Codex configured for the same BlenderMCP server.
Run this terminal block to create the symlink. Replace /path/to/blender-skills with the actual cloned repository path and /path/to/codex/skills with your actual Codex skills path. The final line is the author's commented copy alternative.
# Example: symlink skills into Codex skills path
ln -s /path/to/blender-skills/.claude/skills /path/to/codex/skills/blender-skills
# Or copy: cp -r blender-skills/.claude/skills/* /path/to/codex/skills/
A connected BlenderMCP addon and configured agent client for live creation; otherwise request an instructional workflow.
Use voxel-style to create a small blocky crate in Blender on a 0.1 m voxel grid. Declare the voxel size in the brief, use stepped forms and a small flat-color palette, and keep all geometry consistently snapped to the grid.
The intended target engine and approximate grass-clump size.
Any existing grass atlas or visual reference, if available.
Use vegetation-artist to outline a compact Blender workflow for one game-ready grass clump. Cover grass cards, a shared atlas, pivots at the card and plant bases, VC_Wind weighting, and a simple LOD plan. Keep this first result to a practical authoring checklist.
Room dimensions and units, including door and window positions.
The intended view or architectural feature to emphasize.
Use archviz to plan the first greybox and camera for a small interior using my supplied room dimensions. Start by checking real-world scale, propose a camera in the documented 24–35 mm interior range, and outline window lighting and practical lamps. Keep the result to a short setup plan before final modeling or rendering.