CtrlK
BlogDocsLog inGet started
Tessl Logo

build-game-map-editor

Build, extend, or audit production-linked browser map editors for Three.js and isometric games. Use when Codex needs to create a private director view, derive a versioned editor document from authored placements, add outliner, layer, selection, drag, snap, inspector, or camera controls, expose enemy aggro, leash, or patrol overlays, implement local draft import, export, undo, and reset, secure an editor route with IP and password sessions, or validate and release a map editor without mutating live gameplay data.

75

Quality

92%

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

85%

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

A well-structured, actionable instruction body with a clear lifecycle, explicit validation checkpoints, and a single well-signaled reference file. Its main weakness is moderate redundancy across the document-definition, integration, and verification sections that slightly inflates token usage.

Suggestions

Consolidate the validation rules that are currently restated across 'Define a versioned editor document', 'Integrate a reviewed draft', and 'Verify the editor' into a single canonical checklist referenced from each section.

Move the per-kind inspector settings and access-control bullet lists toward the reference file, keeping only the governing contracts in the body to reduce length.

Add a short 'When to read the reference' pointer earlier in the body so the single external file's role is signaled before the final section.

DimensionReasoningScore

Conciseness

The body is largely lean and assumes competence, but validation requirements are restated across 'Define a versioned editor document', 'Integrate a reviewed draft', and 'Verify the editor', adding redundancy that could be tightened.

2 / 3

Actionability

Guidance is concrete and specific ('reject nonzero Y', '{ x, y: 0, z }', 'HMAC', 'HTTP-only, strict same-site cookie', 'exact IP allowlist'); as an instruction-only skill, the absence of in-body code is acceptable because the reference holds executable commands.

3 / 3

Workflow Clarity

It states an explicit lifecycle ('production source -> editor document -> isolated draft -> validated export -> reviewed source integration') and the integration section is a numbered sequence with explicit validation checkpoints and test coverage.

3 / 3

Progressive Disclosure

The body acts as a well-organized overview and signals one clearly labeled, one-level reference ('references/vesperfall-implementation.md') that exists and holds the concrete implementation map and commands.

3 / 3

Total

11

/

12

Passed

Description

100%

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

A strong, third-person description that covers concrete capabilities, natural trigger terms, and an explicit 'Use when' clause for a clearly bounded game-editor niche. Minor jargon ('production-linked', 'director view') slightly tempers naturalness but does not undermine clarity.

DimensionReasoningScore

Specificity

The description lists many concrete actions such as 'add outliner, layer, selection, drag, snap, inspector, or camera controls' and 'secure an editor route with IP and password sessions', matching the 'multiple specific concrete actions' anchor.

3 / 3

Completeness

It explicitly answers both what ('Build, extend, or audit... map editors') and when ('Use when Codex needs to...'), with an explicit 'Use when' trigger clause.

3 / 3

Trigger Term Quality

It includes natural domain terms a user would say ('map editor', 'Three.js', 'outliner', 'selection', 'snap', 'inspector', 'import, export, undo, and reset'), giving good coverage despite some jargon like 'production-linked'.

3 / 3

Distinctiveness Conflict Risk

The niche is specific (Three.js/isometric game map editors, paused director view, no live gameplay mutation) and the triggers are distinct, making conflict with other skills unlikely.

3 / 3

Total

12

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
MengTo/Skills
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.