assets-find

Search the Unity asset database using a search filter string. The filter accepts names, labels (`l:`), types (`t:`), AssetBundles (`b:`), areas (`a:`), and globs (`glob:`). See the body for the full filter syntax.

Quality

67%

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/SKILL.md

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable with executable CLI examples and clear sections, but it is not fully token-efficient due to a verbatim duplicate of the filter syntax in the input table and inlined full JSON schemas. Progressive disclosure is adequate but could move the schemas into a reference file.

Suggestions

Remove the verbatim filter-syntax block repeated in the `filter` Input-table row; reference the Filter syntax section instead to save tokens.

Move the full input/output JSON schemas into a `references/` file and link to it, keeping the body as a lean overview.

Keep the troubleshooting tip — it is well targeted at the most likely failure mode.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with a compact filter-syntax list and a runnable CLI example, but the `filter` row of the Input table duplicates the entire filter-syntax section verbatim, and the full input/output JSON schemas add bulk that could be trimmed or referenced.	2 / 3
Actionability	It provides fully executable copy-paste CLI commands (direct invocation, `--input-file`, stdin piping) plus troubleshooting for the common 'command not found' case, matching the score-3 anchor of concrete, complete examples.	3 / 3
Workflow Clarity	This is a single-task read-only search operation with an unambiguous call, so per the simple-skill guideline workflow clarity can score 3; there are no destructive or batch operations requiring validation checkpoints.	3 / 3
Progressive Disclosure	The body is well-organized into sections, but no bundle files exist and the verbose JSON input/output schemas are inlined rather than split into a reference file, so the one-level-deep ideal structure is not fully realized.	2 / 3
	Total	10 / 12 Passed

Description

57%

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 to the Unity asset database and distinctive, but it lacks an explicit 'when to use' trigger clause and uses somewhat technical filter tokens rather than natural user phrasings. Completeness is capped at 2 by the missing trigger guidance.

Suggestions

Add an explicit trigger clause, e.g. 'Use when searching or filtering Unity assets by name, label, type, AssetBundle, area, or glob.'

Lead with a more natural action verb like 'Find and filter Unity assets' to mirror language a user would actually say.

Consider tightening 'See the body for the full filter syntax' since the body syntax is already summarized in the description.

Dimension	Reasoning	Score
Specificity	It names the domain (Unity asset database) and lists concrete filter tokens (`l:`, `t:`, `b:`, `a:`, `glob:`), but does not enumerate multiple distinct actions — search is the only verb, so it stops short of the score-3 anchor listing several concrete actions.	2 / 3
Completeness	The 'what' is clearly covered (search the asset database via a filter string), but there is no 'Use when...' or equivalent explicit trigger clause, which the guidelines say should cap completeness at 2.	2 / 3
Trigger Term Quality	Terms like 'search', 'assets', 'AssetBundles', 'labels', and 'types' are relevant, but a user would more naturally say 'find assets', 'search Unity assets', or 'filter by label' — the natural phrasings are partial and technical tokens dominate.	2 / 3
Distinctiveness Conflict Risk	The Unity-asset-specific scope and the distinctive filter token vocabulary give it a clear niche unlikely to trigger for unrelated skills.	3 / 3
	Total	9 / 12 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/SKILL.md
Commit: e0a24ef

Reviewed: about 13 hours 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.