Individual skill
scenario-godot-pipeline-automation
Use when Godot 4.7 work must run without a mouse or at scale: batch import of hundreds of GLB props or an AI image-to-3D art drop, naming rules, import presets and post-import scripts, editor plugins, EditorScript and @tool, EditorImportPlugin, GUT or gdUnit4 tests in CI, a GitHub Actions export workflow, GDExtension basics, or a Godot MCP server; also when --import is slow, textures stay uncompressed, tests pass locally but CI fails, or an export ships test folders.
skills/game-engines/godot/scenario-godot-pipeline-automation/SKILL.md
Source commit f29bf06ab89088695ed3431ac99d20a090441a2f
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 9, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 3,666
- Repository last updated
- Nov 10, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- blender Repository topic
- claude-code Repository topic
- claude-skills Repository topic
- codex Repository topic
- game-assets Repository topic
- game-development Repository topic
- generative-ai Repository topic
- image-generation Repository topic
- mcp Repository topic
- operations Derived category
- testing Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 22,061 bytesSKILL.mdcore · 22,061 bytesSKILL.mdcore · 22,061 bytesreferences/critique.mddoc · 6,185 bytesreferences/expert-notes.mddoc · 8,954 bytesreferences/gui-paths.mddoc · 6,067 bytesreferences/procedures.mddoc · 29,070 bytesreferences/sources.mddoc · 11,263 bytesscripts/agentkit/pipeline/glb_probe.gdasset · 10,043 bytesscripts/agentkit/pipeline/prop_audit.gdasset · 4,826 bytesscripts/agentkit/pipeline/prop_ingest.gdasset · 8,414 bytesscripts/agentkit/pipeline/prop_rules.gdasset · 7,990 bytesscripts/agentkit/pipeline/prop_textures.gdasset · 2,749 bytesscripts/agentkit/pipeline/prop_thumbs.gdasset · 3,861 bytesscripts/agentkit/prop_pipeline_addon/plugin.cfgasset · 251 bytesscripts/agentkit/prop_pipeline_addon/plugin.gdasset · 598 bytesscripts/agentkit/prop_pipeline_addon/prop_post_import.gdasset · 5,098 bytesscripts/ci/godot-ci.ymlasset · 2,891 bytesscripts/ci/godot_ci.shruns · 3,102 bytesscripts/examples/gdext_c/pipeline_ext.casset · 6,520 bytesscripts/examples/gdext_c/pipeline_ext.gdextensionasset · 259 bytesscripts/examples/level_importer/lvl_import.gdasset · 2,717 bytesscripts/examples/level_importer/plugin.cfgasset · 246 bytesscripts/examples/level_importer/plugin.gdasset · 370 bytesscripts/examples/tools/add_spawns.gdasset · 829 bytesscripts/examples/tools/spawn_point.gdasset · 698 bytesscripts/gd_pipeline.pyruns · 20,128 bytesscripts/gdunit/door.gdasset · 182 bytesscripts/gdunit/test_glb_probe.gdasset · 2,489 bytesscripts/gdunit/test_imported_props.gdasset · 616 bytesscripts/gdunit/test_prop_rules.gdasset · 2,770 bytesscripts/gdunit/test_scene_runner.gdasset · 1,077 bytes
Read excerpt
# Godot pipeline automation (tools and build engineer)
Target: Godot 4.7.2.stable, macOS Apple Silicon, gdUnit4 6.2.1.
Expert level here means every step a human would click is a command that CI can run twice with the
same result, and every result is checked by a test that has been seen failing. The tools engineer
owns the path from an art drop or a commit to a tested export: ingest, import, editor tooling,
tests, CI, native extensions and agent channels. If a sibling skill named here is missing from your
available skills, load it with `skill_get` (Scenario MCP) or ask the user to install it
(https://github.com/scenario-labs/skills#install); unattended, proceed from tool schemas and flag
the gap.
**REQUIRED BACKGROUND:** scenario-godot-expert (channels, `gd_run` and `gd_env`, the review loop,
4.7 traps). This skill adds [`scripts/gd_pipeline.py`](scripts/gd_pipeline.py) and the AgentKit