mobile-games

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

Quality

57%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/game-development/mobile-games/SKILL.md

Quality

Content

65%

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 lean, well-organized table-based reference that respects the token budget, but much of its guidance is directional rather than implementable and it offers no sequenced workflow or external reference structure. Adding concrete implementation detail and a checkpointed workflow for a common task would strengthen it.

Suggestions

Turn vague entries into concrete, implementable guidance (e.g., code/config for 44x44 hit areas, FPS caps, or thermal throttling thresholds) instead of phrases like 'Limit CPU/GPU usage'.

Add a sequenced workflow with validation checkpoints for at least one common task, such as an app store submission checklist (build -> validate metadata -> upload -> respond to review).

Consider splitting detailed reference material (app store requirements, monetization models) into separate reference files linked from SKILL.md to enable one-level-deep progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is compact tables with terse entries and no over-explanation of concepts Claude already knows, respecting the token budget and assuming competence.	3 / 3
Actionability	It mixes concrete specifics ('44x44 points', '30 FPS', '64-bit \| Required') with directional phrases ('Limit CPU/GPU usage', 'Responsive UI') and gives no implementation steps, matching the score-2 anchor.	2 / 3
Workflow Clarity	Sections are well-organized and numbered, but there is no multi-step sequenced workflow with validation checkpoints; it is a reference compilation rather than a process, and the >50-line simple-skill exemption does not apply.	2 / 3
Progressive Disclosure	Content is split into clearly headed sections but it is a monolithic ~100-line inline reference exceeding the 50-line 'sections-only = 3' threshold, with no external file references for the more detailed material.	2 / 3
	Total	9 / 12 Passed

Description

50%

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 concise and names a clear domain with relevant subtopics, but it relies on topic nouns rather than concrete actions and omits any explicit 'Use when...' trigger guidance. Adding action verbs and a trigger clause would lift the weaker dimensions.

Suggestions

Add an explicit 'Use when...' clause (e.g., 'Use when building or optimizing mobile games, or when the user mentions touch controls, battery life, thermal limits, or app store submission') to raise completeness and trigger coverage.

Replace topic nouns with concrete actions (e.g., 'Design touch controls, optimize battery and thermals, prepare app store submissions') to improve specificity.

Broaden natural keyword variations users actually say ('mobile games', 'iOS/Android game', 'app store review', 'frame rate', 'thermal throttling') to improve trigger-term quality.

Dimension	Reasoning	Score
Specificity	It names the domain and concrete subtopics ('Touch input, battery, performance, app stores') but lists topic nouns rather than concrete actions like the score-3 anchor ('Extract text... fill forms').	2 / 3
Completeness	It states what the skill covers but has no 'Use when...' clause or equivalent trigger guidance, which the guidelines cap at 2.	2 / 3
Trigger Term Quality	Terms like 'mobile game', 'touch input', 'battery', and 'app stores' are fairly natural but the list is thin and missing common variations, matching the score-2 anchor.	2 / 3
Distinctiveness Conflict Risk	'Mobile game development' is a recognizable niche but, being brief and trigger-less, could still overlap with general game-dev or mobile-app skills.	2 / 3
	Total	8 / 12 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning

	Total	15 / 16 Passed

Repository: vudovn/ag-kit
Path: .agents/skills/game-development/mobile-games/SKILL.md
Commit: 04514f0

Reviewed: about 13 hours ago

Table of Contents

Discovery Implementation Validation

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.