CtrlK
BlogDocsLog inGet started
Tessl Logo

gameobject-duplicate

Duplicate a batch of GameObjects in the currently opened Prefab or active Scene. Marks each affected scene as dirty after duplication. Use 'gameobject-find' to locate the source GameObjects first.

52

Quality

66%

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

Quality

Content

50%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-structured and mostly actionable, with executable CLI examples and thorough schemas, but it is heavily padded by duplicated JSON schema boilerplate and generic CLI usage instructions. The batch workflow also lacks a verification step, and the large inline schemas belong in a separate reference file.

Suggestions

Deduplicate the JSON schemas: define the GameObjectRef structure once (or move both schemas to a references/ file) instead of repeating the identical $defs block in the Input and Output sections.

Replace the generic unity-mcp-cli invocation boilerplate (stdin/file/pipe instructions, npm troubleshooting) with one skill-specific example, and fix the example input so gameObjectRefs is an array of refs matching the schema.

Add a verification step after duplication, e.g. re-query via gameobject-find or check the post-call Selection to confirm the duplicates exist before reporting success.

DimensionReasoningScore

Conciseness

Roughly 100 of ~170 lines are two JSON schemas that repeat the identical AIGD.GameObjectRef definition verbatim, and the "How to Call"/"Troubleshooting" blockquote is generic unity-mcp-cli boilerplate unrelated to this specific skill. Noticeably verbose with several padded/duplicated sections, matching anchor 2 rather than anchor 3's mostly-efficient profile.

2 / 5

Actionability

Provides executable CLI commands, complete input/output schemas, and a concrete troubleshooting section. Falls short of 5 because the example value "gameObjectRefs": "string_value" contradicts the schema's array type, so the primary example is not copy-paste correct.

4 / 5

Workflow Clarity

The Behavior section gives a coherent sequence (resolve refs atomically, invoke DuplicateGameObjectsUsingPasteboard, mark scenes dirty) and notes duplicates are reachable via post-call Selection, but there is no verification step for confirming the batch duplication succeeded. Per the rubric guideline, a batch operation without validation/verification caps workflow clarity at 3.

3 / 5

Progressive Disclosure

Section headers (Inputs, Behavior, How to Call, Input, Output) give reasonable structure, but the ~100 lines of duplicated schema content are API-reference material inlined in SKILL.md with no bundle files or external references at all. Some structure exists, but content that should be separate is inline, matching anchor 3.

3 / 5

Total

12

/

20

Passed

Description

66%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 concrete, third-person, and reasonably distinctive, with good natural trigger keywords. Its main gap is the absence of an explicit "when to use this skill" clause — the gameobject-find reference is a prerequisite hint rather than a trigger.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to duplicate, copy, or clone GameObjects in a Prefab or the active Scene."

Include natural synonyms such as "copy" and "clone" alongside "duplicate" to broaden trigger term coverage.

DimensionReasoningScore

Specificity

"Duplicate a batch of GameObjects in the currently opened Prefab or active Scene. Marks each affected scene as dirty after duplication" names the domain and several specific behaviors (batch duplication, scene-dirty marking, find-first dependency). Not 3 because the actions are more detailed than a bare 1-2 action listing; not 5 because coverage is limited to the duplicate operation's core actions.

4 / 5

Completeness

The "what" is clear and concrete, but there is no "Use when..." trigger clause; "Use 'gameobject-find' to locate the source GameObjects first" is prerequisite workflow guidance, not when-to-use-this-skill guidance. Per the judging guideline, a missing explicit trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

Natural terms a Unity user would say are present: "duplicate", "GameObjects", "Prefab", "Scene", "batch". Missing common synonyms such as "copy" or "clone", which keeps it below anchor 5 but above anchor 3's thin keyword coverage.

4 / 5

Distinctiveness Conflict Risk

Duplicating GameObjects in a Prefab or Scene is a clear niche with a distinct action verb, distinguishable from sibling gameobject tools. Minor overlap risk remains with closely related Unity scene-manipulation skills, so not 5.

4 / 5

Total

15

/

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.

Validation — 16 / 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.