profiler-get-status

Return the Unity profiler's current enabled state, active modules, max-used memory, and platform support flag. Read-only.

Quality

76%

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/profiler-get-status/SKILL.md

Quality

Content

85%

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

The body is a well-organized, actionable tool reference with executable commands and complete schemas; the only slack is mild verbosity in the invocation examples and a confusing placeholder input.

Dimension	Reasoning	Score
Conciseness	The body avoids explaining concepts Claude already knows and is mostly reference data, but three invocation variants (--input, --input-file, stdin) plus a placeholder input example ("nothing": "string_value") add slack that could be tightened.	2 / 3
Actionability	It provides copy-paste-ready executable commands ("unity-mcp-cli run-tool profiler-get-status --input ...") alongside complete input and output JSON schemas, matching the fully-executable anchor.	3 / 3
Workflow Clarity	This is a single-purpose, read-only tool with one unambiguous action and no destructive or batch operation requiring validation; per the simple-skills note that warrants a 3.	3 / 3
Progressive Disclosure	Content is organized into clearly labeled sections (Fields, Behavior, How to Call, Input, Output) with no nested or multi-level references, and no bundle files are needed for this single-file reference.	3 / 3
	Total	11 / 12 Passed

Description

67%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific and clearly scoped to the Unity profiler, but it omits any "when to use" trigger guidance and leans on technical terms rather than natural user phrasing.

Suggestions

Add a 'Use when...' clause, e.g. 'Use when the user asks about Unity profiler status, memory usage, or whether profiling is enabled/supported.'

Include natural trigger terms users would actually say, such as 'profiler status', 'is the profiler enabled', and 'profiler memory'.

Dimension	Reasoning	Score
Specificity	Quotes "current enabled state, active modules, max-used memory, and platform support flag" — four concrete returned capabilities, third-person voice ("Return"), matching the multiple-specific-actions anchor.	3 / 3
Completeness	"Return the Unity profiler's current enabled state..." clearly answers what, but there is no "Use when..." clause or equivalent trigger guidance; per the rubric a missing trigger clause caps completeness at 2.	2 / 3
Trigger Term Quality	Terms like "Unity profiler" and "max-used memory" are relevant but technical; it lacks common natural variations a user would say (e.g. "profiler status", "is profiling enabled", "profiler memory"), so it lands at the some-keywords-but-missing-variations anchor.	2 / 3
Distinctiveness Conflict Risk	Scoped specifically to Unity Profiler status fields, it occupies a clear niche and is unlikely to trigger for unrelated skills.	3 / 3
	Total	10 / 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/profiler-get-status/SKILL.md
Commit: e0a24ef

Reviewed: about 11 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.