CtrlK
BlogDocsLog inGet started
Tessl Logo

makepad-shaders

CRITICAL: Use for Makepad shader system. Triggers on: makepad shader, makepad draw_bg, Sdf2d, makepad pixel, makepad glsl, makepad sdf, draw_quad, makepad gpu, makepad 着色器, makepad shader 语法, makepad 绘制

57

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/makepad-shaders/SKILL.md

The canonical home for this skill is makepad-shaders in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

75%Scale 1-5

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

This is a well-structured skill that provides concrete, actionable shader patterns with good progressive disclosure to external references. The code examples are copy-paste ready and cover the most common use cases. Minor weaknesses include some unnecessary explanations of concepts Claude would know, a lack of error-handling/debugging guidance, and unverifiable external file references.

Suggestions

Add a brief troubleshooting section covering common shader compilation errors and how to diagnose them

Remove or trim the 'When Answering Questions' section items that state things Claude already knows (e.g., explaining what live-reload means)

DimensionReasoningScore

Conciseness

Generally efficient with good use of tables and code examples. Minor over-explanation in sections like 'When Answering Questions' which states things Claude already knows (e.g., 'Makepad shaders use Rust-like syntax'). The 'IMPORTANT: Documentation Completeness Check' section adds some procedural overhead but is arguably necessary for correctness.

4 / 5

Actionability

Provides multiple concrete, copy-paste ready code examples covering common patterns (basic shader, rounded rect, gradient, circle). The Sdf2d quick reference and built-in functions tables are actionable. Minor gap: no example of vertex shaders, custom draw structs in Rust, or how to define custom uniforms beyond simple color properties.

4 / 5

Workflow Clarity

The 'When Writing Code' section provides a clear checklist of rules. The documentation completeness check has a reasonable fallback workflow. However, there's no explicit validation or error-handling workflow for shader development (e.g., what happens when a shader fails to compile, how to debug). Since shaders aren't destructive batch operations, the missing feedback loop cap doesn't apply, but a simple skill like this could benefit from a brief troubleshooting note.

4 / 5

Progressive Disclosure

Good structure with clear references to external files (references/*.md, _base/ directory patterns). The table of advanced patterns is well-organized. However, since no bundle files were provided, we can't verify the referenced paths exist. The skill keeps inline content to key patterns and tables while pointing to detailed docs, which is appropriate. Minor issue: the community/ reference is vague with no description of what's there.

4 / 5

Total

16

/

20

Passed

Description

58%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 excels at trigger term coverage and distinctiveness, providing an extensive list of specific keywords including Chinese-language variants. However, it critically lacks any description of what the skill actually does—there are no concrete actions or capabilities listed. It reads more like a keyword index than a skill description.

Suggestions

Add concrete capability descriptions such as 'Writes and debugs Makepad shaders, explains Sdf2d drawing primitives, helps with draw_bg/draw_quad syntax, and converts GLSL concepts to Makepad shader language.'

Restructure to lead with a 'what it does' statement before the trigger terms, e.g., 'Guides users through Makepad's shader system including SDF-based drawing, GPU pipeline configuration, and custom widget rendering. Use when...'

DimensionReasoningScore

Specificity

Names the domain ('Makepad shader system') but provides no concrete actions. There is no description of what the skill actually does—no verbs like 'generates', 'writes', 'debugs', or 'explains'. It only lists trigger terms without describing capabilities.

2 / 5

Completeness

The 'when' is explicitly addressed with trigger terms, but the 'what' is almost entirely missing—there is no description of what the skill does beyond identifying the domain as 'Makepad shader system'. The lack of a clear 'what' caps this score low.

2 / 5

Trigger Term Quality

Excellent coverage of natural trigger terms including specific API names (Sdf2d, draw_bg, draw_quad), domain terms (shader, glsl, sdf, gpu, pixel), and even Chinese-language synonyms (着色器, shader 语法, 绘制). Users searching for Makepad shader help would likely use one of these terms.

5 / 5

Distinctiveness Conflict Risk

The description targets a very specific niche—Makepad's shader system—with highly distinctive trigger terms like 'Sdf2d', 'draw_bg', and 'draw_quad' that are unlikely to conflict with any other skill.

5 / 5

Total

14

/

20

Passed

Validation

90%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
Reviewed

Table of Contents

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.