mobile-games
Mobile game development principles. Touch input, battery, performance, app stores.
Install with Tessl CLI
npx tessl i github:lchenrique/politron-ide --skill mobile-gamesOverall
score
61%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
22%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is too terse and abstract, reading more like a list of topics than a functional skill description. It fails to specify concrete actions Claude can perform and provides no guidance on when to select this skill. The fragmented keyword style doesn't communicate capabilities effectively.
Suggestions
Rewrite to specify concrete actions (e.g., 'Guides mobile game architecture, optimizes touch controls, implements battery-efficient rendering, prepares builds for App Store and Google Play submission')
Add explicit 'Use when...' clause with trigger scenarios (e.g., 'Use when building games for iOS/Android, optimizing mobile game performance, or preparing game submissions to app stores')
Include common user terms like 'iOS game', 'Android game', 'Unity mobile', 'game optimization', 'mobile gaming'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses abstract, fragmented terms ('Touch input, battery, performance, app stores') without describing concrete actions. It doesn't specify what Claude actually does with these concepts. | 1 / 3 |
Completeness | Only vaguely addresses 'what' (mobile game development principles) and completely lacks any 'when' guidance or explicit triggers for when Claude should use this skill. | 1 / 3 |
Trigger Term Quality | Contains some relevant keywords like 'mobile game', 'touch input', 'app stores' that users might mention, but missing common variations like 'iOS', 'Android', 'Unity', 'game dev', or specific actions users would request. | 2 / 3 |
Distinctiveness Conflict Risk | The 'mobile game' focus provides some distinction, but 'performance' and 'app stores' could overlap with general mobile development or app deployment skills. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
73%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured reference skill that efficiently communicates mobile game development principles through concise tables. Its strength is token efficiency and organization, but it lacks executable code examples or specific implementation guidance, making it more of a checklist than an actionable skill.
Suggestions
Add concrete code snippets for key concepts like touch input handling or thermal monitoring (e.g., Unity/Godot examples for detecting device temperature)
Include specific commands or tools for app store submission validation (e.g., Xcode validation commands, bundletool for Android)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient use of tables to convey information. No unnecessary explanations of basic concepts; assumes Claude understands mobile development fundamentals. | 3 / 3 |
Actionability | Provides concrete guidelines (44x44 touch targets, 30 FPS) and clear tables, but lacks executable code examples or specific implementation commands. Content is more principle-based than copy-paste ready. | 2 / 3 |
Workflow Clarity | This is a principles/reference skill rather than a multi-step workflow, but the thermal management section hints at a process without explicit validation steps. For a reference skill, the organization is clear but lacks actionable sequences. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections and numbered headings. For a sub-100 line reference skill, the structure is appropriate with no need for external file references. Easy to navigate and scan. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
91%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
Total | 10 / 11 Passed | |
- 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.