assets-shader-list-all

List all shaders available in the project assets and packages, sorted by name. Use this to discover a valid `shaderName` for 'assets-material-create'.

Quality

84%

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

Quality

Content

73%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 delivers an executable, unambiguous single-step workflow with concrete commands and troubleshooting. Its main weakness is token efficiency: the description is duplicated, a no-op parameter is documented, and generic complex-input guidance pads a tool that needs no input.

Suggestions

Remove the opening paragraph that duplicates the frontmatter description, or replace it with a single line of genuinely new information.

Drop the `nothing` parameter from the Input table, its JSON schema, and the example input — or state plainly that the tool takes no input and can be called with an empty object.

Trim the generic multi-line/stdin boilerplate (or move it to a shared CLI-usage reference) since this tool's input is trivial; keep only the direct run-tool command and the Troubleshooting note.

Dimension	Reasoning	Score
Conciseness	The opening paragraph restates the frontmatter description almost verbatim, the Input section documents a meaningless `nothing` parameter with an empty description and a placeholder example ("nothing": "string_value"), and the multi-line/stdin guidance is boilerplate for a tool that takes no real input. Mostly efficient but with several unnecessary or duplicated segments.	3 / 5
Actionability	Concrete, copy-paste-ready CLI commands are given (run-tool with --input, --input-file, and stdin variants) along with executable troubleshooting (npm install -g / npx) and a pointer to setup instructions. The placeholder input JSON is slightly confusing but the command itself runs as written.	4 / 5
Workflow Clarity	This is a simple, single-purpose, read-only skill and the single action is unambiguous: run the command, receive an alphabetically sorted list of shader names. No destructive or batch operation is involved, so no validation checkpoints are needed.	5 / 5
Progressive Disclosure	Well-organized single-file layout (Behavior, How to Call, Input, Output) with the one external reference (the /unity-initial-setup skill) clearly signaled in Troubleshooting. Minor gaps: inline boilerplate JSON schemas and the redundant Input section keep it just short of a clean 5.	4 / 5
	Total	16 / 20 Passed

Description

87%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.

A concise, third-person description that clearly states a fully-specified action and an explicit, concrete use trigger tied to a downstream tool. Trigger coverage is good but could add a few more natural phrasings for general shader-browsing requests.

Dimension	Reasoning	Score
Specificity	The action is fully specified — "List all shaders available in the project assets and packages, sorted by name" names the domain, the enumeration behavior, and the sort order. It lists one action with its details rather than several distinct actions, keeping it just below the comprehensive 5 anchor.	4 / 5
Completeness	It explicitly answers both questions: what ("List all shaders… sorted by name") and when ("Use this to discover a valid `shaderName` for 'assets-material-create'"). The when-clause is concrete and specific, matching the anchor-5 pattern of explicit trigger guidance.	5 / 5
Trigger Term Quality	Natural trigger terms are present: "list all shaders", "shaderName", "assets-material-create", "project assets", "packages". A few natural variations users might say ("find shader names", "browse shaders", "what shaders exist") are missing, so it falls just short of comprehensive synonym coverage.	4 / 5
Distinctiveness Conflict Risk	Clear niche — enumerating Unity project shaders to feed the assets-material-create tool — with distinct, unlikely-to-collide triggers (shader, shaderName, material creation).	5 / 5
	Total	18 / 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-shader-list-all/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.