CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

unreal-mcp

Automate Unreal Engine editor scenes, actors, and renders.

Quality

78%

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 ./optional-skills/creative/unreal-mcp/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

92%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.

This is a strong skill body: concrete, executable, and full of live-verified domain knowledge Claude could not guess (serial game thread, discovery-mode tool surface, calibration conventions). Multi-step workflows carry explicit validation checkpoints and a closing checklist, and detail is correctly pushed to five real, well-labeled reference files. Only minor trims to the intro and the Operating-Loop/Pitfalls overlap would tighten it further.

DimensionReasoningScore

Conciseness

The body is dense with non-obvious, project-specific facts (start order, serial game-thread rule, qualified toolset names, calibration conventions) and never explains concepts Claude already knows. Minor over-explanation remains — the intro paragraph about the Hermes catalog and the deliberate repetition between Operating Loop rules and the Pitfalls list could be trimmed — fitting 'Efficient; minor instances of over-explanation' rather than score 5's 'every token earns its place'.

4 / 5

Actionability

Guidance is copy-paste ready throughout: exact plugin names ('Unreal MCP', 'AllToolsets'), menu paths, console commands ('ModelContextProtocol.StartServer'), the install command ('hermes mcp install unreal-engine'), bind URL, config keys, fully-qualified toolset names, and concrete values (165 cm eye height, 'intensity: 10', 120 s timeout). This matches 'Fully executable; copy-paste ready code or commands; specific examples cover the common cases'.

5 / 5

Workflow Clarity

Every process is a numbered sequence with explicit validation: prerequisites in dependency order, a per-session checklist, a fixed 3-step discovery walk, a 7-step operating loop with 'read every result' and read-back-after-write checks, and a final Verification Checklist. Feedback loops for error recovery are explicit (screenshot → art-direct against brief → fix before moving on; stop-and-diagnose on non-success). This matches the top anchor.

5 / 5

Progressive Disclosure

SKILL.md is a lean overview; all five referenced files exist in references/ and their contents match what the Reference Files table claims. References are one level deep, clearly signaled with per-file content descriptions, and load-on-demand guidance is given ('Load on demand; keep SKILL.md-level rules in mind'). This matches 'Clear overview with well-signaled one-level-deep references; content appropriately split; easy navigation'.

5 / 5

Total

19

/

20

Passed

Description

57%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 identifies a distinct, well-scoped niche but under-sells it: a single generic verb ('Automate') covers what are actually many concrete capabilities, and there is no 'when' trigger guidance. It functions as a domain label rather than a complete trigger. Adding an explicit use-when clause with concrete actions and common synonyms (UE5, level, lighting, cinematics) would lift it substantially.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user wants anything done in the Unreal Editor: building or dressing levels, spawning/moving actors, lighting and atmosphere, camera shots, screenshots or renders.'

Replace the single verb 'Automate' with several concrete actions so the capability surface is visible: 'Build and dress levels, spawn and move actors, set up lighting and materials, frame camera shots, and capture screenshots and renders in the Unreal Engine editor.'

Include natural synonyms and version strings users actually say — 'UE5', 'level', 'lighting', 'cinematic' — to improve trigger matching.

DimensionReasoningScore

Specificity

The description names the domain ("Unreal Engine editor") and its objects ("scenes, actors, and renders") but relies on a single generic verb, "Automate". It matches the anchor 'Names domain and 1-2 concrete actions, but not comprehensive' rather than score 4, which requires several distinct specific actions (e.g. 'spawn actors, set up lighting, capture renders').

3 / 5

Completeness

The 'what' is clear (automating Unreal Engine editor scenes, actors, and renders), but there is no 'Use when...' clause or any trigger guidance — the guidelines cap completeness at 3 for this. It cannot score 4, which requires both what and when with even a weakly explicit 'when'.

3 / 5

Trigger Term Quality

Relevant keywords present — "Unreal Engine", "scenes", "actors", "renders" — but common natural variations users would say are missing: UE5/UE, level, lighting, cinematics, screenshot. This fits 'Some relevant keywords but missing common variations or synonyms'; it falls short of score 4's 'Good keyword coverage with only a few natural terms missing'.

3 / 5

Distinctiveness Conflict Risk

"Unreal Engine editor" is an unambiguous, narrow niche; virtually no other skill would claim these triggers. This matches 'Clear niche with distinct triggers; minimal conflict risk' — score 4's 'minor overlap risk with closely related skills' does not apply since the domain is uniquely named.

5 / 5

Total

14

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

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

Warning

Total

13

/

16

Passed

Repository

NousResearch/hermes-agent

Path

optional-skills/creative/unreal-mcp/SKILL.md

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.