profiler-get-rendering-stats

Return current frame timing, FPS, vsync, target frame rate, threading mode, and graphics device type from Unity Time / QualitySettings / SystemInfo.

Quality

79%

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-rendering-stats/SKILL.md

Quality

Content

73%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, executable single-tool reference whose main weakness is redundancy: the field documentation appears twice and input-workaround guidance outweighs the tool's trivial input. Deduplicating the schemas and showing a realistic example output would make it lean and fully copy-paste ready.

Suggestions

Deduplicate the Fields section against the Output JSON Schema — keep the field list with its formulas and trim the schema's per-property descriptions to names/types only.

Replace the unexplained placeholder input ("nothing": "string_value") with a realistic call or note that the tool takes no meaningful input.

Add a short example output JSON so the expected result shape is visible without parsing the full schema.

Dimension	Reasoning	Score
Conciseness	The Fields list and the Output JSON Schema describe the same seven values twice with near-identical descriptions, and the "How to Call" section elaborates stdin/file-input workarounds for a tool whose only input is a placeholder, so the body could be meaningfully tightened.	3 / 5
Actionability	The CLI command is copy-paste ready and field formulas (e.g. "Time.deltaTime * 1000f") plus CLI-not-found troubleshooting are concrete, but the example input "nothing": "string_value" is an unexplained dummy and no sample output is shown.	4 / 5
Workflow Clarity	This is a simple single-purpose skill where the single action (run one CLI command) is unambiguous, and the failure path ("If unity-mcp-cli is not found") is explicitly handled, satisfying the simple-skill exception.	5 / 5
Progressive Disclosure	Sections are well organized and clearly labeled (Fields / How to Call / Troubleshooting / Input / Output), but the body exceeds 50 lines with a large inline output schema that largely duplicates the Fields list, leaving minor organization gaps.	4 / 5
	Total	16 / 20 Passed

Description

75%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 highly specific, distinctive description with excellent concrete field enumeration, weakened only by the complete absence of "when to use" trigger guidance. Adding a "Use when..." clause with natural trigger phrases would lift it to the top band.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks about Unity frame rate, FPS, rendering performance, or graphics device info."

Include natural synonyms such as "rendering stats", "profiler", or "performance" so the description matches how users actually phrase the request.

Keep the field enumeration as-is; it is the description's strongest asset.

Dimension	Reasoning	Score
Specificity	The description enumerates six concrete returned values ("frame timing, FPS, vsync, target frame rate, threading mode, and graphics device type") and names the source Unity APIs (Time / QualitySettings / SystemInfo), which is comprehensive, specific coverage for its single-purpose domain.	5 / 5
Completeness	The "what" is clear and concrete, but there is no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines.	3 / 5
Trigger Term Quality	Natural user phrases like "FPS", "vsync", and "target frame rate" are present, but common variations such as "rendering stats", "profiler", or "Unity performance" are missing, so coverage is good rather than comprehensive.	4 / 5
Distinctiveness Conflict Risk	The description is tightly scoped to Unity rendering statistics from named engine APIs, giving it a clear niche with minimal overlap risk against other skills.	5 / 5
	Total	17 / 20 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-rendering-stats/SKILL.md
Commit: 4c8056f

Reviewed: 8 days 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.