game-development
Expert guidance for game development with C#/Unity, Lua scripting, and best practices for scalable game architecture
39
Quality
27%
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 ./game-development/SKILL.mdQuality
Discovery
32%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 identifies its domain and key technologies but relies on vague terms like 'expert guidance' and 'best practices' instead of concrete actions. The complete absence of a 'Use when...' clause significantly weakens its utility for skill selection, and the abstract framing makes it harder for Claude to know precisely when to apply this skill.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user asks about Unity projects, game scripting, player mechanics, or game architecture patterns'
Replace 'expert guidance' with specific actions like 'Create game mechanics, implement player controllers, design state machines, optimize game loops'
Include additional natural trigger terms users might say: 'gamedev', 'game engine', 'sprites', 'collision detection', 'game AI', '.cs files', 'MonoBehaviour'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (game development) and technologies (C#/Unity, Lua scripting) but uses vague terms like 'expert guidance' and 'best practices' without listing concrete actions like 'create player controllers', 'implement save systems', or 'debug physics'. | 2 / 3 |
Completeness | Describes what the skill covers (game development guidance) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing explicit trigger guidance caps this at 2, but the 'what' is also weak due to vague 'guidance' framing. | 1 / 3 |
Trigger Term Quality | Includes relevant keywords like 'game development', 'C#', 'Unity', 'Lua', and 'game architecture' that users might mention, but misses common variations like 'gamedev', 'game engine', 'scripting', 'game logic', or specific task terms like 'sprites', 'collision', 'AI behavior'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of C#/Unity and Lua provides some distinctiveness, but 'game development' and 'best practices' are broad enough to potentially overlap with general coding skills or other game-related skills. The architecture focus helps but isn't strongly differentiated. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
22%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill reads more like a style guide or checklist of principles rather than actionable guidance for game development. It lacks concrete code examples, executable snippets, and clear workflows that would help Claude perform specific game development tasks. The content would benefit significantly from replacing abstract statements with working code examples and defining clear processes for common game development scenarios.
Suggestions
Add concrete, executable code examples for each major concept (e.g., show actual object pooling implementation, coroutine usage, ScriptableObject setup)
Define clear workflows for common tasks like 'Setting up a new Unity project', 'Implementing a game feature', or 'Debugging performance issues' with validation steps
Remove redundant mentions (object pooling, coroutines appear multiple times) and eliminate explanations of concepts Claude already knows
Split detailed topics (animation systems, Job System, physics optimization) into separate reference files and link to them from the main skill
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably organized but includes some redundant information (object pooling mentioned twice, coroutines mentioned twice) and explains concepts Claude already knows like basic error handling patterns and what prefabs are. | 2 / 3 |
Actionability | The skill provides only abstract guidance and principles without any concrete code examples, executable commands, or copy-paste ready snippets. Statements like 'Use MonoBehaviour for game object behaviors' describe rather than instruct. | 1 / 3 |
Workflow Clarity | No multi-step processes are defined, no validation checkpoints exist, and there's no sequencing for common game development workflows like setting up a project, implementing a feature, or debugging. The content is purely declarative principles. | 1 / 3 |
Progressive Disclosure | The content has reasonable section organization with clear headers for different topics (Unity, Lua, C#), but it's a monolithic document with no references to external files for detailed topics like animation systems or Job System usage that warrant deeper coverage. | 2 / 3 |
Total | 6 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 12 / 16 Passed | |
- Repository
- mindrally/skills
- Commit
47f47c1
- 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.