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, 组件设计, 组件模式

56

Quality

66%

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

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 clean, executable Rust patterns and good conciseness, but it functions as an inlined catalog rather than a guided workflow, and its progressive-disclosure pointers reference files that are absent from the bundle. Adding the missing reference files or inlining their contents and sequencing pattern selection would round it out.

Suggestions

Either ship the referenced files (references/*.md and the _base/ pattern files) or remove the dangling 'Reference Files' and Production Patterns links so navigation is not broken.

Add a short decision guide at the top mapping a user's goal ('toggle between two views', 'virtual list', 'popup') to the specific pattern section, giving the catalog a workflow spine.

Trim the redundant 'Best Practices' list since each item is already demonstrated by the code blocks above it.

DimensionReasoningScore

Conciseness

The body is mostly lean, executable Rust with short section intros and avoids explaining concepts Claude already knows; the only trimmable padding is the end 'Best Practices' recap that restates what the preceding code already shows.

4 / 5

Actionability

It provides complete, copy-paste-ready Rust examples for the common cases (widget structure, text/image toggle, apply_over styling, *Ref wrappers, collapsible, loading state, PortalList), fully executable without pseudocode gaps.

5 / 5

Workflow Clarity

This is a pattern catalog rather than a multi-step process, so there is no overall sequenced workflow with validation checkpoints; each recipe has an implicit code sequence but the skill never frames when to apply which pattern or how to verify the result.

3 / 5

Progressive Disclosure

Sections are clearly headed and a 'Reference Files' list and a Production Patterns table signal deeper material, but the referenced paths (references/widget-patterns.md, references/styling-patterns.md, references/moly-widget-patterns.md, and the _base/ directory) do not exist in the bundle, so the signaled navigation is broken and much pattern content stays inlined.

3 / 5

Total

15

/

20

Passed

Description

60%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 strong trigger coverage and a clear niche, but its 'what' is too vague — it never states the concrete capability, only the trigger surface. Tightening the opening to name the actual actions would lift specificity and completeness.

Suggestions

Lead with a concrete 'what' before the triggers, e.g. 'Designs reusable Makepad widgets using Robius patterns (text/image toggle, modal overlay, collapsible sections, portal lists).'

Move raw API tokens like 'apply_over' and 'TextOrImage' out of the trigger list or pair them with the natural phrase a user would actually say.

Keep the explicit 'Use when ...' trigger clause but ensure the first sentence alone answers both what the skill does and when to reach for it.

DimensionReasoningScore

Specificity

The description names the domain ('Use for Robius widget patterns') but lists no concrete actions — it is a trigger list, not a statement of what the skill does, matching the 'names the domain but actions are minimal or generic' anchor.

2 / 5

Completeness

The 'when' is explicit and strong ('Triggers on: ...'), but the 'what' is vague — 'Robius widget patterns' never says what the skill does (design? implement? a pattern catalog?), so it falls at the clear-but-incomplete midpoint rather than the both-fully-explicit anchor 5.

3 / 5

Trigger Term Quality

It covers many natural user phrases ('reusable widget', 'widget design', 'modal', 'collapsible', 'drag drop', 'pageflip') plus Chinese synonyms, though some entries ('apply_over', 'TextOrImage') are API names rather than natural keywords, leaving a few natural terms missing.

4 / 5

Distinctiveness Conflict Risk

'Robius widget patterns' with distinctive triggers (pageflip, apply_over, 模态, 组件设计) carves out a clear niche tied to the Robius/Makepad ecosystem with minimal overlap risk against other skills.

5 / 5

Total

14

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

referenced_paths_exist

Referenced path issues: 3 missing

Warning

Total

14

/

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.