CtrlK
BlogDocsLog inGet started
Tessl Logo

generative-ui

Generate transient or saved inline chat UI with Alpine/Tailwind controls, outputs, app state, and extensions. Use for knobs, pickers, calculators, dashboards, widgets, or reusable mini-apps.

76

Quality

93%

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

87%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A dense, reference-quality body that adds only framework-specific knowledge Claude lacks, with executable code for the main flow. Its one gap is workflow clarity: the build sequence is implicit rather than an explicit checklist with verification steps.

Suggestions

Open with a short numbered build sequence (pick lifetime → read slotContext inputs → wire outputs → handle app state → style) so the workflow reads as an explicit checklist rather than topical sections.

Add a verification checkpoint, e.g. confirm the output is readable via readAppState("inline-ui:<id>:output") and that transient extensionData is not being relied on for agent-observable state.

Include a brief error-recovery note for common failures such as slotContext being undefined or an extension failing to render inline.

DimensionReasoningScore

Conciseness

The body covers only platform-specific APIs Claude does not know (slotContext, agentNative.ui.output, appAction, appFetch, extensionFetch, the extensionData boundary, semantic Tailwind tokens) without explaining Alpine/Tailwind basics, so every section earns its tokens.

3 / 3

Actionability

It provides copy-paste-ready executable code (the Alpine.data init block, the range input with @input output handler, readAppState) plus concrete API signatures, meeting the fully-executable-examples anchor for the core input/output flow.

3 / 3

Workflow Clarity

Sections are logically ordered (lifetime, inputs, outputs, state, styling) so a sequence is implicit, but there are no explicit numbered steps, validation checkpoints, or error-recovery feedback loops, which the 3 anchor requires.

2 / 3

Progressive Disclosure

The skill is self-contained with no bundle files, organized into clearly headed sections and no nested reference chains, giving easy navigation without a wall of text.

3 / 3

Total

11

/

12

Passed

Description

100%

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 description: third-person, concrete capabilities, explicit trigger guidance, and a distinct inline-chat-UI niche. It cleanly satisfies the what/when/trigger requirements with no first- or second-person voice.

DimensionReasoningScore

Specificity

"Generate transient or saved inline chat UI with Alpine/Tailwind controls, outputs, app state, and extensions" lists multiple concrete capabilities (controls, outputs, app state, extensions) rather than vague language, matching the multiple-specific-actions anchor.

3 / 3

Completeness

It states both what it does ("Generate ... inline chat UI ...") and when to use it via an explicit "Use for" trigger clause, satisfying both the what and when anchors.

3 / 3

Trigger Term Quality

"Use for knobs, pickers, calculators, dashboards, widgets, or reusable mini-apps" gives good coverage of natural terms a user would actually say when requesting an inline UI.

3 / 3

Distinctiveness Conflict Risk

"transient or saved inline chat UI with Alpine/Tailwind" scoped to the extension lifecycle is a clear niche with distinct triggers, unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
BuilderIO/agent-native
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.