game-development

Expert guidance for game development with C#/Unity, Lua scripting, and best practices for scalable game architecture

Quality

11%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./game-development/SKILL.md

Quality

Content

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill is essentially a collection of generic game development best practices that Claude already knows, presented as flat bullet-point lists with no executable code, no concrete examples, no workflows, and no progressive disclosure. It adds virtually no novel or actionable information to Claude's existing knowledge and wastes significant token budget on well-known concepts.

Suggestions

Replace generic advice with concrete, executable code examples (e.g., a complete object pooling implementation, a ScriptableObject data container pattern, a Lua module template) that Claude can directly apply.

Add specific multi-step workflows with validation checkpoints, such as 'Setting up a new Unity project with proper architecture' or 'Integrating Lua scripting into a Unity project' with clear sequenced steps.

Remove all content that states common knowledge Claude already has (e.g., 'use try-catch blocks', 'keep functions small', 'use local variables') and focus only on project-specific conventions, non-obvious patterns, or opinionated architectural decisions.

Split content into a concise SKILL.md overview with references to separate files for detailed topics (e.g., UNITY_PATTERNS.md, LUA_INTEGRATION.md, PERFORMANCE.md) to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The content is heavily padded with general best practices and concepts Claude already knows well (e.g., 'Use try-catch blocks for exception handling', 'Use local variables whenever possible for performance', 'Keep functions small and focused'). Almost every bullet point states common knowledge rather than providing novel, specific guidance.	1 / 3
Actionability	The entire skill consists of abstract guidelines and vague directives with zero concrete code examples, no executable commands, and no specific implementation patterns. Statements like 'Implement object pooling for frequently instantiated objects' describe rather than instruct.	1 / 3
Workflow Clarity	There are no multi-step workflows, no sequenced processes, and no validation checkpoints. The content is entirely a flat list of general principles with no guidance on how to actually execute a game development task from start to finish.	1 / 3
Progressive Disclosure	The content is a monolithic wall of bullet points with no references to external files, no layered structure, and no navigation aids. All content is dumped inline with repetitive sections (e.g., object pooling and ScriptableObjects are mentioned in multiple sections).	1 / 3
	Total	4 / 12 Passed

Description

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.

The description identifies a clear domain (game development with specific technologies) but fails to articulate concrete actions the skill performs, relying instead on vague terms like 'expert guidance' and 'best practices.' It completely lacks a 'Use when...' clause, making it difficult for Claude to know when to select this skill over others. The description reads more like a tagline than a functional skill selector.

Suggestions

Replace vague phrases like 'expert guidance' and 'best practices' with specific actions such as 'Generates Unity C# scripts, designs entity-component architectures, writes Lua game logic, and debugs gameplay systems.'

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about Unity projects, game scripting in C# or Lua, game architecture patterns, or building scalable game systems.'

Include additional natural trigger terms users might say, such as 'game engine', 'MonoBehaviour', 'gameplay programming', 'game loop', or 'scene management'.

Dimension	Reasoning	Score
Specificity	The description uses vague language like 'expert guidance' and 'best practices' without listing concrete actions. It names the domain (game development) and technologies (C#/Unity, Lua) but doesn't describe what specific actions the skill performs (e.g., 'generates game scripts', 'designs entity-component systems', 'debugs Unity projects').	1 / 3
Completeness	The description partially addresses 'what' (guidance for game development) but is vague about it, and completely lacks a 'when' clause or any explicit trigger guidance. The absence of a 'Use when...' clause caps this at 2 per the rubric, and the weak 'what' brings it down to 1.	1 / 3
Trigger Term Quality	Includes some relevant keywords users might say like 'Unity', 'C#', 'Lua', 'game development', and 'game architecture'. However, it misses common variations like 'game engine', 'gameplay', 'scripting', 'ECS', 'MonoBehaviour', '.cs files', or 'game design patterns'.	2 / 3
Distinctiveness Conflict Risk	The combination of C#/Unity and Lua scripting provides some specificity, but 'expert guidance' and 'best practices' are generic enough to overlap with general coding assistance skills or architecture skills. The game development focus helps somewhat but isn't sharply delineated.	2 / 3
	Total	6 / 12 Passed

Validation

100%

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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: mindrally/skills
Commit: 05a7130

Reviewed: 14 days 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.