Skip to content
SkillModel-led2,392 tokens in use

godot-shaders

Helps an agent write Godot 4.7 .gdshader files for canvas_item and spatial, wire ShaderMaterials and check that every shader compiles headless.

9,684 stars on the repository Apache License 2.0gamedev-skills/awesome-gamedev-agent-skills · skills/godot/godot-shaders
npx skills add gamedev-skills/awesome-gamedev-agent-skills
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing godot-shaders costs

89tokens idle
2,392tokens in use
3,598tokens, up to

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Up to adds the files its instructions link. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

shelldetectedwrites filesdetected

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Excellent
  • Frontmatter8/15
  • Structure25/25
  • Examples12/15
  • Output10/15
  • Size11/15
  • Resources15/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent
  • Runs shell commands−5

    does this on the machine, and the frontmatter does not say so

    SKILL.md, line 55
  • Writes files−8

    does this on the machine, and the frontmatter does not say so

    SKILL.md, line 55

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Good
  • Development activity92
  • Maintenance96
  • Community60
  • Maturity24
  • Momentum40

This skill helps an agent write shaders in the Godot Shading Language: choosing the shader type, writing the right output variables, exposing uniforms with hints and wiring a ShaderMaterial in a scene file or from code.

It includes patterns for a scrolling tint, an emissive rim, a screen-reading blur and a headless script that compiles every .gdshader and surfaces SHADER ERROR lines. A gotcha list covers porting 3.x shaders, washed-out colours, transparent sorting and time rollover.

What You Get

  • A core workflow from picking canvas_item or spatial to exposing uniforms, wiring the material and checking compilation
  • Shader patterns for a tinted scrolling UV, an emissive rim on an opaque material and a screen-reading blur
  • A headless GDScript that finds every .gdshader, forces compilation and prints errors for grep
  • A gotcha list for 3.x renames, wrong output variables, missing source_color, transparent pipeline side effects and UV clamping

Common Use Cases

  • Writing a new .gdshader for a sprite or 3D mesh
  • Fixing a SHADER ERROR in the Output panel
  • Porting a Godot 3 shader that uses SCREEN_TEXTURE
  • Setting shader parameters from GDScript

What Makes It Unique

The skill gives a way to check shaders without a window: a headless script that forces the compiler to run and a grep on the log. It lists the Godot 4 renames that break old shaders and the subtle cases, such as writing ALPHA moving a material into the transparent pipeline, that make objects sort wrong.

Under The Hood

The agent loads the SKILL.md and, when needed, a reference on built-ins, render modes and light functions. It writes .gdshader files and a small GDScript compile test into your project, runs the Godot binary headless with output redirected to a log file, and searches the log with grep. If you wired a material by editing a scene file it also runs the Python project checker from a sibling skill. It fetches no web pages and calls no APIs; the headless run does not use the GPU driver, so the skill asks you to look at the result in the real renderer.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers