CtrlK
BlogDocsLog inGet started
Tessl Logo

jui-ui

Entry point for building user interfaces with the JUI framework (Java-to-JavaScript UI). Use this skill whenever doing any front-end / UI work in a JUI application: building screens, pages, panels, dialogs, forms, tables, galleries, navigation, or any reusable UI element — and when you need to know what JUI offers, which kind of artefact to build, what standard controls/components/fragments already exist, or how to inspect the JUI source. Routes to the specialised jui-components, jui-controls, jui-fragments and jui-styles skills. Triggers include: JUI, UI, building a screen/page/panel/form/dialog/table/gallery, SimpleComponent, Control, Fragment, DomBuilder, ControlForm, TabNavigator, or 'how do I do X in the UI'.

66

Quality

83%

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

SKILL.md
Quality
Evals
Security

Quality

Content

63%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 well-structured, information-dense entry-point skill with concrete API guidance and clear dual workflows for modifying versus building UI. Its main weaknesses are repetition across the classification table, decision guide, and workflow, and a broken core reference to a catalogue.md that is not present in the bundle.

Suggestions

Ship the referenced catalogue.md (or remove the dependency on it), since the body repeatedly directs the reader to load it for discovering existing artefacts.

De-duplicate the four-building-blocks table, the 'Quick decision guide', and the 'Building new UI' classification step — keep one canonical classification and have the others point to it.

Move the full docs-link table and the jar-extraction script into a reference file (e.g. references/inspecting-source.md) and link to it from the body to reduce inline bulk.

DimensionReasoningScore

Conciseness

Mostly efficient and dense with domain-specific knowledge Claude lacks, but the four-building-blocks table, the 'Quick decision guide', and the 'Building new UI' workflow re-explain the same classification, and the re-render trap is stated then re-referenced — these could be tightened.

3 / 5

Actionability

Provides concrete API patterns (Wrap.$(el).$(root -> {...}), .by("name"), dom.first("name"), Controls.text(...)), a fully executable jar-extraction bash script, and specific class/base-type names, though much guidance delegates to sibling skills rather than giving copy-paste examples.

4 / 5

Workflow Clarity

Clear sequenced workflows for both 'Modifying existing UI' (4 numbered steps) and 'Building new UI' (7 numbered steps) with concrete sub-actions; missing explicit validation/verify checkpoints, but the work is not destructive or batch in a way that triggers the cap.

4 / 5

Progressive Disclosure

Has a clear overview with well-signaled one-level references to sibling skills and GitHub docs, but the heavily-relied-on catalogue.md reference is a broken/missing file, and the full docs-link table plus the jar-extraction script are inlined where a reference file would be more appropriate.

3 / 5

Total

14

/

20

Passed

Description

96%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, specific description that clearly states its purpose as a JUI UI entry point, comprehensively lists concrete actions and natural trigger terms, and explicitly answers both what and when. Its only weakness is moderate trigger overlap with the sibling skills it routes to.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'building screens, pages, panels, dialogs, forms, tables, galleries, navigation, or any reusable UI element', discovering what exists, inspecting the JUI source, and routing to sub-skills — giving comprehensive coverage of the entry-point role.

5 / 5

Completeness

Explicitly answers both what ('Entry point for building user interfaces with the JUI framework... Routes to the specialised... skills') and when ('Use this skill whenever doing any front-end / UI work... Triggers include: ...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural-term coverage including 'UI', 'building a screen/page/panel/form/dialog/table/gallery', framework type names (SimpleComponent, Control, Fragment, DomBuilder, ControlForm, TabNavigator), and the natural phrase 'how do I do X in the UI'.

5 / 5

Distinctiveness Conflict Risk

Clearly scoped to JUI with framework-specific tokens and an explicit routing role that distinguishes it from siblings, but broad triggers like 'Control', 'Fragment', and 'building a form' create minor overlap risk with the jui-controls/jui-fragments skills it routes to.

4 / 5

Total

19

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

relative_links

Relative link issues: 2 missing

Warning

Total

15

/

16

Passed

Repository
juiproject/jui-stack
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.