Skip to content
SkillModel-led3,060 tokens in use

Level Design

Engine-neutral level design with Godot checks: player metrics measured from the real controller, key and ability gating with a soft-lock check, and pacing as data.

9,682 stars on the repository Apache License 2.0gamedev-skills/awesome-gamedev-agent-skills · skills/disciplines/level-design
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 Level Design costs

93tokens idle
3,060tokens in use
3,988tokens, 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

Nothing detected: no shell, network, file writes, git or credentials in its files.

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
  • Frontmatter12/15
  • Structure25/25
  • Examples15/15
  • Output15/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 →
Good
  • Development activity92
  • Maintenance96
  • Community60
  • Maturity24
  • Momentum40

This skill treats a level as a sequence of intended experiences delivered through space. The order it follows: measure the character, block out with primitives, check reachability and pacing, collect playtest reports, then dress the level.

It includes three Godot 4.7 patterns: a headless script that measures the real jump of the game’s player scene, a pacing check over a list of beats, and a reachability search over a room graph that tracks which keys and abilities the player holds.

What You Get

  • A headless jump measurement that reports apex, reach and airtime from the real player scene
  • A sizing rule: required gaps at about 0.7 of measured reach, optional challenges near 0.95
  • A pacing check that flags too many high-intensity beats in a row, a missing rest before the climax and a level that does not open with a teach beat
  • A goal_reachable search over a room graph that finds soft-locks such as a red key that no room grants

Common Use Cases

  • Sizing gaps and ledges from the controller’s measured jump, with the formula as a first estimate only
  • Planning a critical path, optional branches and gating order for a metroidvania
  • Finding a soft-lock before any art is made
  • Reviewing a level that bores or confuses playtesters with specific questions

What Makes It Unique

The metrics come from running the game’s own player scene: with the example constants, the ideal arc gave 90 px and 206 px while the measured values were 93.6 px and 212 px. The reachability check tracks held keys, so it catches a key behind its own door that a simple connectivity flood fill would pass. It also tells the agent to ask the user for specific playtest reports, because it cannot watch players.

Under The Hood

The skill is instructions and one reference file on pacing and flow, with no scripts of its own. It tells the agent to write helper scripts and run them with Godot in headless mode: one instantiates the project’s player scene on a generated floor and presses input actions to measure the jump, and others run the pacing and reachability checks in the project’s headless test runner. It also mentions baking prototype geometry into static resources. It does not fetch web pages or call APIs.

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