jui-components

Create JUI components — reusable UI building blocks used in GWT/JUI applications. Use this skill when the user asks to: create a new component, build a custom UI element, create a panel or widget, or asks about component patterns. Also trigger when the user mentions component, SimpleComponent, StateComponent, buildNode, renderer, DomBuilder, or asks how to create a reusable UI element.

Quality

83%

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

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.

A strong, example-driven skill body: nearly all content is executable Java with tables and explicit trap warnings, and a clear 10-step creation workflow. The main weaknesses are mild redundancy across extraction variants and a monolithic single-file layout where some reference-grade material (DomBuilder essentials) could live in a bundled or sibling file.

Suggestions

Collapse the three element-extraction variants (use, by + build callback) into one example with a short note listing the alternatives, trimming ~30 lines.

Move the DomBuilder Essentials catalog into a references file or lean harder on the jui-dombuilder skill, keeping only the top-3 most common builder methods inline.

Add a light verification checkpoint at the end of the workflow (e.g. confirm the component renders via DEBUG_RENDER flags) to close the loop.

Dimension	Reasoning	Score
Conciseness	The body is almost entirely executable code, tables, and pointed notes with no filler explaining concepts Claude already knows. Minor over-explanation remains — e.g. three separate variants of element extraction (.use, .by + .build callback) are each shown in full — so it sits at "efficient; minor instances that could be trimmed" rather than lean.	4 / 5
Actionability	Every pattern ships complete, copy-paste-ready Java (buildNode with Wrap.$(el), constructor renderer, Component.Config builder, StateComponent/LifecycleStateVariable, creator classes) plus concrete method/flag tables and inline trap warnings like "otherwise the onclick below renders but never fires". This fully matches the top anchor.	5 / 5
Workflow Clarity	The closing 10-step workflow is clearly sequenced and front-loads the decision points (base-class selection table, rendering-approach choice). It earns 4 rather than 5 because there are no validation or verification checkpoints at all, and 3 would understate how explicit the ordering and selection criteria are.	4 / 5
Progressive Disclosure	The single-file body (~590 lines, no references/ or scripts/ bundle) is well-sectioned and consistently delegates depth to clearly signaled one-level-deep sibling skills ("see the jui-dombuilder skill", "use the `jui-modals` skill"), keeping only summaries inline. It stops short of 5 because reference-grade material such as the DomBuilder method catalog lives inline in one large file rather than being split out.	4 / 5
	Total	17 / 20 Passed

Description

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

A well-constructed description with an explicit "Use this skill when…" trigger clause, natural user phrasings, and distinctive API-level keywords. The main gap is that the "what" side states only a single capability (creating components), so it undersells the pattern coverage the body actually provides.

Suggestions

Broaden the capability statement beyond a single action, e.g. "Create JUI components and choose between the standard base classes (SimpleComponent, StateComponent, Component<Config>) and their rendering, styling, and lifecycle patterns".

Consider narrowing the very broad trigger term "component" (e.g. "JUI component") to reduce overlap with sibling skills like jui-controls and jui-styles.

Dimension	Reasoning	Score
Specificity	"Create JUI components — reusable UI building blocks used in GWT/JUI applications" names the domain plus one concrete action, matching the 'names domain and 1-2 concrete actions' anchor; it does not list several specific capabilities (styling, lifecycle, dialogs are only surfaced in the body), so it is not a 4.	3 / 5
Completeness	It explicitly answers both: "what" ("Create JUI components — reusable UI building blocks used in GWT/JUI applications") and "when" ("Use this skill when the user asks to: create a new component, build a custom UI element… Also trigger when the user mentions…") with concrete trigger phrases, matching the top anchor exactly.	5 / 5
Trigger Term Quality	Natural trigger phrases are well covered ("create a new component", "build a custom UI element", "create a panel or widget", "component patterns", "reusable UI element") and reinforced with API identifiers (SimpleComponent, StateComponent, buildNode, renderer, DomBuilder). A few natural user phrasings are missing and the bare term "component" is broad, keeping it just below the comprehensive anchor 5.	4 / 5
Distinctiveness Conflict Risk	JUI-specific identifiers (SimpleComponent, buildNode, DomBuilder) give it a clear niche with mostly distinct triggers, but generic terms like "component", "panel or widget" overlap with closely related sibling skills (jui-controls, jui-styles); it is not a 5 because that overlap risk is real rather than minimal.	4 / 5
	Total	16 / 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
skill_md_line_count	SKILL.md is long (600 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

Repository: juiproject/jui-stack
Path: jui-skills/jui-components/SKILL.md
Commit: 1783d4e

Reviewed: 5 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.