Skip to content
Agentmart
Submit a tool

unity-testrunner

Run and interpret Unity Test Framework checks for Unified Unity MCP.

Skill by AndreySkyFoxSidorov

IndexedMIT★ 27
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/andreyskyfoxsidorov-unity-testrunner

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Run and interpret Unity Test Framework checks for Unified Unity MCP. Use when validating C# changes, MCP tools, editor behavior, or CI test output.

Use cases: testing, devops, agent-building

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/unity-testrunner

What's inside

Skill name
unity-testrunner
Description
Run and interpret Unity Test Framework checks for Unified Unity MCP. Use when validating C# changes, MCP tools, editor behavior, or CI test output.
License
MIT
Instructions
41 lines in SKILL.md · view on GitHub

Files (4)

  • SKILL.md
  • cli-automation.md · references/
  • result-parsing.md · references/
  • test-patterns.md · references/

SKILL.md (first lines)

# Unity Test Runner

## Use This Skill When

- Running EditMode or PlayMode tests.
- Adding tests for MCP tools, protocol behavior, or editor utilities.
- Interpreting Unity test XML, logs, or CI failures.

## Rules

- Use the narrowest test scope that proves the change.
- Prefer EditMode tests for editor tools, protocol, catalogs, and pure C# behavior.
- Use PlayMode only when runtime scene behavior requires it.
- Do not require TDD by default.
- Do not add mocking frameworks or DI containers unless already present and required.
- Do not use `switch`.

## MCP Validation

For tool contract changes, verify:

- `initialize`
- `tools/list`
- target `tools/call`
- console error output
- updated catalog entries

## Result Summary

Report:

- command or tool used
- pass/fail count when available
- failing test names and first useful error
- any blocker that prevented tests from running

## References

Reference files contain CLI and parsing examples. Update stale shell snippets before copying them.

From AndreySkyFoxSidorov/UnifiedUnityMCP, MIT.

More from AndreySkyFoxSidorov/UnifiedUnityMCP

Signals

Stars
27
Forks
5
Open issues
0
Last commit (this folder)
May 20, 2026 (5 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from AndreySkyFoxSidorov

Cite this page

unity-testrunner skill. Agent Mart. https://agentmart.dev/skills/andreyskyfoxsidorov-unity-testrunner (last updated 2026-10-24)