CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/unreal-automation-system

Author and run Unreal Engine's Automation Test Framework - Epic's C++ test framework for UE 4.x / 5.x, documented at dev.epicgames.com/documentation/en-us/unreal-engine. Covers the five test categories Epic defines (Unit / Feature / Smoke / Content Stress / Screenshot Comparison), the IMPLEMENT_SIMPLE_AUTOMATION_TEST and IMPLEMENT_COMPLEX_AUTOMATION_TEST macros, the BDD-style Automation Spec API (DEFINE_SPEC / BEGIN_DEFINE_SPEC / Describe / It / BeforeEach / LatentIt / xIt), latent commands (ADD_LATENT_AUTOMATION_COMMAND), the Automation Driver for UI input simulation (IAutomationDriverModule::Get().CreateDriver(), By::Id / By::Path locators), running via Session Frontend (Window > Test Automation) and command line (-ExecCmds="Automation RunTests …"), and CI integration. Use when the unit under test is C++ Unreal code that needs the UE runtime, editor, or UMG UI surface.

74

Quality

93%

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

Overview
Quality
Evals
Security
Files

Quality

Content

85%

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

A well-architected skill body: a lean decision surface with concrete commands, sequenced workflows with a CI validation gate, and clean one-level progressive disclosure into two real reference files. The only weakness is repeated inline documentation URLs that inflate the token budget.

Suggestions

Define the three Epic doc URLs once (e.g. in a short 'Sources' note) and cite them by short label in the anti-patterns and limitations tables instead of pasting the full URL on every row.

In the 'Running' section, factor the shared -ExecCmds / -unattended / -nopause flags into a single canonical block so the worked example can reference rather than re-paste the full command line.

Consider trimming the eight-row anti-patterns table to the highest-value rows, or moving the doc-citation-heavy rows into the relevant reference file, to reduce inline repetition.

DimensionReasoningScore

Conciseness

Mostly efficient and free of concept-explanation fluff, but the same full dev.epicgames.com URL is repeated inline ~10 times across the anti-patterns and limitations tables where a single defined link would do — 'could be tightened' per the level-2 anchor, not 'every token earns its place'.

2 / 3

Actionability

Provides fully executable guidance: a copy-paste UnrealEditor-Cmd.exe invocation, concrete EAutomationTestFlags enums, By::Id locators, the 'state': 'Fail' report key, and a step-by-step worked example — copy-paste ready.

3 / 3

Workflow Clarity

The 'How to use' six-step sequence and the five-step worked example are explicitly ordered, and the CI 'Gate' step with 'treat any state: Fail as a failed build' supplies the validation checkpoint / feedback loop the rubric rewards.

3 / 3

Progressive Disclosure

SKILL.md is explicitly the 'decision surface' with two real, one-level-deep references (authoring-macros-and-apis.md, running-and-reporting.md, both present in ./references/), each clearly signaled and consulted at a defined point in the workflow.

3 / 3

Total

11

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that pairs a dense enumeration of concrete capabilities with an explicit 'Use when' trigger and a distinct niche. Voice is correctly third person with no first/second-person slip.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — authoring via IMPLEMENT_SIMPLE/COMPLEX macros, BDD Spec API, latent commands, the Automation Driver, plus running via Session Frontend, command line, and CI integration — matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicitly answers both what ('Author and run ... Covers the five test categories ... macros ... Spec ... Driver ... CI integration') and when ('Use when the unit under test is C++ Unreal code that needs the UE runtime, editor, or UMG UI surface'), with an explicit 'Use when' trigger clause.

3 / 3

Trigger Term Quality

Natural terms a user would say are present ('Unreal Engine', 'Automation Test Framework', 'C++ Unreal code', 'UE runtime', 'editor', 'UMG UI'), giving good coverage; the embedded macro/API names are jargon-heavy but do not crowd out the natural trigger phrases.

3 / 3

Distinctiveness Conflict Risk

A clear, narrow niche — Epic's C++ Unreal Automation Test Framework scoped to UE 4.x/5.x — with trigger language unlikely to fire for any other skill.

3 / 3

Total

12

/

12

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Reviewed

Table of Contents