tests-run

Execute Unity tests (`EditMode` or `PlayMode`) and return per-test results. Supports filtering by test assembly, namespace, class, and method. Refreshes the AssetDatabase first; defers execution across domain reloads if scripts changed. Precondition: every open scene must be saved — dirty scenes abort the run.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./Unity-MCP-Plugin/.claude/skills/tests-run/SKILL.md

Quality

Content

77%

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

Actionable and workflow-safe, with real commands and clear validation/retry guidance for a batch test operation. The main weakness is token efficiency: redundant parameter descriptions and large inline schemas that could be offloaded to reference files.

Suggestions

Collapse the prose 'Filters' and 'Response toggles' sections into the Input table to remove duplicated parameter descriptions.

Move the verbose output JSON schema (and optionally the input schema) into a references/ file and link to it, keeping SKILL.md as a lean overview.

Replace the 'string_value' placeholders in the 'How to Call' example with at least one realistic concrete example so it is immediately runnable.

Dimension	Reasoning	Score
Conciseness	Mostly efficient reference docs, but the Filters and Response-toggles prose duplicates the Input table, and the full input/output JSON schemas with verbose .NET type names inflate the body; it could be tightened.	2 / 3
Actionability	Provides concrete, copy-paste-ready CLI invocations ('unity-mcp-cli run-tool tests-run --input ...', '--input-file', stdin pipe) plus a parameter table with examples, matching the 'fully executable' anchor.	3 / 3
Workflow Clarity	Explicit checkpoints and feedback loops are present: dirty-scene precondition with 'save them and retry', and compilation-error short-circuit to 'fix the project first', plus the SessionState resume-after-reload sequence — matching the 'clear sequence with explicit validation steps' anchor.	3 / 3
Progressive Disclosure	No bundle files exist, and the ~275-line body inlines full input/output JSON schemas that read as reference material better suited to a separate file; organization is present but content that should be split is inline, matching the level-2 anchor.	2 / 3
	Total	10 / 12 Passed

Description

82%

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 specific, well-scoped description with strong natural trigger terms and low conflict risk. Its only gap is the absence of an explicit 'Use when...' trigger clause, which limits completeness.

Suggestions

Add an explicit trigger clause such as 'Use when the user asks to run Unity EditMode or PlayMode tests or to check test results.' to satisfy the 'when should Claude use it' half of completeness.

Lead with the user-facing trigger phrasing before the implementation details to maximize trigger-term recall.

Dimension	Reasoning	Score
Specificity	Lists many concrete actions — 'Execute Unity tests', 'return per-test results', 'filtering by test assembly, namespace, class, and method', 'Refreshes the AssetDatabase first', 'defers execution across domain reloads' — matching the 'multiple specific concrete actions' anchor.	3 / 3
Completeness	Clearly states what the skill does, but there is no 'Use when...' clause or equivalent explicit trigger guidance; per the judging guidelines a missing trigger clause caps completeness at 2.	2 / 3
Trigger Term Quality	Contains natural domain terms a Unity developer would say — 'Unity tests', 'EditMode', 'PlayMode', 'test assembly, namespace, class, and method' — giving good coverage of the phrasing users actually use to request test runs.	3 / 3
Distinctiveness Conflict Risk	The Unity-test niche with EditMode/PlayMode and the dirty-scene precondition is highly specific and unlikely to trigger for unrelated skills, matching the 'clear niche with distinct triggers' anchor.	3 / 3
	Total	11 / 12 Passed

Validation

100%

Warnings & errors only

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.

Repository: IvanMurzak/Unity-MCP
Path: Unity-MCP-Plugin/.claude/skills/tests-run/SKILL.md
Commit: e0a24ef

Reviewed: about 10 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.