SkillAgentSearch skills...

author-game-levels

Author or revise readable, flat-world Three.js game levels. Use for movement and camera routes, collision and navigation, encounter zones, landmarks, objectives, pickups, motivated lighting, visibility, deterministic level data, or desktop and mobile playthrough verification.

Install / Use

npx skills add MengTo/Skills --skill author-game-levels

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

83/100

Category

Other

Supported Platforms

Universal

Tags

Our assessment of author-game-levels

author-game-levels scores 83/100 on our quality scale, 242nd of 330 Other skills we index.

Its SKILL.md is 4.3 KB long, split into 7 sections and no code examples: a solid amount of guidance for an agent.

With 6,252 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
11/20
Description
15/15
Adoption
16/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so author-game-levels is actively maintained.
  • Our last check on 2026-11-06 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-02. Automated pattern scan on 2026-10-02. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

author-game-levels compared with similar skills

All 4 of these similar skills score higher than author-game-levels; compare them before choosing.

SkillScoreStarsUpdatedFormat
author-game-levels (this skill)by MengTo836.3k54d agoSKILL.md
x402by browser-use100121.0k3d agoSKILL.md
algorithmic-artby anthropics100177.9k55d agoSKILL.md
pptxby anthropics100177.9k55d agoSKILL.md
designby nextlevelbuilder100149.0k6d agoSKILL.md

Frequently asked questions

How do I install author-game-levels?
Run npx skills add MengTo/Skills --skill author-game-levels. The install tabs above show the steps for each supported agent.
Which AI agents does author-game-levels work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is author-game-levels safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is author-game-levels still maintained?
The repository was last updated about 2 months ago, so author-game-levels is actively maintained.

name: author-game-levels description: Author or revise readable, flat-world Three.js game levels. Use for movement and camera routes, collision and navigation, encounter zones, landmarks, objectives, pickups, motivated lighting, visibility, deterministic level data, or desktop and mobile playthrough verification.

Author Game Levels

Treat architecture as gameplay communication. Every route, arena, gate, prop, and light must help the player read movement, threats, objectives, or state.

Enforce one gameplay plane

Keep all collision, navigation, encounter routes, objectives, pickups, and player movement on one accessible plane.

  • Do not add stairs, ramps, raised platforms, drop-offs, cliffs, bridges, ledges, pits, or vertical traversal.
  • Do not change gameplay elevation for shortcuts, arenas, hazards, rewards, or visual variety.
  • If visual height is requested later, keep it non-walkable background dressing. It must not alter navigation, camera occlusion, threat visibility, targetability, or player movement.

Separate level systems

Maintain explicit, independently testable layers for:

  • authored level data and stable zone/anchor IDs;
  • visual geometry and non-walkable background dressing;
  • simplified collision geometry;
  • flat navigation data and movement clearance;
  • encounter, enemy, gate, reset, pickup, objective, and exit zones.

Share stable IDs and transforms between layers, but never infer collision, navigation, or encounter boundaries from decoration alone.

Lay out readable play

  1. Define the architectural purpose of each space: traversal, orientation, combat, recovery, reward, transition, or objective.
  2. Preserve clear movement, camera, and dodge corridors at the intended play distance.
  3. Keep threats, pickups, exits, gates, and interaction targets visible before commitment.
  4. Telegraph encounters through visible arena shape, approach, state change, and stable zone anchors.
  5. Deliberately place arenas, gates, checkpoints, retry spawns, and reset paths. Prevent soft locks, duplicate rewards, hidden re-entry, and enemies pursuing through unrelated zones.
  6. Use landmarks, lighting, contrast, and composition to guide without hiding hazards or making the route ambiguous.

Motivate every local light

Attach every local torch, lantern, brazier, or similar light spatially to a visible emitter. Its position, range, color, intensity, shadowing, and occlusion behavior must match what that emitter appears able to produce.

  • Forbid unexplained floating local lights.
  • Keep a source-to-light inventory with emitter ID, light ID, attachment transform, type, range, color/intensity, occlusion intent, enabled state, and fallback behavior.
  • Move the light with a moving emitter. Disable or remove its local contribution when the emitter is disabled, hidden, destroyed, or unloaded.
  • Document ambient or world lighting separately. Use it for deliberate global visibility or mood, never to fake a torch or other local source.

Validate data and geometry

  • Assert that all walkable collision, navigation vertices/links, encounter anchors, gates, objectives, pickups, exits, and reset points remain on the configured gameplay plane within a small tolerance.
  • Reject walkable slopes, out-of-plane links, vertical shortcuts, elevated spawn points, and level data that implies height-changing traversal.
  • Check collision/nav agreement, route clearance, zone containment, deterministic gate/reset behavior, stable anchor references, and persistence of level progress.
  • Validate source-to-light inventory completeness, emitter/light attachment, range/color intent, and moving or disabled emitter state transitions.

Prove traversal in the browser

Run deterministic route, collision, navigation, encounter, reset, and lighting fixtures, then traverse every critical and optional route in the repository-approved browser.

  • On desktop and mobile, verify uninterrupted flat movement, dodge clearance, camera framing, threat/pickup/exit visibility, encounter telegraphs, gates, retry paths, and touch controls.
  • Exercise moving and disabled emitter cases and confirm no light remains detached or unexplained.
  • Inspect dense views for occlusion, console health, frame time, draw calls, memory stability, and long-session lighting cost.
  • Report new failures separately from existing baseline issues.

Related Skills

View on GitHub
GitHub Stars6.3k
CategoryOther
Updated1mo ago
Forks741

Languages

HTML

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions