Run Tests Agent Skill

Provides guidelines for running Unity tests using the run_unity_tests tool.

Context cost
14.2k tokensestimated from the bundle, loaded when it triggers
Bundle
10 files · 68.0 kB5 scripts among them — read before you run
Licence
Unlicensethe author’s own terms
Last change
—no release on file
Servers it uses
Noneruns standalone

What it does

Provides guidelines for running Unity tests using the run_unity_tests tool. Make sure to use this skill whenever running, executing, or re-running tests on the Unity editor. This includes verifying implementations, debugging test failures, running specific test assemblies, or any task that involves the run_unity_tests tool. Also covers running Play Mode tests on the player for verifying player-only behavior (e.g., #if directives and code stripping). Also covers verifying `[Category("VisualVerification")]` tests after a run by analyzing the saved screenshots.

What this skill changes about the agent has not been set out here as a list. Its SKILL.md, shown below, says it in the author’s own words.

gamedev

The skill itself

A skill is instructions the model reads, so you can see what you are getting: below is the start of its SKILL.md. The front matter loads with every session, the body loads when the skill triggers, and the whole file comes with the install.

SKILL.md8.7 kB · preview
--- name: run-tests license: Unlicense metadata: author: Koji Hasegawa ---
15## Gotchas
16
17- **Never call two Unity Editor tools in parallel.** unity_play_control, get_unity_compilation_result, run_unity_tests, and run_method_in_unity must be called strictly one at a time — always wait for each call to return before making the next one. Calling them concurrently causes domain-reload conflicts that result in "canceled" or "did not connect within 30 seconds" errors.
18- **When a Unity Editor tool returns error or canceled, wait 10 seconds before retrying.** Domain reload typically takes several seconds; immediate retry hits the same in-flight reload and fails again. Do not switch tools in the meantime (e.g., calling unity_play_control to verify state) — that just compounds the multiplexed calls. If the same tool returns error or canceled on two consecutive attempts (with the 10-second wait between them), stop and consult the user instead of retrying further.
19
20## Run Tests
21
22Before running tests, complete the following steps in order:
23
241. If any code was modified, confirm compilation success using the get_unity_compilation_result tool before proceeding.
252. To determine assemblyNames and testMode for a specific test class, run ${CLAUDE_SKILL_DIR}/scripts/resolve-test-target.sh <test-class-cs-path>. The script prints <assemblyName>\t<testMode> (e.g. MyGame.Tests\tPlayMode). Skip this step when running an already-known assembly.
26
27Then use the run_unity_tests tool to run the tests on the Unity editor.
28
29Test execution can take several minutes. Do not re-run while a test is in progress — always wait for it to complete or time out. If a timeout occurs, narrow down the tests using filter settings and re-run.
30
31### Performance Test Results
32
33When com.unity.test-framework.performance is installed, each run writes its measurements to Application.persistentDataPath/PerformanceTestResults.json (alongside the TestResults.xml they are parsed from). Resolve that directory with ${CLAUDE_SKILL_DIR}/scripts/get-persistent-data-path.sh <unity-project-root>.
This is a preview of SKILL.md. Download or install the skill to get the whole thing.
In the file
SKILL.md1,145 words
Files10
LicenceUnlicense
Why you can read it

Nothing in a skill executes. The client loads the text and the model follows it, so a skill can be audited the way a runbook is — by reading it.

What it costs in context

Skills are not billed by the call. They are paid for in context: every token the instructions occupy is a token your code, your diff and your conversation cannot use. Here is what this one takes and when it takes it.

≈190
always loaded
The name and description, so the model knows the skill exists and when to reach for it.
13,985
on trigger
The instruction body and 9 supporting files, read only when the skill fires.
7.1%
of a 200k window
Ten skills this size would take about 71% of the window before you open a file.
050k100k150k200k context window

14.2k tokens, estimated from the bundle at four bytes to the token, held for the rest of the session once it triggers. Heavy. Teams tend to install this one per project rather than globally, and load it only when the job comes up.

Servers bill, skills cost

A server charges by the month. A skill charges once per session, in context, and then keeps charging it for as long as the session lives.

Before and after

The same question, put to the same model twice: once as it comes, and once with these instructions loaded.

No worked example has been published for this skill yet.

The procedure it runs

The procedure has not been set out here step by step. It is in the body of its SKILL.md: the start of it is shown above, and the whole file comes with the install.

Prose, not code

These steps are written for a model to follow, not executed by a runtime. It can still be told to skip one, and it will say so when it does.

Servers it uses

None. This skill calls no MCP servers at all.

Everything it needs is in the instructions, so it works in a project with nothing connected — the model reads the file and changes how it works with what it can already reach.

Its SKILL.md does not declare which tools it asks the agent for, so what it touches is whatever the instructions themselves ask for — read them before you install it.

What it asks for
Writes filesnot declared
Network accessnot declared

This SKILL.md carries no allowed-tools line, so neither is declared. A skill grants no permissions of its own — it can only ask for tools your client already has.

What it will not do

Every skill is narrow, and the useful ones say where they stop. These are the jobs this one is the wrong tool for.

What this skill is not for has not been published here. Nothing is implied by that: it is a section the author has not filled in.

What is in the bundle

10 files, 68.0 kB on disk. Mostly text — the instructions the model reads — with 5 scripts in it that your client would run only if the instructions tell it to. 1 file of its source is not in the download — listed after these, with why.

  • SKILL.md8.7 kB
  • resources/run-on-standalone-player.md22.4 kB
  • resources/troubleshooting-run-unity-tests.md13.7 kB
  • resources/troubleshooting-test-helper.md2.8 kB
  • resources/troubleshooting-test-helper-ui.md9.1 kB
  • scripts/extract-visual-verification.py6.7 kB
  • scripts/get-persistent-data-path.sh1.3 kB
  • scripts/get-player-settings.sh0.9 kB
  • scripts/resolve-assembly.sh1.0 kB
  • scripts/resolve-test-target.sh1.4 kB

Not in the download

Not carried is a type a skill download does not hold. Take it from its source.

  • assets/PlayerTestRunner.csnot carried
What is not in it

A skill installs nothing and depends on nothing: it is a folder your client reads. This one carries 5 scripts beside the text, so the download is 10 files — not the whole of its source: 1 file is left out. It is listed under the files, with why. The Unlicense licence covers the templates and examples as well as the instructions.

Install

Installing copies the bundle into your project. Nothing runs at install time — the files sit on disk until the model reads them.

# Run Tests · 14.2k tokens when loaded · macOS, Linux mkdir -p .claude/skills && t=$(mktemp -d) && curl -fsSL -o "$t/bundle.tar.gz" https://mcprush.com/api/skills/run-tests/bundle.tar.gz && tar -xzf "$t/bundle.tar.gz" -C "$t" && [ -d "$t/run-tests" ] && { [ ! -e .claude/skills/run-tests ] || { mv .claude/skills/run-tests "$t/.previous" && echo "Previous copy moved to $t/.previous"; }; } && mv "$t/run-tests" .claude/skills/ && echo "Installed .claude/skills/run-tests"
On Windows, or any OS with Node 20+
npx mcprush@latest skill add nowsprinting/run-tests

Windows PowerShell says 'running scripts is disabled on this system'? Run Set-ExecutionPolicy -Scope CurrentUser RemoteSigned once, or type npx.cmd instead of npx (codex.cmd, gemini.cmd, grok.cmd likewise). PowerShell 7 needs neither. Writes to .claude/skills/run-tests/ in the current project. For every project instead, run mkdir -p ~/.claude/skills && t=$(mktemp -d) && curl -fsSL -o "$t/bundle.tar.gz" https://mcprush.com/api/skills/run-tests/bundle.tar.gz && tar -xzf "$t/bundle.tar.gz" -C "$t" && [ -d "$t/run-tests" ] && { [ ! -e ~/.claude/skills/run-tests ] || { mv ~/.claude/skills/run-tests "$t/.previous" && echo "Previous copy moved to $t/.previous"; }; } && mv "$t/run-tests" ~/.claude/skills/ && echo "Installed ~/.claude/skills/run-tests" (macOS, Linux) — or add --global to the npx line. The curl line replaces .claude/skills/run-tests/ only after the download succeeds, so files left there by another skill of the same name, or by an older release, do not mix in. A copy already there is moved aside, not deleted, and the line prints where. Not in this download: 1 file of its source (which one, and why). Take it from its source.

Which clients pick it up on their own

A skill is a folder of text. Most of these read a skills folder and pick it up without being told; the rest take the same folder another way — an upload in the app, a parameter on an API call — and then choose it by its description just the same.

Claude Code.claude/skills/
Claude DesktopCustomize › Skills
ChatGPTSkills › Create › Upload
Cursor.cursor/skills/
VS Code.github/skills/
Codex CLI.agents/skills/
Gemini CLI.gemini/skills/
Grok Build.grok/skills/
Microsoft CopilotSkills › Upload a skill
PerplexityComputer › Skills › Upload a skill
DeepSeek Harness.dsh/skills/
Zed.agents/skills/
Devin Desktop.devin/skills/
Windsurf (legacy).windsurf/skills/
OpenAI Agents SDKInstructions or sandbox Skills
HTTP / APIa request parameter
This release
Versionnot versioned
Publishedno release date on file
PriceFree
Referencenowsprinting/run-tests

Versions

Its author publishes no version number, so there is nothing here to pin to: what you install is the folder as it stands today. Instructions change more often than APIs do — a skill can be rewritten entirely without anything it depends on moving.

Pinning

Nothing to pin to: this skill carries no version number of its own. What you install is what the folder holds on the day you install it.

Reviews

—no reviews yet

Nobody has reviewed this skill yet. The rating is the mean of the reviews written here, so there is none until somebody writes the first.

Sign in to review it

A review is tied to an account so it can be answered, edited and taken down by the person who wrote it.

Sign in
Who can post

Anybody with an account, one review each. It carries the version that was current when you wrote it, and the publisher may reply once.

Publisher
Servers0
Claim this skill