CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

testland/unity-test-framework

Use for any question or task about testing C# code in a Unity game-engine project, even a single PlayMode test for a MonoBehaviour: Unity Test Framework EditMode vs PlayMode tests, [Test] and [UnityTest], assembly definitions, the Test Runner window, batch-mode command-line runs and CI. Not the ThrowTheSwitch C library.

Quality

94%

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

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

A strong, well-structured body: concrete executable examples for both test modes and CLI runs, a genuinely useful anti-patterns table, and clean one-level progressive disclosure to real reference files. The only weaknesses are minor — a duplicated Test-vs-UnityTest recommendation, a short NUnit assertion primer, and no explicit failure-recovery loop in the CI workflow.

Suggestions

State the "prefer [Test] over [UnityTest] unless you need to yield" guidance once (it currently appears in both the EditMode section and the NUnit assertion APIs section) and trim the basic NUnit assertion enumeration to just the UTF-specific recommendation.

Add a brief failure-recovery step to the CI integration section (e.g., on result="Failed", read the failed <test-case> stack traces from the -testResults XML and re-run with -testFilter on the failing fixtures) to close the workflow feedback loop.

Fill in the EditMode example's [TearDown] with the actual Object.DestroyImmediate(go) cleanup call instead of only a comment, since the body of the copy-paste example is currently empty.

DimensionReasoningScore

Conciseness

The body is dense with UTF-specific facts (pinned doc quotes, asmdef JSON, CLI flags, anti-patterns), but the "prefer [Test] over [UnityTest] unless you need to yield" advice appears twice (EditMode section and NUnit APIs section), and enumerating basic NUnit assertions like "Assert.AreEqual, Assert.Throws<T>(() => ...)" re-explains what Claude already knows. This fits the efficient-with-minor-trimmings anchor, not the every-token-earns-its-place anchor.

4 / 5

Actionability

Two complete runnable test classes, a full PlayMode asmdef JSON block, a complete batch-mode CLI invocation with flags, and concrete fixes in the anti-patterns table ("[TearDown] Object.DestroyImmediate(go) on every fixture", "actions/cache@v4 with the Library/ path") make the guidance copy-paste ready and cover the common authoring/running cases, matching the 5 anchor.

5 / 5

Workflow Clarity

The pipeline (When to use → Authoring → Running → Parsing results → CI) is clearly sequenced, and there is an explicit verification directive ("treat the -testResults XML as the source of truth", "Parse -testResults XML in CI") so the batch-operation cap does not bind. However, there is no failure-recovery feedback loop (e.g., what to do when a CI run reports failures beyond reading stack traces), which keeps it at the most-checkpoints-present anchor rather than 5.

4 / 5

Progressive Disclosure

The three referenced files (references/attributes.md, references/cli.md, references/results-and-ci.md) all exist, are substantive, and are one level deep; each is linked at a natural point with a description of what it contains ("The full batch-mode flag table ... are in references/cli.md"), and the bulk detail (attribute cheatsheet, flag table, XML schema, full CI workflow) is appropriately split out. This matches the clear-overview anchor.

5 / 5

Total

18

/

20

Passed

Description

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

An exemplary description: it states what the skill covers concretely, gives an explicit and naturally-phrased when-to-use trigger, and proactively disambiguates from the identically-named C testing library. No vague or padded language is present.

DimensionReasoningScore

Specificity

The description lists multiple concrete capabilities spanning the full workflow — "EditMode vs PlayMode tests, [Test] and [UnityTest], assembly definitions, the Test Runner window, batch-mode command-line runs and CI" — which matches the comprehensive-coverage anchor rather than the minor-gaps anchor one level below.

5 / 5

Completeness

Both halves are explicit: the capability list answers "what", and "Use for any question or task about testing C# code in a Unity game-engine project, even a single PlayMode test for a MonoBehaviour" is a concrete when-clause with trigger phrases, matching the 5 anchor exactly; the missing-when cap at 3 clearly does not apply.

5 / 5

Trigger Term Quality

It captures natural phrases users actually say — "testing C# code in a Unity game-engine project", "a single PlayMode test for a MonoBehaviour", "Test Runner window", "CI" — plus verbatim attribute names. Coverage of natural terms including synonyms matches the 5 anchor; no commonly-said trigger term for this domain is missing, so it is not the 4 anchor.

5 / 5

Distinctiveness Conflict Risk

Scoping to "a Unity game-engine project" plus the explicit exclusion "Not the ThrowTheSwitch C library" preempts the one real name collision, giving a clear niche with minimal conflict risk as in the 5 anchor.

5 / 5

Total

20

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

On this page