screenshot-isolated

Render a target GameObject from a chosen camera angle with optional layer-based isolation, configurable background (solid/skybox/transparent), multi-light setup via JSON, and Composite (2x2 Front/Right/Back/Top) mode. Returns a PNG image. When isolated=true, inactive children may briefly fire OnEnable — see the body for side-effect notes.

Quality

71%

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

Quality

Content

56%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 well-organized and domain-specific with a clear single-action workflow and thoughtful troubleshooting, but it is padded: the full JSON schema duplicates the input table, a caveat is repeated three times, and the main invocation example uses placeholder values instead of an executable worked example.

Suggestions

Replace the "string_value" placeholders with one fully-filled, copy-paste-ready example (e.g. a real gameObjectRef, isolated, backgroundMode, cameraView, and lights values) so the How to Call section is executable.

Move the full Input JSON Schema into a references/ file (e.g. references/schema.json) and keep only the Input table plus a one-line pointer, removing the duplication.

State the OnEnable side-effect caveat once (in the Side-effect caveat section) and drop its repetition from the opening paragraph to save tokens.

Dimension	Reasoning	Score
Conciseness	Sections like Camera views, Background modes, and Lights are tight and useful, but the ~110-line inline JSON schema largely duplicates the Input table, and the OnEnable side-effect caveat is stated three times (description, opening paragraph, dedicated section). Mostly efficient with clear redundancy that could be trimmed — matches anchor 3, not 4 where only minor trimming would be needed.	3 / 5
Actionability	The CLI invocation and the lights JSON example are concrete, but the primary call example fills every parameter with the placeholder "string_value" (including booleans and numbers), making it a template rather than executable code, and no filled real-world example is given. Some concrete guidance but incomplete/pseudocode-like, matching anchor 3 rather than 4's "concrete code with minor gaps".	3 / 5
Workflow Clarity	This is a single-action tool skill and the workflow (run unity-mcp-cli with the input, or --input-file/stdin for complex payloads) is unambiguous in structure, with a troubleshooting path for CLI-not-found. Minor gaps (placeholder values instead of a worked example, no step to verify the returned image) keep it at anchor 4 rather than 5.	4 / 5
Progressive Disclosure	No bundle files exist and the document has a sensible header structure, but the full JSON Schema (~110 lines) is reference material inlined into SKILL.md that belongs in a separate reference file, duplicating the Input table. Structure present with content that should be separate inlined — anchor 3 rather than 4's "most content appropriately placed".	3 / 5
	Total	13 / 20 Passed

Description

71%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, concrete description of the tool's capabilities with strong domain keywords. Its main weakness is the complete absence of a 'when to use this' trigger clause, which caps completeness, and the lack of colloquial trigger terms like 'screenshot' or 'capture'.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks for a screenshot or image capture of a GameObject, prefab, or scene object in Unity, or mentions rendering an object from a specific angle."

Include natural trigger synonyms such as "screenshot", "capture", or "image" so the description matches how users actually phrase the request.

Trim the OnEnable side-effect detail from the description ("see the body for side-effect notes" suffices) to spend those tokens on trigger guidance instead.

Dimension	Reasoning	Score
Specificity	"Render a target GameObject from a chosen camera angle with optional layer-based isolation, configurable background (solid/skybox/transparent), multi-light setup via JSON, and Composite (2x2 Front/Right/Back/Top) mode. Returns a PNG image" lists multiple specific concrete actions with comprehensive coverage of the tool's capabilities, matching the top anchor.	5 / 5
Completeness	The "what" is clear and detailed, but there is no "Use when..." or equivalent explicit trigger guidance — the "When isolated=true, inactive children may briefly fire OnEnable" sentence is a conditional caveat, not usage-trigger guidance, which caps completeness at 3 per the judging guidelines. Not score 4 because the "when" is entirely absent rather than merely imprecise.	3 / 5
Trigger Term Quality	Good keyword coverage ("GameObject", "camera angle", "PNG", "isolation", "Composite") but missing natural phrases a user would say such as "screenshot", "capture", or "image of an object". Not score 5 because synonym/colloquial coverage is incomplete; not score 3 because the included keywords are relevant and varied rather than partially covered.	4 / 5
Distinctiveness Conflict Risk	"Render a target GameObject... layer-based isolation... Composite mode" carves a distinct Unity-rendering niche with minimal conflict risk, though it could overlap with a generic Unity screenshot/render skill. Mostly distinct with minor overlap, matching the score-4 anchor rather than 5 (no distinct trigger phrases reinforcing the niche) or 3 (the domain is far from generic).	4 / 5
	Total	16 / 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/screenshot-isolated/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.