shader-debugging SKILL.md skillA
shader-debugging from vecnode/vncode is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add vecnode/vncode/shader-debugging@git:20261020.ef66089Pins git:20261020.ef66089 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- vecnode/vncode
- Path
packages/dsh-shaders/skills/shader-debugging/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261020.ef66089, committed Oct 20, 2026
- Size
- 6,788 bytes
- Repository stars
- 10
- License
- AGPL-3.0
Reading a GLSL compiler's log, mapping its line numbers to your source, telling "compiles" from "draws", and the triage order for a black canvas. Read this when a shader fails in a way that does not make sense, or when it compiles and still shows nothing.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Debugging a shader Shader debugging is unusual: there is no breakpoint, no stack, and the compiler's message is often three lines away from the cause. The order below is the fastest path from "it does not work" to a specific fault. ## Step 1: read the rung, not the mood Every answer from this row names how far it got: ``` shader my-shader — FAILED at v1-static (es100) v1-static: only the static rules ran - no compiler was asked ``` `v1-static` on a machine that has a browser means the source was refused before a compiler saw it (a `#version` in a wrapper dialect, or desktop GLSL). `v2-compiled` means a real compiler accepted it - so a broken picture is not a syntax problem. Never say "it does not compile" from a `v1` answer. ## Step 2: trust the line numbers, and know why A compiler reports a line in the string it was HANDED. For an `es100` source that is your file, so line numbers match. For a wrapper dialect (Shadertoy, modules) the row prepends a header and appends `main()`, so the compiler's line 40 might be your line 27. The mapping is done for you: a diagnostic says ``` line 27 — 'dot2' : no matching overloaded function found ``` …
Read the whole file at its exact version.
How to install
mdr add vecnode/vncode/shader-debugging@sha256:21a8da1ca7ab3286The line at the top of this page pins the label git:20261020.ef66089, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_c425mwaxsnjf3dqe)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 20, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (6788 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
vecnode/vncode · 10 stars · license AGPL-3.0 · pushed 2026-10-20 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_c425mwaxsnjf3dqe GET https://markdownregistry.com/api/v1/resolve?ref=vecnode/vncode/shader-debugging GET https://markdownregistry.com/api/v1/blob/21a8da1ca7ab328654be614d294cf785b32b808100bf5f6ea5adf45692bdbfff
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.