CtrlK
BlogDocsLog inGet started
Tessl Logo

makepad-widgets

Version: makepad-widgets (dev branch) | Last Updated: 2026-01-19 > > Check for updates: https://crates.io/crates/makepad-widgets

34

Quality

30%

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

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

SKILL.md
Quality
Evals
Security

Quality

Content

61%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 content is concise and actionable with solid executable examples, but workflow sequencing lacks explicit validation checkpoints and progressive disclosure is undermined by missing reference files and inlined catalog material. Fixing the references and moving the bulk catalog out would most improve the score.

Suggestions

Create the missing ./references/widgets-core.md, widgets-advanced.md, and widgets-richtext.md files and move the 84-widget catalog, View/Button variants, and ImageFit tables into them, leaving only an overview and quick-start examples in SKILL.md.

Add an explicit validate->fix->retry loop in the Documentation Completeness Check (e.g. on missing file, attempt /sync-crate-skills makepad --force then re-read before falling back to built-in knowledge).

Add a concrete event-handling example showing handle_event/Scope usage, since the trait is listed but no usage pattern is given.

DimensionReasoningScore

Conciseness

The body is mostly lean code examples and tables with little padding; it assumes Claude knows Rust and only adds Makepad-specific patterns, though the 84-widget table and variant tables add some bulk that could be trimmed.

4 / 5

Actionability

Concrete, copy-paste-ready Rust/Live DSL examples for View, Button, Label, Image, and TextInput plus widget trait signatures and property tables give mostly executable guidance with only minor gaps (e.g. no event-handling example).

4 / 5

Workflow Clarity

'When Writing Code' and 'When Answering Questions' provide rough guidance but not a sequenced multi-step workflow, and the Documentation Completeness Check has a fallback but no explicit validate->fix->retry checkpoint, fitting 'steps present but checkpoints missing or implicit'.

3 / 5

Progressive Disclosure

The body signals three ./references/*.md files, but the references directory does not exist, so the references are dead; meanwhile the large 84-widget catalog and variant/trait tables that belong in separate files are inlined into SKILL.md, matching 'content that clearly belongs in separate files is inlined'.

2 / 5

Total

13

/

20

Passed

Description

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

The description field is pure version/update metadata rather than a capability and trigger description, so it fails every dimension of the rubric. It should be rewritten to state what the skill does and when Claude should load it.

Suggestions

Replace the description with a capability statement, e.g. 'Write and explain Makepad widget code (View, Button, Label, TextInput, etc.) using Live DSL patterns. Use when the user asks about Makepad widgets, live DSL syntax, or Rust UI widget code.'

Keep version/update metadata in the body's header block (where it already exists) rather than the frontmatter description field.

Add natural trigger terms users would actually say — 'Makepad widgets', 'live DSL', 'Makepad UI', 'Rust widget code' — to improve trigger and distinctiveness scores.

DimensionReasoningScore

Specificity

The description is metadata only ("Version: makepad-widgets (dev branch) | Last Updated: 2026-01-19 > > Check for updates: https://crates.io/crates/makepad-widgets") with no concrete actions or capabilities stated, matching the 'Entirely vague; no concrete actions' anchor.

1 / 5

Completeness

Neither 'what this does' nor 'when to use it' is addressed anywhere in the description, matching the 'Missing both what and when' anchor.

1 / 5

Trigger Term Quality

No natural trigger keywords appear; 'widgets' is buried inside a version/URL string rather than offered as a phrase users would say, fitting 'No natural keywords; only technical jargon or entirely generic language'.

1 / 5

Distinctiveness Conflict Risk

The text is generic crate metadata that does not describe a niche or distinguishable purpose, so it conflicts with virtually any skill that uses version metadata.

1 / 5

Total

4

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

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.