jui-controls

Create JUI controls — interactive form field components used in GWT/JUI applications. Use this skill when the user asks to: create a new control, build a custom form field, create an interactive input component, or asks about control patterns. Also trigger when the user mentions control, form field, value management, dirty detection, or asks how to create a reusable input that can be placed in a ControlForm.

Quality

79%

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 ./jui-skills/jui-controls/SKILL.md

Quality

Content

75%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 highly actionable, well-organized skill body with executable templates and a clear build workflow. Its main weakness is conciseness: duplicated method examples and two overlapping full-class templates inflate the token budget without adding guidance.

Suggestions

Show valueFromSource/valueToSource once — pick the canonical StringSupport.safe form and reference it from the template instead of repeating both variants.

Collapse the Minimal Template and Full Template with Style Variants into a single progressive template, or move the variant/creator-class detail into a reference file once bundle files are introduced.

Add a final 'Verify' step to the Workflow (e.g., confirm the control renders, dirty detection toggles, and validation messages fire) so the sequence has an explicit checkpoint.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and code-focused, but contains noticeable redundancy: valueFromSource/valueToSource appear in the Minimal Template and again under Required Methods with differing implementations (inputEl.value vs StringSupport.safe), and two near-complete class templates (Minimal and Full with Variants) overlap heavily.	3 / 5
Actionability	Fully executable, copy-paste-ready templates cover the common cases including forms integration, composing child components, the creator class, and delayed modification handlers.	5 / 5
Workflow Clarity	The 'Workflow' section gives a clear 10-step sequence for building a control; this is a build task rather than a destructive/batch operation so no validation cap applies, but there is no explicit verify/test checkpoint for the finished control.	4 / 5
Progressive Disclosure	No bundle files exist, so all content is inline, but the body is well-sectioned and pushes detail to sibling skills via clearly signaled one-level references ('see the jui-styles skill', 'see the jui-dombuilder skill').	4 / 5
	Total	16 / 20 Passed

Description

83%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 strong, well-structured description that clearly states the skill's purpose and provides explicit, natural trigger phrases. It is comprehensive on the 'when' axis; the main room for improvement is disambiguating controls from the sibling jui-components skill.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('create a new control, build a custom form field, create an interactive input component, or asks about control patterns'), but the first three are overlapping restatements of the same action, leaving minor coverage gaps rather than comprehensive breadth.	4 / 5
Completeness	Explicitly answers both 'what' ('Create JUI controls — interactive form field components used in GWT/JUI applications') and 'when' with concrete trigger phrases ('Use this skill when the user asks to:... Also trigger when the user mentions...').	5 / 5
Trigger Term Quality	Good coverage of natural terms users would say ('control', 'form field', 'value management', 'dirty detection', 'reusable input', 'ControlForm'), though 'control patterns' leans slightly technical and a few synonyms are missing.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche with distinct triggers (ControlForm, dirty detection, value management), but the closely related jui-components skill represents a real overlap risk that the description does not explicitly disambiguate.	4 / 5
	Total	17 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: juiproject/jui-stack
Path: jui-skills/jui-controls/SKILL.md
Commit: 3639345

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.