CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

78%

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

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 tight, actionable, well-structured body for a simple tool — the invocation is unambiguous and errors are documented. The main flaws are triplicated input documentation and an example that uses values (0x0) the skill itself declares invalid.

Suggestions

Consolidate the three overlapping input listings ('## Inputs' bullets, the '## Input' table, and the JSON Schema) into a single section to remove redundancy.

Fix the example call to use valid dimensions (e.g., "width": 1920, "height": 1080) so it does not contradict the stated 'must be > 0' constraint.

DimensionReasoningScore

Conciseness

The prose is mostly efficient and assumes Claude's competence, but the same two parameters are documented three times ('## Inputs' bullets, the '## Input' table, and the Input JSON Schema), which is unnecessary padding that could be tightened to one listing. It is not a 2 because nothing explains concepts Claude already knows.

3 / 5

Actionability

Concrete, copy-paste-ready CLI commands are provided with --input, --input-file, and stdin variants plus troubleshooting, but the example passes "width": 0 and "height": 0, violating the body's own 'must be > 0' constraint — a minor gap that keeps it below fully executable top-band examples.

4 / 5

Workflow Clarity

This is a simple, single-purpose, non-destructive skill and the single action (invoke the CLI tool, receive the image) is unambiguous, with error conditions explicitly stated ('Throws/errors when no Scene View is open or the Scene View camera is null'). Per the simple-skill guideline, this qualifies for the top score.

5 / 5

Progressive Disclosure

The body is self-contained and well sectioned, with a clearly signaled one-level reference to the /unity-initial-setup skill and no bundle files needed. It falls short of 5 due to a minor organization gap: the duplicated '## Inputs' and '## Input' sections describing the same parameters.

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 specific, distinctive description that clearly states what the tool does and how, but it lacks any 'Use when...' trigger guidance and misses a few natural keyword variations. Adding an explicit usage-trigger clause would raise completeness to the top band.

Suggestions

Add a trigger clause such as 'Use when the user asks for a screenshot of the Unity Scene View, or wants to visually inspect the current Unity scene.'

Include a couple of natural synonyms/variations (e.g., 'Unity', 'PNG', 'snap the scene') to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

The description states the concrete action ('Capture a screenshot from the Unity Editor Scene View at the requested size'), the rendering mechanism ('Renders via the Scene View's active camera onto a temporary RenderTexture'), and the precondition, comprehensively covering this single-purpose tool with no gaps.

5 / 5

Completeness

The 'what' is clearly answered (capture a Scene View screenshot at a requested size), but there is no 'Use when...' or equivalent trigger clause; 'Requires an open Scene View' is a precondition, not usage guidance, so the rubric cap applies.

3 / 5

Trigger Term Quality

Natural terms users would say are present ('screenshot', 'capture', 'Unity Editor', 'Scene View'), but a few natural variations are missing (e.g., 'Unity', 'PNG', contrast with 'Game View'), falling just short of the comprehensive synonym coverage of the top anchor.

4 / 5

Distinctiveness Conflict Risk

It carves out a clear niche — Unity Editor Scene View screenshots — explicitly distinct from sibling concerns like Game View, so the risk of triggering for the wrong skill is minimal.

5 / 5

Total

17

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

IvanMurzak/Unity-MCP

Path

Unity-MCP-Plugin/.claude/skills/screenshot-scene-view/SKILL.md

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.