CtrlK
BlogDocsLog inGet started
Tessl Logo

screenshot-scene-view

Capture a screenshot from the Unity Editor Scene View at the requested size. Renders via the Scene View's active camera onto a temporary `RenderTexture`. Requires an open Scene View.

56

Quality

64%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./Unity-MCP-Plugin/.claude/skills/screenshot-scene-view/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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.

The body is a lean, actionable, well-organized single-purpose skill with executable CLI examples and a clear render sequence. Its main weakness is redundant restatement of the width/height inputs across three sections and a self-inconsistent example (0-valued dimensions) that slightly undermines actionability.

Suggestions

Consolidate the width/height specification into one place (e.g. keep the table plus JSON schema, and reference them from the prose Inputs section) to remove triplication.

Fix the example to use valid dimensions (e.g. width: 1920, height: 1080) so it matches the stated '> 0' constraint and is runnable as-is.

Add a brief pre-check note (e.g. confirm a Scene View is focused before invoking) to make the implicit validation explicit and strengthen workflow clarity.

DimensionReasoningScore

Conciseness

Largely efficient prose that assumes Claude's competence, with only mild redundancy: the width/height inputs are restated across the prose 'Inputs', the 'Input' table, and the 'Input JSON Schema' block, which could be trimmed.

4 / 5

Actionability

Provides concrete, copy-paste-ready CLI commands (unity-mcp-cli run-tool ...) covering stdin, file, and inline input patterns, with minor gaps such as the example using width:0/height:0 which violates the stated '> 0' constraint.

4 / 5

Workflow Clarity

The single screenshot action is described as a clear sequence (allocate RenderTexture, swap onto camera, Render, ReadPixels, encode PNG, restore prior targetTexture) with explicit error conditions, though explicit validation checkpoints before/after the render are only implicit.

4 / 5

Progressive Disclosure

Well-organized single-file skill with clear section headers and a one-level reference to the /unity-initial-setup skill; no bundle files exist, and structure is good, though the input is restated across three sections rather than being split cleanly.

4 / 5

Total

16

/

20

Passed

Description

53%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.

The description clearly states what the skill does in third person with concrete technical detail, but omits any explicit 'Use when...' trigger guidance and relies on technical jargon over natural user phrasing. Adding a usage-trigger clause and more natural synonyms would lift the completeness and trigger-term scores.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks for a screenshot of the Unity Scene View or to capture what the Scene View camera sees.'

Include natural-language synonyms users might say (e.g. 'capture', 'snapshot', 'Scene View image') alongside the technical 'RenderTexture' terminology.

Consider mentioning the output format (PNG image) in the description to round out the 'what' and improve specificity.

DimensionReasoningScore

Specificity

Names the domain and 1-2 concrete actions ('Capture a screenshot', 'Renders via the Scene View's active camera onto a temporary RenderTexture') but coverage is narrow to a single screenshotting action rather than multiple specific capabilities.

3 / 5

Completeness

The 'what' is clearly stated (captures a screenshot via the Scene View camera onto a RenderTexture) but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

Contains relevant keywords ('screenshot', 'Unity Editor Scene View') but lacks common synonyms or natural variations a user might say, and includes technical jargon ('RenderTexture') rather than user-friendly phrasing.

3 / 5

Distinctiveness Conflict Risk

Scoped to the Unity Editor Scene View camera specifically, giving it a clear niche distinct from generic screenshot skills, though minor overlap risk remains with sibling Unity screenshot tools (e.g. Game View).

4 / 5

Total

13

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
IvanMurzak/Unity-MCP
Reviewed

Table of Contents

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.