CtrlK
BlogDocsLog inGet started
Tessl Logo

robius-widget-patterns

CRITICAL: Use for Robius widget patterns. Triggers on: apply_over, TextOrImage, modal, 可复用, 模态, collapsible, drag drop, reusable widget, widget design, pageflip, 组件设计, 组件模式

48

Quality

52%

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/skills/robius-widget-patterns/SKILL.md

The canonical home for this skill is robius-widget-patterns in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

57%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 is a solid pattern catalog for Makepad widget development with concrete, mostly executable Rust code examples covering common UI patterns (toggle, collapsible, loading states, portal lists). Its main weaknesses are verbosity—several complete implementations are inlined that could be referenced from bundle files—and the lack of workflow guidance for pattern selection or validation. The progressive disclosure structure is partially undermined by the amount of inline code.

Suggestions

Move the longer code examples (Avatar, LoadableContent, PortalList) into the referenced `_base/` pattern files and keep only concise summaries with links in SKILL.md to improve conciseness and progressive disclosure.

Add a brief decision guide or flowchart at the top helping Claude choose which pattern to apply based on the user's requirements (e.g., 'Need toggle between views? → Text/Image Toggle Pattern').

Add validation/debugging guidance: how to verify a widget renders correctly, common compilation errors with Makepad widgets, and how to troubleshoot visibility/layout issues.

DimensionReasoningScore

Conciseness

The skill is fairly long (~300 lines) with several complete code examples. Some patterns (like the full Avatar implementation) are quite verbose and could be summarized with references to bundle files. The best practices list at the end restates things already demonstrated in the code. However, it avoids explaining basic Rust or Makepad concepts Claude would already know.

3 / 5

Actionability

The code examples are concrete, executable Rust with complete struct definitions, live_design! macros, and impl blocks. Minor gaps exist—some examples reference undefined types (e.g., `UserInfo`, `AvatarTextInfo`, `utils::first_letter`) without clarification, and the PortalList pattern has a `self.populate_item` placeholder—but overall the patterns are copy-paste ready.

4 / 5

Workflow Clarity

This is a pattern catalog rather than a multi-step workflow, so sequential steps are less critical. However, there's no guidance on when to use which pattern, no decision tree for choosing between patterns, and no validation steps (e.g., how to verify a widget renders correctly or how to debug common issues). For a pattern-oriented skill, the lack of a selection workflow or testing/validation guidance limits clarity.

3 / 5

Progressive Disclosure

The skill references a `_base/` directory with 14+ numbered patterns and a `references/` directory with additional files, which is good structure. However, no bundle files were provided to verify these exist, and the main SKILL.md inlines substantial code (~250 lines of examples) that could arguably live in the referenced pattern files. The table of patterns is well-organized but the inline code creates a long document that partially undermines the disclosure structure.

3 / 5

Total

13

/

20

Passed

Description

47%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 effectively identifies its niche domain (Robius widget patterns) and provides a comprehensive list of trigger terms in both English and Chinese, which aids in skill selection. However, it critically lacks any description of what the skill actually does—there are no concrete actions, verbs, or outputs described. The description reads more like a keyword index than a functional description.

Suggestions

Add concrete action verbs describing what the skill does, e.g., 'Implements reusable Robius widget patterns including collapsible panels, drag-and-drop interfaces, modal dialogs, and page-flip animations.'

Include a 'Use when...' clause that contextualizes the trigger terms, e.g., 'Use when building or designing UI components in the Robius framework, including modals, collapsible elements, or drag-and-drop interactions.'

DimensionReasoningScore

Specificity

Names the domain ('Robius widget patterns') but provides no concrete actions. The description lists trigger terms but doesn't explain what the skill actually does—no verbs describing capabilities like 'creates', 'implements', or 'designs'.

2 / 5

Completeness

The 'when' is addressed via the trigger list, but the 'what' is extremely vague—'Robius widget patterns' doesn't explain what concrete actions or outputs the skill provides. There is no explanation of what the skill actually does beyond naming a domain.

2 / 5

Trigger Term Quality

Includes a good variety of natural trigger terms including both English and Chinese keywords (apply_over, TextOrImage, modal, collapsible, drag drop, reusable widget, widget design, pageflip, plus Chinese equivalents). Missing some common variations but overall solid keyword coverage for a niche domain.

4 / 5

Distinctiveness Conflict Risk

The specificity to 'Robius' framework and the unique combination of trigger terms (including Chinese terms and domain-specific terms like 'apply_over', 'pageflip', 'TextOrImage') make it fairly distinct. Minor overlap risk with generic widget/UI design skills.

4 / 5

Total

12

/

20

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

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