web-games
Web browser game development principles. Framework selection, WebGPU, optimization, PWA.
77
72%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agent/skills/game-development/web-games/SKILL.mdQuality
Discovery
N/ABased on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
Something went wrong
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill excels at concise, well-organized reference material for browser game development decisions. The tables and decision trees are excellent for quick lookups. However, it functions more as a reference guide than an actionable skill - it tells Claude what tools and strategies to use but lacks executable code examples showing how to implement them.
Suggestions
Add executable code snippets for key operations like WebGPU feature detection (`if (navigator.gpu) {...}`), audio context initialization on user interaction, and tab visibility handling
Include a concrete example of PWA manifest and service worker setup for games, or reference a separate file with implementation details
Add validation steps for the asset loading strategy (e.g., how to verify compression is working, how to test offline functionality)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. Uses tables and decision trees to convey maximum information with minimal tokens. No unnecessary explanations of concepts Claude already knows. | 3 / 3 |
Actionability | Provides good strategic guidance with specific formats, tools, and patterns, but lacks executable code examples. The content describes what to do rather than showing how with copy-paste ready code snippets. | 2 / 3 |
Workflow Clarity | The decision tree for framework selection is clear, and loading phases are sequenced, but there are no validation checkpoints or feedback loops for the development process. Multi-step workflows like PWA setup lack explicit step sequences. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections and headers. For a skill of this scope (overview/principles document), the structure is appropriate with logical groupings. No deeply nested references or monolithic walls of text. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
90%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 | |
- Repository
- lchenrique/politron-ide
- Commit
7114206
- 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.