assets-find-built-in

Search the built-in assets of the Unity Editor (located at Resources/unity_builtin_extra). Filters by name and/or type; built-in assets have no GUID so GUID-based lookups are not supported.

Quality

64%

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/assets-find-built-in/SKILL.md

Quality

Content

75%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 a well-structured, mostly executable tool reference with lean prose and a clear call example, held back by triplicated input description, placeholder example values, and inlined JSON schemas that could be externalized.

Suggestions

Replace the placeholder example values ('string_value', 0) with a realistic working example (e.g., a name fragment and a concrete UnityEngine type) so the snippet is immediately runnable.

Dedupe the input description: keep either the prose 'Inputs' section or the 'Input' table, and let the JSON schema serve as the authoritative spec rather than repeating all three.

Add a brief note on interpreting output (e.g., empty result vs. truncated at maxResults) to give the workflow a verification checkpoint.

Dimension	Reasoning	Score
Conciseness	Lean and efficient with no concept over-explanation, but the input is described three times (prose 'Inputs', the 'Input' table, and the full input JSON schema), which is minor redundancy that could be trimmed. Not 5 because of that duplication.	4 / 5
Actionability	Provides a concrete, executable unity-mcp-cli command with JSON input plus stdin/file variants and troubleshooting, but the example uses placeholder values ('string_value', 0) rather than a realistic working example. Not 5 because common-case examples are not shown with real values.	4 / 5
Workflow Clarity	The single read-only tool call is unambiguous with a troubleshooting checkpoint for a missing CLI, but there is no explicit validation of the returned result or guidance on interpreting empty/truncated output. Not 5 because a verify/interpret step for the read result is absent.	4 / 5
Progressive Disclosure	Self-contained body with clear section headers and no nested references, but the bulky input/output JSON schemas are inlined (~75 lines) where they could live in a separate reference file. Not 5 because that bulk could be split out.	4 / 5
	Total	16 / 20 Passed

Description

53%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 clearly states what the skill does and carves out a distinct niche, but omits explicit 'Use when...' trigger guidance, which caps completeness and weakens natural trigger-term coverage.

Suggestions

Add an explicit 'Use when...' clause with natural triggers (e.g., 'Use when searching Unity's built-in/default Editor assets, or when the user asks to find a built-in texture, material, or shader without a GUID').

Include common synonyms and natural phrasings ('built-in assets', 'default assets', 'Editor resources') alongside the technical path so users' words match the description.

Optionally enumerate a few more concrete actions (e.g., 'list, filter, and inspect built-in assets') to lift specificity.

Dimension	Reasoning	Score
Specificity	Names the domain (built-in Unity assets at Resources/unity_builtin_extra) and 1-2 concrete actions ('Search', 'Filters by name and/or type') plus a constraint, but the action list is not comprehensive. It does not reach 4 because no several specific actions are enumerated.	3 / 5
Completeness	Has a clear 'what' (search built-in assets, filter by name/type) but no 'Use when...' or equivalent trigger guidance, capping completeness at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Contains some relevant keywords ('built-in assets', 'Unity Editor', 'name', 'type', 'GUID') but leans on technical jargon ('unity_builtin_extra', 'GUID-based lookups') and misses natural user phrasings like 'find a built-in asset' or 'search default assets'. Not 4 because natural-term coverage is thin.	3 / 5
Distinctiveness Conflict Risk	Clear niche (built-in Unity assets at a specific path) with the GUID exclusion distinguishing it from other asset-finding skills; mostly distinct with only minor overlap risk. Not 5 because trigger phrasing is less crisp than the top anchor.	4 / 5
	Total	13 / 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/assets-find-built-in/SKILL.md
Commit: 91e2472

Reviewed: 5 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.