CtrlK
BlogDocsLog inGet started
Tessl Logo

object-get-data

Get serialized data for a Unity `UnityEngine.Object` — all serializable fields and properties. Supports token-saving path-scoped reads via `paths` or `viewQuery`. Pair with 'object-modify' when you need to write back.

55

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./Unity-MCP-Plugin/.claude/skills/object-get-data/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 content is actionable and well-structured for a single-purpose read tool, with executable commands and complete schemas. Its main weaknesses are repeated path-syntax/field descriptions and large inlined JSON schemas that would benefit from externalization.

Suggestions

Move the full input and output JSON schemas into a separate references/ file and link to it, keeping only essential field notes inline.

De-duplicate the path syntax and field descriptions (currently restated in the body, input table, and schema).

Add one worked example with a concrete objectRef and a small paths/viewQuery payload to cover the common case.

DimensionReasoningScore

Conciseness

Mostly efficient prose, but the path syntax and field descriptions are repeated across the body, input table, and inlined JSON schema, and the large input/output schemas are inlined rather than externalized.

3 / 5

Actionability

Provides an executable CLI command, concrete path syntax, stdin/file variants, and full JSON schemas for input and output; only minor gaps (no worked example with a real objectRef).

4 / 5

Workflow Clarity

This is a simple single-step read tool with an unambiguous call; no destructive/batch loop is required so the simple-skill exception applies, though no validation guidance for verifying partial reads is given.

4 / 5

Progressive Disclosure

The body has section structure but inlines the full input and output JSON schemas, which would fit better in a separate reference file; no bundle files exist to externalize detail.

3 / 5

Total

14

/

20

Passed

Description

58%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 is specific and well-scoped to a Unity object read operation with clear capability statements, but it omits an explicit 'Use when...' trigger clause, capping its completeness. Trigger term coverage is solid but lacks synonyms.

Suggestions

Add an explicit trigger clause, e.g. 'Use when you need to inspect or read a Unity object's serialized fields/properties without modifying it.'

Broaden trigger terms with synonyms users naturally say (e.g. 'inspect', 'dump', 'Unity component', 'GameObject fields').

Clarify that this is read-only to sharpen distinction from the 'object-modify' sibling skill.

DimensionReasoningScore

Specificity

Names the domain (Unity serialized data) and several concrete actions — 'all serializable fields and properties', 'path-scoped reads via paths or viewQuery', 'write back' — with only minor coverage gaps.

4 / 5

Completeness

Has a clear 'what' but no explicit 'Use when...' trigger clause; per the guideline a missing trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

Includes relevant developer terms ('Unity', 'serialized data', 'fields and properties', 'path-scoped reads', 'object-modify') but lacks common synonyms or file extensions users might naturally say.

3 / 5

Distinctiveness Conflict Risk

Clear Unity-object-read niche, explicitly paired with 'object-modify' for writes; only minor overlap risk with that sibling skill.

4 / 5

Total

14

/

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.