CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

build-mobile-threejs-games

Build, tune, or test a Three.js game for mobile web. Use for touch movement, action controls, target selection, touch inventory, safe areas, portrait/landscape layouts, responsive HUD, battery/performance budgets, and real mobile browser QA.

Quality

84%

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

72%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.

The body is exceptionally concise and well-organized for a short, self-contained skill, with no wasted tokens. However, it reads as a requirements checklist rather than actionable guidance: it says what to ensure (controls, HUD legibility, QA coverage) without how to achieve or verify any of it. Adding a few concrete techniques, measurable criteria, or an ordered test sequence would substantially raise actionability and workflow clarity.

Suggestions

Add concrete, executable specifics for the weakest areas: e.g., minimum touch-target size in CSS pixels, pointer/touch event handling patterns for the movement control, or a code snippet for safe-area insets.

Provide a short ordered workflow (build controls -> layout HUD -> set quality defaults -> run QA checklist) with explicit validation checkpoints, such as verifying orientation change does not reset state.

Include measurable pass/fail criteria for the QA section (e.g., frame-rate budget on low-end quality, long-session memory ceiling) so testing is verifiable rather than implied.

DimensionReasoningScore

Conciseness

The ~15-line body is lean and directive ("Treat mobile as a primary control and performance surface"), assumes Claude's competence, and contains no padding or explanation of known concepts. Every token earns its place, matching the anchor 5 example.

5 / 5

Actionability

The body provides concrete checklists ("Test touch targets, multi-touch, long sessions, audio unlock, pause/background return, reduced motion, low-end quality") but gives no specific techniques, commands, code snippets, or measurable criteria for executing them. It has some concrete guidance with key execution details missing, matching anchor 3; it is not anchor 4 because nothing is directly executable or copy-paste ready.

3 / 5

Workflow Clarity

The content is organized into thematic sections (Controls, Responsive HUD, Performance and QA) but presents no build-tune-test sequence and no validation checkpoints. Since this is a multi-faceted skill rather than a single unambiguous action, the simple-skill exception does not apply, so it sits at anchor 3 (structure present, checkpoints missing) rather than 5.

3 / 5

Progressive Disclosure

The skill is under 50 lines, self-contained, and needs no external references; per the rubric guideline, well-organized sections alone qualify it for 5. The three clear section headers make navigation trivial, and no bundle files exist to misplace.

5 / 5

Total

16

/

20

Passed

Description

87%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.

The description is well-crafted: it uses third person, states concrete actions, and includes an explicit 'Use for' clause with specific trigger phrases covering controls, layout, HUD, and performance. It is concise and highly distinct within the skill namespace. Minor room remains in synonym coverage (e.g., 'mobile game', platform terms).

Suggestions

Add one or two common synonyms such as 'mobile game' or 'smartphone browser' to broaden natural trigger coverage.

Optionally mention deployment or asset-pipeline actions if those are in scope, to round out capability coverage.

DimensionReasoningScore

Specificity

"Build, tune, or test a Three.js game for mobile web" names three concrete actions in a well-defined domain, matching the anchor for several specific actions with minor gaps. It falls short of 5 because it does not comprehensively enumerate capabilities (e.g., asset optimization, deployment), and exceeds 3 because it goes beyond 1-2 actions.

4 / 5

Completeness

The description explicitly answers both what ("Build, tune, or test a Three.js game for mobile web") and when ("Use for touch movement, action controls, ... and real mobile browser QA") with concrete trigger phrases, matching the anchor 5 example structure exactly.

5 / 5

Trigger Term Quality

Natural trigger terms like "touch movement", "responsive HUD", "portrait/landscape layouts", and "battery/performance budgets" give good keyword coverage. A few natural user phrasings are missing (e.g., "mobile game", common platform names), which keeps it below the comprehensive-synonym coverage of 5 but clearly above the partial coverage of 3.

4 / 5

Distinctiveness Conflict Risk

"Three.js game for mobile web" carves out a clear niche, and the touch/HUD/safe-area/mobile-QA triggers are distinct from generic web development or desktop Three.js skills, giving minimal conflict risk. Anchor 4's "minor overlap risk" would apply only if it also claimed desktop Three.js work.

5 / 5

Total

18

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

MengTo/Skills

Path

agent-skills/game-development/build-mobile-threejs-games/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.