CtrlK
BlogDocsLog inGet started
Tessl Logo

makepad-basics

CRITICAL: Use for Makepad getting started and app structure. Triggers on: makepad, makepad getting started, makepad tutorial, live_design!, app_main!, makepad project setup, makepad hello world, "how to create makepad app", makepad 入门, 创建 makepad 应用, makepad 教程, makepad 项目结构

65

Quality

79%

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

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

SKILL.md
Quality
Evals
Security

Quality

Content

82%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 highly actionable with complete executable examples and good structure, suffering only from minor over-explanation in the Q&A section and references to bundle files that are not present. It is a strong, well-organized getting-started skill.

DimensionReasoningScore

Conciseness

The body is mostly efficient with copy-paste code and compact tables, but the 'When Answering Questions' section adds general facts ('Makepad is GPU-first', cross-platform) Claude largely already knows, matching the 'minor instances of over-explanation' anchor. It is not 5 because that section could be trimmed.

4 / 5

Actionability

It provides fully executable, copy-paste-ready code for the common cases (complete App struct with live_design!, Cargo.toml, button-click handling, widget access) plus concrete platform install commands, matching the 'fully executable; copy-paste ready' anchor.

5 / 5

Workflow Clarity

The 'When Writing Code' list gives a clear 5-step sequence and the 'Documentation Completeness Check' includes a read-then-validate branch, but the code-writing workflow lacks an explicit validation checkpoint. It is not 5 because not all sequences have explicit checkpoints, and not 3 because the steps are clearly sequenced with one validation loop present.

4 / 5

Progressive Disclosure

The body is well-structured with clear sections and signals one-level-deep references ('./references/app-structure.md', './references/event-handling.md') in a Documentation block, matching the 'good structure; references mostly clear' anchor. It is not 5 because those referenced files are not actually shipped in the bundle, a minor navigation gap.

4 / 5

Total

17

/

20

Passed

Description

76%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 has excellent trigger-term coverage and distinctiveness, with explicit 'when' guidance, but its 'what' is vague and names no concrete actions. Strengthening the capability statement would raise the specificity and completeness scores.

Suggestions

Replace the vague 'getting started and app structure' with concrete actions, e.g. 'Generate Makepad app boilerplate, configure Cargo.toml, and write live_design! UI definitions and event handlers.'

Tighten the 'what' so it pairs concrete verbs with the trigger list, making the capability statement as explicit as the already-strong 'when' clause.

DimensionReasoningScore

Specificity

The description names the domain ('Makepad getting started and app structure') but lists no concrete actions such as generating boilerplate or setting up Cargo.toml, matching the anchor 'Names the domain but actions are minimal or generic'. It does not reach 3 because no specific capabilities are enumerated.

2 / 5

Completeness

It provides both a 'what' (Makepad getting started and app structure) and an explicit 'when' (a 'Triggers on:' list), but the 'what' is vague compared to the concrete-action anchor for 5. It is above 3 because the 'when' is explicit and strong rather than weakly implied.

4 / 5

Trigger Term Quality

The 'Triggers on:' list gives comprehensive natural-language coverage including synonyms ('makepad getting started', 'makepad tutorial', 'makepad hello world', 'makepad project setup') and multilingual variants (makepad 入门, 创建 makepad 应用, makepad 教程, makepad 项目结构), matching the comprehensive-coverage anchor.

5 / 5

Distinctiveness Conflict Risk

Makepad is a specific Rust UI crate and the triggers (live_design!, app_main!, makepad) are highly niche with minimal overlap risk against other skills, matching the 'clear niche with distinct triggers' anchor.

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.