CtrlK
BlogDocsLog inGet started
Tessl Logo

jui-modals

Build modals and dialogs in the JUI framework — floating UI for create/edit forms, confirmations, alerts and custom panels. Use this skill whenever the work involves a modal, dialog, popup, create form, edit/update form, delete confirmation, confirm/alert/error/save prompt, slide-out panel, or wrapping a component so it opens over the page. Triggers include: Modal, ModalDialog, ModalDialogCreator, IDialogOpener, NotificationDialog, modal dialog, dialog opener, open() pattern, create/update form pair, IProcessable, IEditable, IResetable, IModalAware, confirm dialog, 'open a form in a dialog', 'dialog-enable a component', actions / footer buttons on a dialog.

72

Quality

89%

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

78%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 a strong, executable reference for a complex framework pattern, with concrete code, clear sequencing, and good offloading of exhaustive detail. Its main defect is progressive disclosure: the body repeatedly links to a reference.md that is not present in the bundle, breaking the overview-to-detail path.

Suggestions

Add the missing reference.md bundle file under references/ (with the exhaustive Config options, Variant/Type values, lifecycle interfaces, and NotificationDialog button/outcome matrix the body promises), so the progressive-disclosure links resolve.

Tighten the conciseness by removing the re-statements of IResetable.reset() and the dialog contract that already appear in the interface/event tables, keeping a single authoritative explanation.

Promote validation to an explicit Workflow checkpoint (e.g. a step noting "verify validate() passes and the IModalAware dirty-guard is wired for destructive/save flows") to make the feedback loops visible in the sequence.

DimensionReasoningScore

Conciseness

The body is dense and technical, using tables and terse prose without explaining concepts Claude already knows, but has some repetition (the IResetable.reset() guidance and contract details are restated across the pattern, key-points, and idiom sections). It is not a 5 because a few of these re-statements could be trimmed; it is not a 3 because it is substantially tighter than "some unnecessary explanation."

4 / 5

Actionability

It provides multiple copy-paste-ready Java patterns (MyCreateForm, the ProductCreateForm/ProductUpdateForm pair, NotificationDialog.confirm, build, MyDialog subclass) with real class names, generics, and interface wiring covering the common cases. It is not a 4 because the stubbed remote-call bodies are out of this skill's stated scope (dialog wiring), so the executable guidance that falls within scope is complete; it is not below 5 as no key dialog-wiring step is missing.

5 / 5

Workflow Clarity

The numbered Workflow section (classify → build contents → dialog-enable → reuse shared instance → wire results → reuse Variants → edit-extends-create) gives a clear sequence, and validation/confirmation gates are present in-code (validate() before outcome.accept, NotificationDialog.confirm, the IModalAware dirty-guard). It is not a 5 because validation is not framed as an explicit checkpoint or feedback loop in the Workflow list; it is not a 3 because validation and the dirty-guard are genuinely present rather than absent.

4 / 5

Progressive Disclosure

The body is well sectioned and clearly signals one-level-deep references to [reference.md](reference.md) for exhaustive Config/Variant/matrix/action-API detail, but that referenced file does not exist anywhere in the bundle. It is not a 4 because a missing referenced bundle file is more than a "minor organization gap"; it is not a 2 because the structure and signaling are clearly better than minimal or buried references.

3 / 5

Total

16

/

20

Passed

Description

100%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 is a strong, model example: it concisely states what the skill does, gives an explicit "Use this skill whenever..." trigger clause, and lists both natural and technical trigger terms scoped to the JUI framework. Voice is correctly third person with no first/second-person drift.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities — "create/edit forms, confirmations, alerts and custom panels" plus "slide-out panel" and "wrapping a component so it opens over the page" — covering the full modal space comprehensively. It is not a 4 because there are no notable coverage gaps across the modal/dialog domain.

5 / 5

Completeness

It explicitly answers both "what" ("Build modals and dialogs in the JUI framework — floating UI for create/edit forms, confirmations, alerts and custom panels") and "when" ("Use this skill whenever the work involves a modal, dialog, popup..." plus a concrete Triggers list). It is not a 4 because both halves are concrete and explicit, not merely adequate.

5 / 5

Trigger Term Quality

The "Triggers include:" list gives comprehensive natural terms (modal, dialog, popup, create form, delete confirmation, confirm/alert/error/save prompt, slide-out panel) alongside synonyms and natural phrases ("open a form in a dialog", "dialog-enable a component"). It is not a 4 because common variations are present rather than a few missing.

5 / 5

Distinctiveness Conflict Risk

It is anchored to a specific framework ("JUI framework") with niche trigger symbols (ModalDialogCreator, IDialogOpener, NotificationDialog, IProcessable, IEditable, IResetable, IModalAware), giving a clear niche with minimal conflict risk. It is not a 4 because the framework scoping and symbol triggers make overlap with other skills unlikely.

5 / 5

Total

20

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 3 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.