CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

generate2dmap

Plan and build 2D game maps and scenes - top-down and side-scrolling levels, tilemaps, prop packs, parallax backgrounds and HD-2D battle or story plates - with collision, navigation and reachability checks, environment motion, a playable HTML preview and export to Tiled, Godot 4 or LDtk. Map art (terrain, tiles, props, plates, parallax layers) is image generation by default, through generate2dmedia route_media.py (the API when a key is configured, else the local Codex or Grok CLI); map data (layout, collision, exits, spawns) is written as data. Use for any map, level, room, scene, background, terrain or prop-kit request. Not for characters, creatures, items or FX (generate2dsprite), character animation (video2dsprite), code-drawn tiles or maps (codeart2d, only on request) or calling an image or video API by itself (generate2dmedia).

Quality

95%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

92%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A dense, highly actionable skill body: every pipeline step is an executable command with flags, validation gates and feedback loops are explicit, and detailed contracts are correctly deferred to one-level-deep reference files that all exist. The only ding is inline version/dependency requirements, which the rubric treats as time-sensitive content that should not live in the main body.

Suggestions

Move the dependency version requirements (Python 3.10+, numpy, Pillow, ffmpeg 5.1+, node) out of the Commands paragraph into a reference file or setup note, keeping time-sensitive version pins out of the always-loaded body.

A few Pipeline rows pack multiple tools and caveats into one cell (e.g. the validate row chains four commands plus review instructions); splitting the validate/preview chain into its own short numbered sequence would preserve density while improving scanability.

DimensionReasoningScore

Conciseness

The body is lean, telegraphic and assumes Claude's competence — no concept explanations, every section carries commands or rules — which sits at the top anchor. However, it embeds time-sensitive version requirements inline ('Needs Python 3.10+, numpy and Pillow... ffmpeg 5.1+ for scene motion') with no deprecated/old-patterns placement, which the guidelines say should penalize conciseness, placing it between the top two anchors.

4 / 5

Actionability

The Pipeline table is fully executable: copy-paste-ready command lines with concrete flags for every task (e.g. 'map_nav.py check --bundle <b> --output-dir <new>'), explicit exit-code semantics (exit 1 errors, 2 usage, 4 QA-fail), and output conventions ('Every tool writes a new --output-dir... refuses an existing one'). This matches the anchor for copy-paste ready commands covering the common cases.

5 / 5

Workflow Clarity

The sequence is explicit ('Block out navigation, make art and kit, place it, validate the data, preview, then export') with hard validation gates ('accepted only after map_bundle.py validate and map_nav.py check pass... route check says ok: true for every route'), feedback loops ('regenerate on failure', 'review nav-debug.png', staged publish with '--strict-qc publishes nothing on failure'), and an Acceptance checklist. Clear sequence with explicit validation, matching the top anchor.

5 / 5

Progressive Disclosure

The ~90-line body is an overview that routes to twelve well-signaled, one-level-deep reference files, each linked at its point of use with a purpose hint ('Choose by behaviour ([map-strategies.md]...; starting values per genre in [map-presets.md])'), plus schemas and a runtime module. All in-bundle referenced paths were verified to exist; references are one level deep, never nested.

5 / 5

Total

19

/

20

Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

An exemplary description: concrete capabilities with comprehensive coverage, natural trigger phrases for when to use it, and explicit disambiguation against every adjacent sibling skill. It is dense rather than padded, so its length is informational, not fluff.

DimensionReasoningScore

Specificity

The description lists many concrete, explicit actions with comprehensive coverage: 'Plan and build 2D game maps and scenes', 'tilemaps, prop packs, parallax backgrounds and HD-2D battle or story plates', 'collision, navigation and reachability checks', 'playable HTML preview and export to Tiled, Godot 4 or LDtk'. This matches the anchor for multiple specific concrete actions with comprehensive coverage, and coverage spans planning, art, data, validation, preview and export with no minor gaps, so it is not the level below.

5 / 5

Completeness

It explicitly answers both 'what' (a full list of concrete capabilities including validation, preview and export targets) and 'when' ('Use for any map, level, room, scene, background, terrain or prop-kit request'), and goes further with an explicit not-for clause. It clearly matches the anchor for both what and when with concrete trigger phrases, not the level below where 'when' could be more explicit.

5 / 5

Trigger Term Quality

'Use for any map, level, room, scene, background, terrain or prop-kit request' covers the natural synonyms a user would actually say, plus domain terms (tilemap, parallax, HD-2D plates, top-down, side-scrolling). Keyword coverage is comprehensive rather than merely good with a few natural terms missing, so it fits the top anchor.

5 / 5

Distinctiveness Conflict Risk

It carves out a clear niche (maps, levels, scenes, terrain, prop kits) and explicitly disambiguates each sibling skill that could conflict: 'Not for characters, creatures, items or FX (generate2dsprite), character animation (video2dsprite), code-drawn tiles or maps (codeart2d...) or calling an image or video API by itself (generate2dmedia)'. Minimal conflict risk, matching the top anchor.

5 / 5

Total

20

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 5 suspicious

Warning

referenced_paths_exist

Referenced path issues: 3 deeper-than-1-level

Warning

Total

14

/

16

Passed

Repository

0x0funky/agent-sprite-forge

Path

skills/generate2dmap/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.