CtrlK
BlogDocsLog inGet started
Tessl Logo

pc-games

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

54

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/game-development/pc-games/SKILL.md

The canonical home for this skill is pc-games in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

68%Weight 40%Scale 1-5

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

The body is a well-structured, concise reference with concrete tooling and technique guidance and clear navigation via numbered sections. Its main weakness is workflow clarity: it reads as reference material with no explicit validation checkpoints or sequenced multi-step process.

Suggestions

Add an explicit validation/feedback loop to the profiling workflow, e.g. 'Profile → identify bottleneck → apply fix → re-profile to confirm improvement.'

Move engine version specifics (Unity 6, Godot 4, Unreal 5) into a dedicated, clearly dated section so time-sensitive info does not pervade the body and date the skill.

Replace the generic 'When to Use' line with a concrete usage trigger or remove it to tighten the closing.

DimensionReasoningScore

Conciseness

The body is lean, relying on tables, a decision tree, and short bullets with almost no prose padding, but embedded engine version numbers (Unity 6, Godot 4, Unreal 5) and the vague 'When to Use' line are minor trimmable/time-sensitive items keeping it just below a 5.

4 / 5

Actionability

Provides concrete, specific guidance — named tools (Profiler Window, Unreal Insights), named techniques (Burst, Addressables, Nanite, Lumen), and actionable mapping tables (action→button, bottleneck→solution) — with only minor gaps, fitting 'mostly executable guidance' for an instruction-only skill.

4 / 5

Workflow Clarity

The engine-selection decision tree and 'Profiling First' section imply a sequence, but there are no explicit validation checkpoints or feedback loops and most sections are reference material rather than a sequenced workflow, matching 'steps present but checkpoints missing.'

3 / 5

Progressive Disclosure

Content is well-organized into six numbered sections with clear headers in a single self-contained file with no nested or buried references and no bundle files, matching 'good structure; most content appropriately placed; minor organization gaps.'

4 / 5

Total

15

/

20

Passed

Description

53%Weight 40%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 clearly scopes the skill to PC/console game development with three named focus areas, but lacks an explicit 'Use when...' trigger clause, which caps completeness and weakens trigger guidance. It is distinct and reasonably specific but would benefit from concrete trigger phrases.

Suggestions

Add an explicit 'Use when...' clause listing natural triggers, e.g. 'Use when building or optimizing PC/console games, choosing an engine, or implementing controller/Steam/console platform features.'

Convert topic-area nouns into concrete actions, e.g. 'Select an engine, implement platform features, optimize performance' to raise specificity.

Include natural user phrases and synonyms (controller support, Steam integration, certification, profiling) as trigger terms.

DimensionReasoningScore

Specificity

Names the domain ('PC and console game development principles') and lists three areas ('Engine selection, platform features, optimization strategies'), but these are topic-area nouns rather than concrete verb-actions, matching the 'names domain and 1-2 concrete actions' anchor better than the more action-oriented score 4.

3 / 5

Completeness

Provides a clear 'what' but no 'Use when...' clause or equivalent trigger guidance, so completeness is capped at 3 per the judging guideline.

3 / 5

Trigger Term Quality

Includes relevant keywords (PC, console, game development, engine) but misses common natural variations a user would say ('controller support', 'Steam integration', 'optimize my game'), fitting the 'some relevant keywords but missing variations' anchor.

3 / 5

Distinctiveness Conflict Risk

'PC and console game development principles' carves a clear niche distinct from web/mobile/data skills with only minor overlap risk against closely related skills, matching the 'mostly distinct' anchor.

4 / 5

Total

13

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.