Scene ready check
Run the scene gate on a glTF 2.0 file: structure validity (buffers/accessors consistent), triangle budget vs declared target platform, true scale in meters, collision geometry present. Trigger: "is this scene game-ready", "check my glTF", "validate this level". NOT a performance profiler and NOT an art review — materials, draw calls, and taste live in the engine.From its SKILL.md
npx -y skills add wjlgatech/design-anything --skill scene-ready-checkAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
3 things to look at
- 23 days oldThe repository was created 23 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 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.
What its file declares
Copied from the file, not written here
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
1.8 KB, 337 tokens by cl100k_base, as published. Nobody here has run it
scene-ready-check
When to use
Any glTF scene claiming to be game/sim ready — generated by brief-to-blueprint or exported from a DCC tool.
What it does
- S1 structure: glTF 2.0, embedded buffers decode to declared lengths, accessors fit their bufferViews, index counts divide by 3.
- S2 poly budget: total triangles ≤
data/scene.ymlbudget for the declared target (pc|mobile); unknown target ⇒ not measured ⇒ fail. - S3 true scale: meters declared (
asset.extras.units) and scene extent within sanity bounds — the units-bug catcher. - S4 collision: at least one
*_collisionnode exists.
Example
python3 examples/arena/generate.py scene.gltf
python3 pipeline/scene_gate.py scene.gltf --target pc --json
Verification (eval-with-teeth)
Success may be declared ONLY when the gate exits 0. The gate is held by tests that mutate the golden arena seven known-bad ways (corrupt buffer, fake index count, wrong units, 100× extent, missing collision, unknown target) and assert each fails:
python3 -m pytest tests/test_scene_gate.py -q
Safety
A READY scene is dimensionally sane and playable-shaped — not performant, not art-directed, not engine-imported. The report says so.
Cross-runtime
Python + PyYAML; exit codes gate any CI.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.