The body is lean and assumes competence: no concept explanations, just a behavior summary, executable invocation, troubleshooting, and compact input/output schemas; every section earns its place.

It provides a fully executable copy-paste command plus file/stdin variants and concrete troubleshooting for a missing CLI, matching the score-3 executable-guidance anchor.

This is a simple single-task skill whose single action (run the tool, get sorted shader names) is unambiguous, with behavior and troubleshooting making the flow clear; per the simple-skills note this scores 3.

A compact skill with no external references and no bundle files, organized into clear sections (Behavior, How to Call, Troubleshooting, Input, Output), matching the under-50-lines note that well-organized sections alone can score 3.

It names one concrete action ("List all shaders ... sorted by name") but does not enumerate multiple distinct concrete actions, matching the score-2 anchor rather than the multi-action score-3 example.

It states what ("List all shaders ... sorted by name") and an explicit when ("Use this to discover a valid shaderName for 'assets-material-create'"), satisfying the explicit-trigger requirement for a 3.

"shaders" is a relevant natural keyword, but the trigger is tied to a sibling tool name ("assets-material-create") and lacks common natural variations like "find shader" or "what shaders are available", so it matches the score-2 anchor.

The niche is narrow (listing shaders to feed a specific material-creation tool) with a distinct, tool-specific trigger, making conflict with other skills unlikely.