makepad-skills

Makepad UI development skills for Rust apps: setup, patterns, shaders, packaging, and troubleshooting.

Quality

26%

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

Quality

Content

7%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 skill is essentially a placeholder stub that repeats its own description three times and provides no actionable content whatsoever. It contains no code, no commands, no examples, no workflows, and no structured references — just a link to an external repository. It fails on every dimension of the rubric.

Suggestions

Add concrete, executable code examples for at least the core tasks mentioned (setup, basic UI patterns, shader usage, packaging commands).

Replace the redundant 'When to Use' and 'Instructions' sections with actual step-by-step workflows, e.g., a quick-start guide for setting up a Makepad project with specific cargo commands.

Create bundle files (e.g., SHADERS.md, PACKAGING.md, TROUBLESHOOTING.md) and reference them from the SKILL.md to provide progressive disclosure for the multiple topics claimed.

Include at least one complete, copy-paste-ready example of a minimal Makepad app with DSL widget definitions and event handling.

Dimension	Reasoning	Score
Conciseness	The content is padded with redundant repetition — the description, 'When to Use' section, and 'Instructions' section all say essentially the same thing. However, it's short overall, so it's not severely verbose, just noticeably wasteful with what little content exists.	2 / 5
Actionability	There is zero concrete guidance — no code, no commands, no specific steps, no examples. The entire body is a vague description that links to an external repository without providing any actionable instructions.	1 / 5
Workflow Clarity	No steps, no sequence, no workflow of any kind is present. The skill claims to cover setup, patterns, shaders, packaging, and troubleshooting but provides no process for any of them.	1 / 5
Progressive Disclosure	There are no bundle files, no referenced sub-documents, and the only link is to an external GitHub repository with no explanation of what's there. The content is a stub with no meaningful structure or navigation.	1 / 5
	Total	5 / 20 Passed

Description

45%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 identifies a clear niche (Makepad UI development in Rust) which helps with distinctiveness, but it reads more like a table of contents than an actionable skill description. It lacks a 'Use when...' clause and concrete action verbs, and misses natural trigger terms users might employ when seeking help with Makepad projects.

Suggestions

Add an explicit 'Use when...' clause with trigger phrases like 'Use when the user is building UIs with Makepad, creating Rust GUI applications, or mentions Makepad widgets, DSL, or cross-platform packaging.'

Replace category labels with concrete actions, e.g., 'Creates Makepad widgets, configures project setup, writes custom shaders, packages apps for mobile/desktop, and debugs layout issues.'

Include natural synonyms and related terms users might say, such as 'GUI', 'widget', 'cross-platform', 'mobile app', 'desktop app', or 'Makepad DSL'.

Dimension	Reasoning	Score
Specificity	Names the domain (Makepad UI development for Rust) and lists several high-level action categories (setup, patterns, shaders, packaging, troubleshooting), but these are category labels rather than concrete actions like 'create widgets' or 'configure build targets'.	3 / 5
Completeness	Provides a reasonable 'what' (Makepad UI development covering setup, patterns, shaders, packaging, troubleshooting) but has no 'when' clause or trigger guidance at all, which per the rubric should cap completeness at 3 — and since the 'what' is also somewhat vague, a score of 2 is appropriate.	2 / 5
Trigger Term Quality	Includes relevant keywords like 'Makepad', 'Rust', 'UI', 'shaders', and 'packaging', but misses natural user phrases and synonyms such as 'GUI', 'widget', 'layout', 'DSL', '.rs files', 'mobile app', or 'cross-platform'.	3 / 5
Distinctiveness Conflict Risk	Specifying 'Makepad' as the framework makes this fairly distinctive and unlikely to conflict with generic Rust or other UI framework skills. Minor overlap risk exists with general Rust development or shader-related skills.	4 / 5
	Total	12 / 20 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
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
Path: skills/makepad-skills/SKILL.md
Commit: 57c135b

Reviewed: 4 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.