CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/unity-test-framework

Author and run the Unity game-engine Test Framework (`com.unity.test-framework`, currently v1.8). Distinct from the ThrowTheSwitch Unity C testing library at throwtheswitch.org/unity - the two tools share only a name. Covers package install via Package Manager, the EditMode vs PlayMode split, the [Test] / [UnityTest] / [SetUp] / [TearDown] / [UnityPlatform] attributes, assembly-definition setup (Editor folder vs asmdef with `includePlatforms` / `optionalUnityReferences: [TestAssemblies]`), Test Runner window, command-line batch invocation with `-runTests` / `-testPlatform` / `-testResults` / `-testFilter` / `-testCategory`, NUnit 3.5 assertion API, and CI integration. Use when the unit under test is C# Unity code that needs to exercise the Unity runtime or editor.

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

High

Do not use without reviewing

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 well-structured, highly actionable body that splits detail into real one-level-deep references and provides executable code and CLI examples. Its main weakness is mild verbosity from verbatim documentation quotes that could be tightened without losing clarity.

Suggestions

Tighten verbatim doc quotes (e.g. the EditMode 'are only run in the Unity Editor...' and PlayMode 'execute as coroutines...' passages) to paraphrases so every token earns its place.

Add an explicit validate→fix→re-run loop in the 'Parsing results' / CI section (on `result="Failed"`, fix the failing test and re-invoke `-runTests`) to lift workflow_clarity to 5.

Reduce repeated inline doc-source attributions ('per the edit-mode-vs-play-mode docs') by consolidating sourcing into the reference files.

DimensionReasoningScore

Conciseness

The body is dense and actionable without explaining basics Claude already knows, but includes several verbatim doc quotes ('are only run in the Unity Editor and have access to the Editor code in addition to the game code') that could be trimmed; efficient with minor over-explanation. Not a 5 because those quoted passages and repeated doc-source attributions add tokens that do not all earn their place.

4 / 5

Actionability

Provides copy-paste-ready executable EditMode and PlayMode C# examples, a concrete asmdef JSON block, and a fully specified Unity batch-mode CLI invocation covering the common run case.

5 / 5

Workflow Clarity

The run/CI sequence is clear (invoke batch mode → treat `-testResults` XML as source of truth → surface `result="Failed"` → enumerate failed `<test-case>`), and verification is present so the batch-operation cap at 3 does not apply. Not a 5 because there is no explicit fix-and-re-run feedback loop for failing tests.

4 / 5

Progressive Disclosure

SKILL.md is a clear overview with well-signaled, one-level-deep markdown links to real bundle files (references/attributes.md, references/cli.md, references/results-and-ci.md — all present), with the bulk cheatsheet, flag table, and CI workflow appropriately split into those references.

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.

A strong, specific description that covers capabilities comprehensively, gives an explicit 'Use when' trigger, and explicitly disambiguates from a same-named C library. Third-person voice is used throughout, so no voice penalty applies.

DimensionReasoningScore

Specificity

Lists multiple concrete actions spanning install ('package install via Package Manager'), the EditMode vs PlayMode split, specific attributes, asmdef setup, Test Runner, CLI batch flags, NUnit 3.5 assertions, and CI integration — comprehensive coverage rather than minimal.

5 / 5

Completeness

Explicitly answers both 'what' ('Author and run the Unity game-engine Test Framework ... Covers ...') and 'when' ('Use when the unit under test is C# Unity code that needs to exercise the Unity runtime or editor') with concrete trigger phrasing.

5 / 5

Trigger Term Quality

Includes natural trigger phrases a user would say ('C# Unity code that needs to exercise the Unity runtime or editor') plus synonyms and identifiers (unity, test-framework, edit-mode, play-mode, nunit, csharp) via keywords; comprehensive natural-term coverage.

5 / 5

Distinctiveness Conflict Risk

Carves a clear niche and actively disambiguates ('Distinct from the ThrowTheSwitch Unity C testing library at throwtheswitch.org/unity - the two tools share only a name'), minimizing wrong-skill triggering.

5 / 5

Total

20

/

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Reviewed

Table of Contents