assets-shader-get-data

Inspect Unity shader assets for properties, subshaders, passes, and compilation messages.

Updated May 27, 2026
One-click install
npx skills add https://github.com/AdielMag/ClashUp --skill assets-shader-get-data-adielmag
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: assets-shader-get-data
Source: https://github.com/AdielMag/ClashUp/tree/main/client/ClashUp.Unity/.claude/skills/assets-shader-get-data
Command: npx skills add https://github.com/AdielMag/ClashUp --skill assets-shader-get-data-adielmag

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires unity-mcp-cli.

What problem does it solve? Debugging or auditing shaders in a Unity project normally requires opening the editor and clicking through inspectors. This Skill retrieves detailed shader data — properties, subshader and pass structure, compilation errors, and supported status — directly through the unity-mcp-cli, with token-saving scoped reads for large shaders. ## Core Features & Use Cases - Shader Inspection: Returns shader name, render queue, supported status, property count, and pass count for any shader asset referenced by path, GUID, or instance ID. - Compilation Diagnostics: Includes per-platform compilation error and warning messages with line numbers and severity. - Token-Saving Scoped Reads: Use paths or viewQuery to read only specific fields or subtrees instead of the full shader payload. - Use Case: A material renders pink in your build. Run this tool on the shader to check HasErrors and Messages, identify the failing platform, then drill into the failing pass source code with includeSourceCode. ## Quick Start Ask the AI to get the compilation messages and property list for the shader at Assets/Shaders/MyShader.shader using the assets-shader-get-data tool.

Frequently Asked Questions about assets-shader-get-data

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check why a Unity shader fails to compile?▼

Call the tool with the shader's asset reference and includeMessages set to true. The response returns per-platform compilation messages with line numbers and severity, plus a HasErrors flag for quick checks.

How to list all properties of a Unity shader programmatically?▼

Set includeProperties to true when calling the tool. It returns each property's name, display description, type, flags, range bounds, and default texture for Texture properties.

How do I find a shader asset before inspecting it?▼

Use the assets-find tool with the filter t:Shader to search by name, or assets-shader-list-all to enumerate every shader name in the project. Then pass the resulting path, GUID, or instance ID as the assetRef.

Can I read only part of a large shader's data to save tokens?▼

Yes. Supply paths to read specific fields like 'nested/field' or 'arrayField/[0]', or use viewQuery to navigate to a subtree with name regex, max depth, or type filters. The two options are mutually exclusive.

Why is the shader source code missing from the response?▼

Source code is excluded by default because it can be very large. Set includeSourceCode to true, which also requires includeSubshaders, to embed pass source code in the subshader data.