pc-games

PC and console game development principles. Engine selection, platform features, optimization strategies.

Quality

36%

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 ./skills/game-development/pc-games/SKILL.md

Quality

Content

36%Scale 1-5

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

This skill reads as a high-level reference card or cheat sheet for game development concepts rather than an actionable skill that teaches Claude how to perform specific tasks. It lacks executable code, concrete implementation steps, and workflow sequences. While the tables and decision tree provide some structure, most of the content covers general knowledge Claude would already possess.

Suggestions

Add concrete, executable code examples for each engine (e.g., setting up input abstraction in Unity, Godot, and Unreal with actual code snippets).

Define a clear workflow for at least one key process, such as 'Setting up a new project with platform integration,' with numbered steps and validation checkpoints.

Remove or significantly condense tables that list widely-known information (e.g., what Steam achievements are) and replace with specific implementation guidance Claude wouldn't already know.

Remove the vacuous 'When to Use' section and the generic closing quote, which add no value.

Dimension	Reasoning	Score
Conciseness	The content is reasonably efficient with good use of tables and decision trees, but includes some information Claude already knows (e.g., what Steam achievements are, basic engine feature comparisons that are widely known). The 'When to Use' section at the end is vacuous filler. Some tables add little value beyond what Claude would already know.	3 / 5
Actionability	The skill is almost entirely descriptive rather than instructive. There are no executable code examples, no specific commands, no concrete implementation steps. The 'input abstraction' section shows a conceptual mapping but not how to implement it in any engine. It reads more like a reference card than actionable guidance Claude could execute.	2 / 5
Workflow Clarity	There is no clear multi-step workflow or process sequence. The decision tree for engine selection is a useful structure, but the rest is a collection of reference tables without sequencing, validation steps, or any process flow. The 'Profiling First' section implies a workflow but doesn't articulate steps or checkpoints.	2 / 5
Progressive Disclosure	The content is organized into clear sections with headers and tables, which aids navigation. However, there are no references to external files for deeper content (e.g., engine-specific setup guides, platform certification details), and several sections could benefit from being split out. No bundle files exist to support deeper exploration.	3 / 5
	Total	10 / 20 Passed

Description

36%Scale 1-5

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 (PC and console game development) but remains at a high level, listing topic areas rather than concrete actions the skill performs. It lacks a 'Use when...' clause, making it difficult for Claude to know precisely when to select this skill. The trigger terms are too few and too generic to reliably distinguish this from related skills.

Suggestions

Add a 'Use when...' clause with concrete trigger phrases, e.g., 'Use when the user asks about game engines, console porting, platform-specific optimization, or PC/console game architecture.'

Replace abstract topic labels with specific actions, e.g., 'Guides engine selection (Unity, Unreal, Godot), advises on platform-specific features (Xbox, PlayStation, Switch, PC), and recommends performance optimization strategies (frame rate, memory, GPU/CPU profiling).'

Include natural synonyms and specific terms users would mention, such as 'game engine', 'Unreal Engine', 'Unity', 'frame rate', 'porting', 'cross-platform', 'rendering pipeline'.

Dimension	Reasoning	Score
Specificity	Names the domain (PC and console game development) and mentions a few high-level topics (engine selection, platform features, optimization strategies), but these are categories rather than concrete actions. No specific verbs describing what the skill actually does.	2 / 5
Completeness	Provides a vague 'what' (game development principles, engine selection, platform features, optimization) but has no 'when' clause at all. The lack of explicit trigger guidance caps this dimension, and the 'what' itself is more of a topic list than a clear capability description.	2 / 5
Trigger Term Quality	Includes some relevant keywords like 'game development', 'engine selection', 'optimization', 'PC', and 'console', but misses many natural user phrases such as 'game engine', 'Unity', 'Unreal', 'performance', 'porting', 'frame rate', 'GPU', 'Xbox', 'PlayStation', 'Nintendo Switch', etc.	3 / 5
Distinctiveness Conflict Risk	Somewhat specific to PC/console game development, which narrows it from general game development, but could still overlap with skills about game design, game engines, performance optimization, or mobile game development. The boundaries are not clearly drawn.	3 / 5
	Total	10 / 20 Passed

Validation

90%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/game-development/pc-games/SKILL.md
Commit: 57c135b

Reviewed: 3 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.