CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

68

Quality

83%

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

78%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 concise, well-organized instruction-only skill with a solid QA checklist, but its guidance is largely abstract and lacks the concrete values, APIs, or examples that would make it fully actionable.

Suggestions

Add concrete specifics to Controls: name touch-target minimum sizes, the safe-area API (e.g., env() safe-area-inset), and a multi-touch gesture example rather than 'provide a clear movement control'.

For Responsive HUD, give concrete breakpoint/viewport dimensions or a layout snippet for portrait vs landscape instead of only listing what to keep legible.

In Performance and QA, specify the 'repository-approved browser' and give device-appropriate quality defaults as actual values (e.g., pixel ratio cap, target FPS) so the QA checklist is verifiable.

DimensionReasoningScore

Conciseness

The body is lean across three short sections with no padding and no explanation of concepts Claude already knows; every token earns its place, matching the 'lean and efficient; assumes Claude's competence' anchor.

5 / 5

Actionability

Guidance is directive but abstract ('Provide a clear movement control', 'avoid overlapping action zones') with no concrete values, code, or APIs (e.g., specific safe-area APIs or touch-target sizes); it sits between high-level hints and incomplete concrete guidance, matching anchor 3.

3 / 5

Workflow Clarity

The skill is simple and under 50 lines with a clear thematic organization and an explicit QA verification checklist ('Test touch targets, multi-touch, long sessions...'), providing most checkpoints with only minor sequencing gaps.

4 / 5

Progressive Disclosure

No bundle files are needed and the skill is under 50 lines with well-organized sections, so the simple-skill exception applies and progressive disclosure scores 5 on well-organized sections alone.

5 / 5

Total

17

/

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.

A strong, specific description with explicit 'what' and 'when' guidance and a clear niche. The only mild weakness is that the leading verbs (build/tune/test) are broad and some natural trigger synonyms are absent.

DimensionReasoningScore

Specificity

The description opens with three concrete verbs ('Build, tune, or test') on a specific domain (Three.js game for mobile web) and enumerates many capability areas, matching the 'several specific actions; minor gaps' anchor rather than the fully comprehensive anchor 5.

4 / 5

Completeness

It explicitly answers both 'what' ('Build, tune, or test a Three.js game for mobile web') and 'when' with concrete trigger phrases ('Use for...'), matching the anchor for clearly and explicitly answering both with concrete trigger phrases.

5 / 5

Trigger Term Quality

'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' gives good natural-keyword coverage a user would actually say, but misses some common synonyms and is not exhaustive enough for anchor 5.

4 / 5

Distinctiveness Conflict Risk

'Three.js game for mobile web' is a clear niche with distinct triggers (touch inventory, safe areas, responsive HUD) and minimal overlap risk with other skills.

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.

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.