Name: makepad-layout
Rating: 60 (1 reviews)
Author: administrakt0r

makepad-layout

CRITICAL: Use for Makepad layout system. Triggers on: makepad layout, makepad width, makepad height, makepad flex, makepad padding, makepad margin, makepad flow, makepad align, Fit, Fill, Size, Walk, "how to center in makepad", makepad 布局, makepad 宽度, makepad 对齐, makepad 居中

Quality

70%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/makepad-layout/SKILL.md

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

Quality

Content

72%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 concrete executable Makepad layout patterns and value tables, and it is reasonably token-efficient. Its main weaknesses are a missing validation/feedback loop for the code-generation workflow and inlined reference material plus referenced files that are not present in the bundle.

Suggestions

Add an explicit verification step after code generation (e.g. 'Confirm width/height/flow are set on every container; verify Fill vs Fit usage') to lift workflow_clarity above the validation cap.

Move the property, size, flow, and align reference tables into the referenced ./references/ files and keep only the key patterns inline, improving both conciseness and progressive disclosure.

Ensure the referenced files (./references/layout-system.md, ./references/core-types.md) actually exist in the bundle, or remove the read-or-fallback instruction that depends on them.

Dimension	Reasoning	Score
Conciseness	The body is largely lean — pattern tables and code examples with minimal padding — but a few sections (the ASCII box model, the property reference) restate layout basics Claude already knows, keeping it just below fully efficient.	4 / 5
Actionability	Fully executable, copy-paste-ready Rust snippets cover the common cases (basic container, centering, row, fixed+flex), supplemented by concrete value tables for Size, Flow, and Align.	5 / 5
Workflow Clarity	The 'Documentation Completeness Check' gives a numbered sequence with a read-fail fallback, but there are no validation checkpoints for the actual code-writing task; per the feedback-loop cap, the absence of verification for a code-generation workflow holds this at 3.	3 / 5
Progressive Disclosure	The body points to two reference files ('./references/layout-system.md', './references/core-types.md') for detail, which is good, but those directories do not exist in the bundle, and substantial reference-style material (property/size/flow/align tables) is inlined rather than offloaded.	3 / 5
	Total	15 / 20 Passed

Description

67%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 excels at trigger-term coverage and distinctiveness with rich Makepad-specific keywords including multilingual variants, but it omits any statement of the concrete actions the skill performs, leaving the 'what' implicit and weakening specificity and completeness.

Suggestions

Add an explicit 'what' clause naming the actions the skill performs, e.g. 'Generate Makepad layout code and explain sizing, flow, and alignment.'

Lead with the capability statement before the trigger list so readers learn what the skill does before when it applies.

Use third-person action verbs ('Generates layout code', 'Explains sizing and flow') rather than the bare 'Use for' directive to improve specificity.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Makepad layout system') but lists no concrete actions — it says only 'Use for' followed by trigger terms, never stating what the skill actually does (write layout code, explain sizing, etc.).	2 / 5
Completeness	There is a clear 'when' ('Use for Makepad layout system. Triggers on: ...') but no explicit 'what' describing the skill's capabilities, so it caps at the 'clear what but missing when' inverse — here the 'when' is explicit but the 'what' is absent, leaving it at the midpoint.	3 / 5
Trigger Term Quality	Comprehensive natural-term coverage including synonyms ('makepad layout', 'width', 'height', 'flex', 'center in makepad'), type names (Fit, Fill, Size, Walk), and Chinese variants (makepad 布局, 宽度, 对齐, 居中).	5 / 5
Distinctiveness Conflict Risk	Highly niche triggers specific to Makepad (Fit, Fill, Walk, makepad layout) make conflict with unrelated skills minimal; the domain is clearly bounded.	5 / 5
	Total	15 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
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
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/makepad-layout/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.