CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

63

Quality

73%

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

Quality

Content

65%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with executable CLI commands and a complete input schema, but it loses points on conciseness and progressive disclosure due to the large inline schema and placeholder-only call examples, and the single-action workflow would benefit from one real worked example.

Suggestions

Replace the "string_value" placeholders in the How to Call example with at least one concrete worked example (e.g. a real gameObjectRef path and a populated lights array) so the call sequence is unambiguous.

Move the full Input JSON Schema into a referenced reference file (e.g. references/schema.json) and keep only a brief field summary inline, improving both conciseness and progressive disclosure.

Add a short "Validation" note for the isolated=true side-effect path (e.g. recommend isolated=false for scenes with OnEnable-dependent scripts) framed as a checkpoint rather than only a caveat.

DimensionReasoningScore

Conciseness

The body is mostly efficient and avoids explaining basics, but the full ~110-line inline JSON Schema and the placeholder-only "string_value" CLI example add tokens that could be tightened, sitting between the score-2 and score-3 anchors.

2 / 3

Actionability

Provides concrete, copy-paste-ready executable commands ("unity-mcp-cli run-tool screenshot-isolated", "--input-file", stdin pipe, "npx" fallback) plus a real input table with defaults and enum schemas, matching the score-3 fully-executable anchor.

3 / 3

Workflow Clarity

It is a single-action skill so the action is largely unambiguous, but the "How to Call" examples use unhelpful "string_value" placeholders rather than a concrete worked example, leaving the actual call sequence weaker than the score-3 unambiguous anchor.

2 / 3

Progressive Disclosure

Sections are well-organized, but there are no bundle files and the full JSON Schema is inlined as content that could be a separate reference; the body exceeds 50 lines, so it does not qualify for the simple-skill score-3 exception.

2 / 3

Total

9

/

12

Passed

Description

82%

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, third-person, and distinct, but it lacks an explicit "Use when..." trigger clause, which caps completeness at 2. Adding a usage-trigger sentence would round out the description.

Suggestions

Append an explicit trigger clause, e.g. "Use when the user asks to screenshot or render a Unity GameObject, isolate an object for capture, or generate a 2x2 composite view."

Keep the side-effect note but consider moving the "see the body" pointer to the body only, so the description stays a tight capability+trigger statement.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities — "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" — matching the score-3 anchor of multiple specific concrete actions.

3 / 3

Completeness

It clearly answers what (renders with isolation/background/lighting/camera, returns PNG) but has no "Use when..." trigger clause; per the guideline a missing explicit trigger caps completeness at 2, so it does not reach the explicit-triggers score-3 anchor.

2 / 3

Trigger Term Quality

Natural Unity-domain terms a user would say ("GameObject", "camera angle", "Composite", "isolation", "background") give good coverage, above the score-2 "some relevant keywords but missing common variations" anchor.

3 / 3

Distinctiveness Conflict Risk

A clearly distinct niche (Unity GameObject screenshot with layer-based isolation) with third-person voice ("Render...", "Returns...") unlikely to conflict with unrelated skills, matching the score-3 clear-niche anchor.

3 / 3

Total

11

/

12

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.