CtrlK
BlogDocsLog inGet started
Tessl Logo

mobile-games

Mobile game development principles. Touch input, battery, performance, app stores.

60

Quality

71%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/game-development/mobile-games/SKILL.md

The canonical home for this skill is mobile-games in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

82%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 a concise, well-structured reference that supplies concrete numeric targets and practices across the mobile-game domain without padding. It is reference-oriented rather than workflow-oriented, and a few entries stay directional instead of fully actionable.

DimensionReasoningScore

Conciseness

The body is a lean, table-and-bullet reference with no padded prose or explanations of concepts Claude already knows; every section earns its place, matching the 'lean and efficient; every token earns its place' anchor.

5 / 5

Actionability

Provides concrete, specific guidance with hard numbers ('44x44 points', '30 FPS', 'Target API: Current year's SDK', '64-bit: Required'), and as an instruction-only skill absence of code is not penalized, but some entries ('Limit CPU/GPU usage', 'Throttle when hot') remain directional rather than fully actionable, fitting 'mostly executable guidance; minor gaps'.

4 / 5

Workflow Clarity

Content is organized into clearly numbered, well-sequenced topical sections; as a principles/reference skill there is no destructive batch operation requiring validation, so the clear organization scores well, though the closing 'When to Use' line is vague, matching 'clear sequence with most checkpoints present; minor gaps'.

4 / 5

Progressive Disclosure

The content is self-contained in one well-organized file with clear section headers and tables and no broken or nested references (no bundle files exist), giving good structure; it is slightly longer than the simple-skill 50-line threshold, so it lands at 'good structure; minor organization gaps' rather than a 5.

4 / 5

Total

17

/

20

Passed

Description

61%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 clearly identifies a distinct niche and surfaces relevant natural keywords, but it lists covered topics rather than concrete actions and omits any explicit 'Use when' trigger clause, capping completeness and specificity.

Suggestions

Add an explicit 'Use when...' trigger clause, e.g. 'Use when building or optimizing mobile games, or when the user mentions touch input, battery life, thermal limits, or app store requirements.'

Reframe the topic list as concrete actions the skill performs (e.g. 'Optimize touch input, battery, and thermal performance; prepare builds for iOS App Store and Google Play.') to lift specificity.

Include synonyms or platform-specific terms (e.g. 'iOS', 'Android', 'Google Play', 'App Store') to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

Names the domain ('Mobile game development principles') plus several concrete topic areas ('Touch input, battery, performance, app stores'), but these are covered topics rather than concrete actions the skill performs, fitting the 'names domain and 1-2 concrete actions but not comprehensive' anchor.

3 / 5

Completeness

A clear 'what' is present (mobile game development principles across touch, battery, performance, app stores) but there is no 'Use when...' or equivalent trigger clause, so per the rubric cap the missing explicit trigger guidance limits completeness to 3.

3 / 5

Trigger Term Quality

Includes natural user-facing phrases like 'Touch input', 'battery', 'performance', and 'app stores' alongside 'mobile game development', giving good keyword coverage though missing synonyms or extensions, matching the 'good keyword coverage; a few natural terms missing' anchor.

4 / 5

Distinctiveness Conflict Risk

The mobile-game-development niche with specific triggers (touch input, battery, app stores) is mostly distinct from other skills with only minor overlap risk, matching the 'mostly distinct; minor overlap risk' anchor.

4 / 5

Total

14

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-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.