makepad-reference

This category provides reference materials for debugging, code quality, and advanced layout patterns.

Quality

33%

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

Quality

Content

59%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 serves as a reference index for Makepad development with a useful quick-fix table and debug tips. Its main weakness is that the Quick Navigation table references topics and files that don't exist in the bundle, making it a broken navigation hub. The actionable content that is present (error fixes, debug commands) is helpful but thin.

Suggestions

Either provide the referenced bundle files (troubleshooting guide, code quality guide, adaptive layout guide) or remove the Quick Navigation table that references non-existent content.

Expand the Common Issues Quick Reference with brief code examples showing the fix in context, not just one-line descriptions.

Add actual file links in the Quick Navigation table (e.g., [TROUBLESHOOTING.md](TROUBLESHOOTING.md)) instead of plain text descriptions in the File column.

Dimension	Reasoning	Score
Conciseness	Generally efficient and avoids over-explaining concepts Claude would know. The introductory sentence repeats the description which is slightly redundant, and the Quick Navigation table references files that don't exist in the bundle, but overall token usage is reasonable.	4 / 5
Actionability	The Common Issues Quick Reference table provides concrete fixes, and the debug tips include executable commands and code snippets. However, the Quick Navigation table references files/topics without actual links or content, and the fixes in the table are brief hints rather than fully executable guidance with context.	3 / 5
Workflow Clarity	As a reference/lookup skill rather than a multi-step workflow skill, the content is well-organized for quick lookup with clear tables. The debug tips provide a clear sequence (set env var, run, add logging). No destructive operations are involved, so validation checkpoints aren't critical here.	4 / 5
Progressive Disclosure	The Quick Navigation table references topics like 'API Documentation', 'Troubleshooting', 'Code Quality', and 'Adaptive Layout' with descriptions in the 'File' column but no actual file links or paths. No bundle files are provided, so these references lead nowhere. The skill claims to be a navigation hub but fails to actually connect to any sub-files.	2 / 5
	Total	13 / 20 Passed

Description

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

This description is extremely vague and reads more like a category label than a skill description. It provides no concrete actions, no trigger guidance, and covers such broad topics (debugging, code quality, layout) that it would conflict with many other skills. It also uses the framing 'This category provides reference materials,' which is passive and uninformative about what the skill actually does.

Suggestions

Replace the abstract category label with specific concrete actions the skill performs, e.g., 'Provides CSS Grid and Flexbox layout patterns, common debugging strategies for JavaScript/TypeScript, and code quality checklists.'

Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about CSS layout techniques, debugging strategies, linting rules, or code review best practices.'

Narrow the scope to reduce conflict risk — 'debugging, code quality, and advanced layout patterns' spans too many domains. Either split into separate skills or specify the exact technology stack covered.

Dimension	Reasoning	Score
Specificity	The description uses entirely vague language — 'reference materials,' 'debugging,' 'code quality,' and 'advanced layout patterns' are abstract categories, not concrete actions. No specific capabilities are described.	1 / 5
Completeness	The 'what' is extremely vague ('provides reference materials') and there is no 'when' clause at all. It fails to answer either question meaningfully.	1 / 5
Trigger Term Quality	Terms like 'debugging,' 'code quality,' and 'layout patterns' are somewhat relevant but very generic. They lack natural user phrases, synonyms, or specific technologies that a user would mention.	2 / 5
Distinctiveness Conflict Risk	'Debugging,' 'code quality,' and 'layout patterns' are so broad that this description could conflict with virtually any coding, CSS, or development-related skill.	1 / 5
	Total	5 / 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-reference/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.