CtrlK
BlogDocsLog inGet started
Tessl Logo

makepad-dsl

CRITICAL: Use for Makepad DSL syntax and inheritance. Triggers on: makepad dsl, live_design, makepad inheritance, makepad prototype, "<Widget>", "Foo = { }", makepad object, makepad property, makepad DSL 语法, makepad 继承, makepad 原型, 如何定义 makepad 组件

61

Quality

72%

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

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

A well-organized, actionable reference with solid code examples and clear guidance sections, penalized mainly by dangling references to missing bundle files. Conciseness and actionability are strong; progressive disclosure is undermined by the absent reference files.

Suggestions

Ship the referenced ./references/dsl-syntax.md and ./references/inheritance.md files (or remove the references and keep the material inline) so the signaled progressive disclosure is not broken.

Either remove the DSL Syntax Reference table or move it into the missing dsl-syntax.md to cut the overlap with the Key Patterns code blocks and improve conciseness.

Add one complete live_design!{ ... } example tying together the DSL block and the Rust struct so the linking pattern is fully executable end-to-end.

DimensionReasoningScore

Conciseness

The body is mostly lean code examples and tables with little padded prose, but the DSL Syntax Reference table partially repeats what the Key Patterns code blocks already show, leaving minor redundancy to trim.

4 / 5

Actionability

Concrete, mostly copy-paste-ready code blocks cover anonymous/named objects, inheritance override, widget instantiation, and Rust struct linking; a full end-to-end live_design! macro example would close the small gap to fully executable coverage.

4 / 5

Workflow Clarity

Clear numbered guidance exists ('When Writing Code', 'When Answering Questions') plus a Documentation Completeness Check with an error/fallback branch; for this code-generation skill there are no destructive batch operations requiring validation, so this sits at clear-sequence-with-minor-gaps.

4 / 5

Progressive Disclosure

Structure is intended well (a dedicated Documentation section signals one-level-deep references to dsl-syntax.md and inheritance.md), but those referenced files do not exist in the bundle, so the externalized detail is unreachable and the inline reference material is doing all the work.

3 / 5

Total

15

/

20

Passed

Description

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

A tightly scoped, bilingual trigger-rich description with strong distinctiveness. Its main weakness is a thin 'what' statement that names the domain and two capabilities rather than enumerating concrete actions.

Suggestions

Expand the 'what' clause to list 3-4 concrete actions (e.g., 'Define DSL prototypes, inherit and override widget properties, link Rust structs via live_design!').

Lead with a natural-language capability sentence before the 'Triggers on' list so the 'what' is explicit without relying on the trigger enumeration.

DimensionReasoningScore

Specificity

Names the domain and two concrete capabilities ("Makepad DSL syntax and inheritance") but lists no further concrete actions, matching the anchor that names domain plus 1-2 actions without comprehensive coverage.

3 / 5

Completeness

It states both a 'what' ("Use for Makepad DSL syntax and inheritance") and an explicit 'when' ("Triggers on:" list), but the 'what' is terse and the trigger list leans on syntax fragments rather than fully explicit natural trigger guidance.

4 / 5

Trigger Term Quality

Strong keyword coverage ("makepad dsl", "live_design", "makepad inheritance", "makepad prototype", "<Widget>", plus Chinese synonyms) gives good natural-term breadth; a few common phrasings are still missing, so it sits just below fully comprehensive.

4 / 5

Distinctiveness Conflict Risk

Every trigger is scoped to the Makepad niche (makepad-prefixed terms, live_design macro, DSL syntax), giving a clear niche with minimal overlap risk against other skills.

5 / 5

Total

16

/

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.