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

69%

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

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 body gives fully executable CLI guidance with useful fallbacks and troubleshooting, but it is padded by triple-stated input documentation and inlined machine-generated JSON schemas. Consolidating the duplicated parameter documentation and moving the schemas to reference files would tighten it substantially.

Suggestions

Collapse the '## Inputs' bullets, '## Input' table, and '### Input JSON Schema' into a single parameter table — three representations of the same three parameters is the main source of redundancy.

Move the Input/Output JSON schemas to a reference file (e.g. references/schemas.md) and keep only the output shape summary inline, so SKILL.md stays an overview.

Replace the placeholder example ('string_value', 'maxResults': 0) with a realistic invocation such as searching for 'Sprites-Default' with maxResults 5, and remove the verbatim restatement of the description in the opening line.

Dimension	Reasoning	Score
Conciseness	Sections are individually lean with no concept over-explanation, but the parameter spec is stated three times — the '## Inputs' bullets, the '## Input' table, and the '### Input JSON Schema' — and the opening line restates the frontmatter description verbatim. This is 'mostly efficient but could be tightened' (anchor 3) rather than the minor trim of anchor 4 or the padded prose of anchor 2.	3 / 5
Actionability	Provides copy-paste-ready commands — 'unity-mcp-cli run-tool assets-find-built-in --input ...' — with --input-file and stdin variants plus troubleshooting for a missing CLI. Minor gaps only: the example uses placeholder values ('string_value', 'maxResults': 0) rather than a realistic invocation, keeping it below anchor 5's coverage of common cases.	4 / 5
Workflow Clarity	The single read-only action is unambiguous, with a worked call, fallback invocation styles, and troubleshooting; no validation is required for a non-destructive search. Minor gaps (placeholder example values, redundant Inputs/Input sections) keep it at anchor 4 rather than 5.	4 / 5
Progressive Disclosure	Content is sectioned but imperfectly organized: duplicate 'Inputs' and 'Input' headings, Troubleshooting oddly nested under 'How to Call', and ~75 lines of machine-generated Input/Output JSON schemas inlined in SKILL.md that would fit better in a separate reference file. This matches anchor 3 ('some structure but could be better organized; content that should be separate is inline').	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 appropriately niche, clearly stating what the skill does and its GUID limitation, but it never tells Claude when to use it. Adding a 'Use when...' trigger clause and natural synonyms like 'find' or 'default assets' would raise both completeness and trigger quality.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user wants to find or search Unity's built-in/default assets like Sprites-Default or the built-in fonts.'

Include natural synonyms users would actually say — 'find', 'default assets', 'editor resources' — alongside 'search' and 'built-in assets'.

Briefly mention what results look like (asset references by instanceID) so the 'what' is fully concrete.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions — 'Search the built-in assets of the Unity Editor (located at Resources/unity_builtin_extra)' and 'Filters by name and/or type' — plus an explicit GUID limitation, with only minor coverage gaps (no mention of result caps or ranking). It exceeds anchor 3 (only 1-2 generic actions) but falls short of anchor 5's comprehensive coverage.	4 / 5
Completeness	The 'what' is clear (search built-in Unity assets, filter by name and/or type) but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. Not 2, because the 'what' is specific and concrete rather than vague.	3 / 5
Trigger Term Quality	Contains some relevant natural terms ('Search', 'built-in assets', 'Unity Editor') but misses common variations users would say such as 'find', 'default assets', or 'built-in resources'. This matches anchor 3 (relevant keywords missing synonyms) better than anchor 4's good coverage with only a few terms missing.	3 / 5
Distinctiveness Conflict Risk	Clear niche — Unity Editor built-in assets with an explicit 'GUID-based lookups are not supported' boundary distinguishing it from project-asset searches — but sibling asset-search skills could overlap on generic terms like 'assets' and 'search'. Mostly distinct with minor overlap risk (anchor 4), not the minimal-conflict clarity of anchor 5.	4 / 5
	Total	14 / 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: 4c8056f

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