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.

61

Quality

71%

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

67%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 well-structured, actionable tool-definition body with clear sections and copy-paste CLI examples. The main drag is redundancy between the intro and dedicated sections, and placeholder values in the headline example.

Suggestions

Trim the intro paragraph so it does not restate the Camera/Background/Side-effect details already covered in their own sections.

Replace the 'string_value' placeholders in the headline CLI example with a realistic minimal call (e.g. gameObjectRef + cameraView + isolated) so it is immediately copy-paste runnable.

Deduplicate the lights field enumeration between the 'Lights' section and the Input table (keep the full list in one place).

DimensionReasoningScore

Conciseness

Mostly efficient but padded in places: the long intro paragraph (line 8) restates details already covered in dedicated Camera/Background/Side-effect sections, and the lights field list appears in both the 'Lights' section and the Input table, adding redundancy.

3 / 5

Actionability

Provides concrete, executable CLI commands (run-tool with --input, --input-file, stdin pipe) plus a real lights JSON example, though the primary example fills every parameter with 'string_value' placeholders rather than a copy-paste-ready realistic call.

4 / 5

Workflow Clarity

This is a single-action render skill with an unambiguous invocation and a troubleshooting note; no destructive/batch validation is required, so the simple-skill path applies, but there is no explicit check that the returned PNG is non-empty or valid.

4 / 5

Progressive Disclosure

Well-organized sections (Camera views, Background modes, Lights, Side-effect caveat, How to Call, Input, Output) with no nested references and no bundle files present; the ~110-line inlined JSON schema is a minor organization gap that could live in a reference file but is reasonable to keep inline for a tool definition.

4 / 5

Total

15

/

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, well-scoped description that clearly conveys what the skill does and is highly distinctive. Its main weakness is the absence of an explicit 'Use when...' trigger clause, which caps completeness.

Suggestions

Add an explicit trigger clause such as 'Use when the user asks to screenshot or render a GameObject from a specific camera angle, isolate an object in a render, or set up custom lighting for a capture.'

Include common synonyms users might say ('screenshot', 'capture', 'snapshot') alongside 'Render' to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Render a target GameObject from a chosen camera angle', 'layer-based isolation', 'configurable background (solid/skybox/transparent)', 'multi-light setup via JSON', 'Composite (2x2 ...)', 'Returns a PNG image' — giving comprehensive coverage.

5 / 5

Completeness

The 'what' is clearly stated (render a GameObject to a PNG with isolation/background/lighting), but there is no 'Use when...' or equivalent trigger clause, which caps completeness at 3 per the guidelines.

3 / 5

Trigger Term Quality

Good keyword coverage with natural terms like 'Render', 'GameObject', 'camera angle', 'background', 'isolation', 'lights', but omits common synonyms a user might say ('screenshot', 'capture', 'snapshot').

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (Unity GameObject screenshot rendering with isolation/composite/multi-light) with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

17

/

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.