CtrlK
BlogDocsLog inGet started
Tessl Logo

unreal-engine-cpp-pro

Expert guide for Unreal Engine 5.x C++ development, covering UObject hygiene, performance patterns, and best practices.

57

Quality

66%

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/unreal-engine-cpp-pro/SKILL.md

The canonical home for this skill is unreal-engine-cpp-pro in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

78%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-organized, concise UE5 C++ reference with concrete executable snippets and a closing PR checklist that provides validation. Main weaknesses are a few partial code fragments (async loading, interface call) and the absence of explicit error-recovery feedback loops.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's UE knowledge, using tight bullet lists and code with minimal prose; only small explanatory clauses ('extremely useful for AI debugging', 'Fail hard in dev if missing') could be trimmed.

4 / 5

Actionability

Provides concrete, mostly executable C++ snippets (FindComponentByClass, interface Execute_ call, TSoftClassPtr, UE_LOG) and specific naming prefixes; falls short of 5 because some snippets are fragments and the async-loading example defers to a comment rather than showing the StreamableManager path.

4 / 5

Workflow Clarity

Organized as principles plus patterns with a closing 'Checklist before PR' that serves as an explicit validation checkpoint; no destructive/batch operations triggering the cap-3 rule, but it lacks explicit validate->fix->retry feedback loops elsewhere.

4 / 5

Progressive Disclosure

The skill is self-contained (~115 lines, no bundle files exist and none are referenced) with well-organized, clearly headed sections and easy navigation; per the scoring notes this qualifies for 5.

5 / 5

Total

17

/

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 identifies a specific niche (UE5 C++ development) but is framed as an abstract 'expert guide' rather than concrete actions and omits any explicit 'Use when' trigger guidance. Adding a concrete 'Use when' clause with natural trigger terms would lift completeness and trigger-term quality.

Suggestions

Add an explicit 'Use when ...' clause naming concrete trigger situations, e.g. 'Use when writing or optimizing Unreal Engine 5.x C++ (Actors, Components, UObjects, UFUNCTION/UCLASS reflection, Blueprint-exposed APIs).'

Replace abstract framing ('Expert guide for ... covering best practices') with concrete actions users would recognize (e.g. 'Expose UCLASS/UFUNCTION to Blueprints, apply UObject/GC hygiene, optimize Tick and casts').

Include natural synonyms users actually say (UE5, Blueprint, reflection, garbage collection, .uproject) to improve trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain ('Unreal Engine 5.x C++ development') plus a couple of concrete areas ('UObject hygiene, performance patterns'), but the actions are framed abstractly as 'Expert guide for / covering' rather than listing several specific concrete actions.

3 / 5

Completeness

It clearly states what the skill covers, but provides no explicit 'when to use' trigger guidance; the missing 'Use when' clause caps completeness at 3 per the guidelines.

3 / 5

Trigger Term Quality

'Unreal Engine 5.x' and 'C++' are natural user terms, but it lacks a 'Use when' clause and misses common variations (UE5, Blueprint, UCLASS, reflection) that users would say.

3 / 5

Distinctiveness Conflict Risk

The Unreal Engine 5.x C++ niche is specific and low-conflict, distinct from Blueprint-only or other-engine skills; falls just short of 5 because it lacks explicit anchoring trigger phrases.

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.