Skip to content
SkillModel-led1,151 tokens in use

Engine Guide

Choose and use Godot, Bevy, Babylon.js, three.js or HTML for games, videos and interactive 3D, with install steps, build commands and headless capture.

7,372 stars on the repository MIT Licensehtdt/godogen · skills/engine-guide
npx skills add htdt/godogen
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing Engine Guide costs

105tokens idle
1,151tokens in use
8,642tokens, 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

shelldetected

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 →
Fair
  • Frontmatter12/15
  • Structure9/25
  • Examples3/15
  • Output5/15
  • Size15/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

No findings.

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Fair
  • Development activity68
  • Maintenance24
  • Community48
  • Maturity32
  • Momentum40

Engine Guide gives an agent one guide per engine: Godot 4 with C# or GDScript, Bevy in Rust, Babylon.js, three.js and an HTML and canvas stack. Each covers the project sketch, build commands, headless capture to screenshots and video, and the traps that pass a build but fail at runtime.

It also helps choose between engines by what you will hold at the end and how you want to watch progress. Because capture steps a fixed timestep per frame, the same guides cover videos, trailers, explainers and interactive pages made in an engine.

What You Get

  • A guide per engine: godot.md, godot-gdscript.md, bevy.md, babylon.md, threejs.md and html.md
  • A setup guide for installing ffmpeg, ImageMagick, Godot with .NET, Rust, Node and headless-browser tooling at current versions
  • Build gates and capture recipes that turn a scene into screenshots or an encoded video
  • A list of silent-failure traps for each engine, such as dropped nodes in a saved Godot scene or macOS hangs on fatal errors
  • Guidance for using an engine as a video studio with voice-over and music on one timeline

Common Use Cases

  • Start a game and pick the engine that fits how you want to follow progress
  • Make a trailer, explainer or product showcase as an engine-rendered video
  • Build an interactive 3D landing scene or data visualization in three.js or Babylon.js
  • Capture screenshots from a headless Godot or Bevy project
  • Continue work on an existing engine project with its traps in mind

What Makes It Unique

The guides skip what a model already knows and keep the failures that give no error: Godot scenes that save without some nodes, shadows that vanish without generated normals, and a macOS fatal error that hangs a headless run. Capture uses a fixed timestep, so render cost never shows in the output, which lets the same tools produce deterministic video. Engine choice is treated as the user’s call because switching later means a rewrite.

Under The Hood

The skill is reference text: SKILL.md plus one guide per engine and a setup file, with no scripts of its own. The instructions tell the agent to run shell commands: check installed versions, install toolchains and system packages, download Godot releases from GitHub, run dotnet, cargo, npm and Vite builds, start headless Godot under a timeout, render with xvfb, and encode video with ffmpeg. That means it downloads software, writes project files and captured frames into your project, and needs a hardware GPU path for video capture. It says to give you the one command to run when a step needs root.

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