Godot technical artist
Skill schmoenraad/godot-gamestudio/plugins/godot-gamestudio/skills/godot-technical-artist
Build and optimize Godot shaders, materials, VFX, particles, lighting, rendering settings, asset imports, compression, and visual performance budgets. Use for technical-art implementation and art-pipeline deliverables.From its SKILL.md
npx -y skills add schmoenraad/godot-gamestudio --skill godot-technical-artistAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
0.9 KB, 134 tokens by cl100k_base, as published. Nobody here has run it
Godot Technical Artist
- Read the renderer, target hardware, resolution, art direction, and existing budgets.
- Choose the simplest Godot-native technique that achieves the visual goal.
- Keep shader parameters artist-tunable and document non-obvious ranges.
- Verify imports, filtering, mipmaps, compression, color space, and material reuse.
- Measure runtime cost where possible; do not infer performance from appearance alone.
- Capture visual evidence and before/after metrics for review.
Use an installed lower-level Godot engineering skill when available; otherwise use Godot directly for shaders, VFX, imports, runtime inspection, and optimization.
What ships with it: 1 file
220 B alongside SKILL.md
agents/
- openai.yaml220 B
Gives 0 of the 12 instructions most performance cost skills give in 134 tokens
Counted across 803 of the 1,058 authors here whose files we hold, read 2026-08-07
- Keep skill files under 500 lines or tokensin 82 of 803, across 16 files
- Use imperative form in instructionsin 80 of 803, across 9 files
- Draft assertions while test runs are in progressin 75 of 803, across 9 files
- Create two to three realistic test promptsin 74 of 803, across 9 files
- Write skill descriptions to be pushyin 72 of 803, across 7 files
- Save test cases to evals JSONin 72 of 803, across 6 files
- Ask questions about edge cases and input formatsin 72 of 803, across 7 files
- Save timing data immediately when runs completein 70 of 803, across 5 files
- Include all trigger conditions in the skill descriptionin 69 of 803, across 3 files
- Launch all test runs in a single turn or simultaneouslyin 69 of 803, across 3 files
- Capture intent before writing a skillin 67 of 803, across 1 file
- Import directly instead of barrel filesin 52 of 803, across 15 files
Said here and by no other author read
- read the renderer target and budgets
- choose the simplest native technique
- keep shader parameters artist-tunable
- document non-obvious parameter ranges
- verify imports compression and material reuse
- measure runtime cost directly
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.