screenshot-game-view

Capture a screenshot of the Unity Editor's Game View by reading its internal render texture directly. Image size matches the current Game View resolution; the tool corrects Y-flip on DirectX / Metal so the output is always upright. Requires an open Game View window.

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/screenshot-game-view/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-structured, actionable, single-purpose skill with executable CLI examples and a clear internal workflow. Its only real weakness is mild redundancy in the intro and a placeholder "nothing" input parameter that adds noise without value.

Suggestions

Trim the opening paragraph since it duplicates the frontmatter description, or replace it with information not already stated.

Clarify or drop the "nothing" input parameter — if the tool takes no real input, state that explicitly instead of presenting a dummy string field with an empty description.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean with focused sections, but the opening paragraph restates the description and the Input table centers on a meaningless "nothing" parameter with an empty description, adding noise that could be trimmed.	2 / 3
Actionability	Concrete, copy-paste-ready CLI commands are provided (unity-mcp-cli run-tool screenshot-game-view --input ...) plus executable troubleshooting fixes (npm install -g unity-mcp-cli / npx), giving clear runnable guidance.	3 / 3
Workflow Clarity	The single-task workflow is described as an unambiguous sequence (locate GameView, repaint, reflect m_RenderTexture, ReadPixels, Y-flip on top-left UV APIs, encode PNG); as a simple non-destructive skill it needs no validation checkpoint.	3 / 3
Progressive Disclosure	For a short, single-purpose skill with no bundle files, the content is well organized into Behavior, How to Call, Troubleshooting, Input, and Output sections, with a clearly signaled pointer to the /unity-initial-setup skill for setup.	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 niched to Unity Game View screenshots, with concrete technical actions. Its main weakness is the missing explicit "Use when..." trigger guidance and limited keyword variation, which cap completeness and trigger-term quality.

Suggestions

Add an explicit "Use when..." clause, e.g. "Use when the user asks for a screenshot of the Unity Game View or to capture what the game currently looks like."

Broaden natural trigger terms to include common variations like "capture", "grab", or "game window" alongside "screenshot" and "Game View".

Dimension	Reasoning	Score
Specificity	Multiple concrete actions are named explicitly — "Capture a screenshot... by reading its internal render texture directly", "corrects Y-flip on DirectX / Metal", and "Image size matches the current Game View resolution" — rather than vague abstraction.	3 / 3
Completeness	The "what" is clear (capture a Game View screenshot), but there is no "Use when..." trigger clause; "Requires an open Game View window" states a precondition rather than explicit usage guidance, capping completeness at 2 per the rubric guideline.	2 / 3
Trigger Term Quality	Natural terms like "screenshot", "Game View", and "Unity Editor" appear, but common user variations such as "capture", "grab", or "game window" are not covered, leaving the keyword set somewhat narrow for a 3.	2 / 3
Distinctiveness Conflict Risk	It targets a very specific niche — the Unity Editor Game View render texture — with triggers unlikely to overlap with other skills, so conflict risk is low.	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/screenshot-game-view/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.