CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

assistant-ui-runtime

Guide to the assistant-ui runtime system, the state and action layer behind every chat surface. Use when creating a runtime (useLocalRuntime with a ChatModelAdapter, useExternalStoreRuntime for Redux or Zustand backed stores, useRemoteThreadListRuntime, useCloudThreadListRuntime, useAssistantTransportRuntime), wiring AssistantRuntimeProvider, or reading and mutating thread, message, composer, and attachment state. Covers useAui, useAuiState, and useAuiEvent with the stable selector rule, the scope accessors (aui.thread, aui.message, aui.composer, and siblings), the AuiConfig plus AuiProvider grammar, RuntimeCapabilities, and the attachment, speech, dictation, feedback, suggestion, and history adapters. Route here for a provider error ('Cannot read property of undefined'), a removed v0.12 hook import, an infinite re-render from an object literal selector, or state not updating. For multi-thread list UI use thread-list instead; for toolkit definitions and tool call UI use tools instead.

76

Quality

96%

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

93%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 high-quality reference skill body: lean, dense with executable examples that show both correct and incorrect usage, well-organized diagnostics for common errors, and a clean one-level-deep reference structure where every cited file exists. The only soft spot is that the end-to-end runtime setup sequence lives in reference files rather than being outlined inline.

DimensionReasoningScore

Conciseness

The body is dense with API specifics and assumes competence — no padding, no re-teaching of known concepts, and even the gotchas are terse symptom→fix pairs; every token earns its place (e.g. the compact runtime hierarchy tree and the one-line deprecated-events table).

5 / 5

Actionability

Snippets are fully executable and copy-paste ready, with correct/incorrect contrast ("primitive: correct" vs the object-literal "Wrong" case) and concrete selector objects, covering the common cases for hooks, scope accessors, config, and thread operations.

5 / 5

Workflow Clarity

Organization is clear and the Common Gotchas section provides explicit symptom→cause→fix recovery checkpoints, but there is no inline step-by-step setup sequence for building a runtime (construction is delegated to reference files), leaving minor sequence gaps. Not 5 because the top anchor expects an explicitly sequenced multi-step process with validation checkpoints; not 3 because what is presented is complete and unambiguous rather than implicit.

4 / 5

Progressive Disclosure

The body is a true overview: seven one-level-deep references, all verified to exist on disk, each labeled with its content in a References section and cross-linked inline where relevant, plus a Related Skills map for sibling navigation.

5 / 5

Total

19

/

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.

An exemplary description: it states what the skill covers, gives explicit and varied 'use when' triggers including literal error messages, and actively routes away overlapping topics to sibling skills. All four dimensions sit at the top anchors with no vagueness or over-claiming.

DimensionReasoningScore

Specificity

The description lists multiple named concrete capabilities — "creating a runtime (useLocalRuntime with a ChatModelAdapter, useExternalStoreRuntime for Redux or Zustand backed stores, useRemoteThreadListRuntime...)", "wiring AssistantRuntimeProvider", "useAui, useAuiState, and useAuiEvent", and a full adapter list (attachment, speech, dictation, feedback, suggestion, history) — matching the comprehensive-coverage anchor rather than the minor-gaps anchor.

5 / 5

Completeness

It explicitly answers both questions: what ("the state and action layer behind every chat surface") and when ("Use when creating a runtime... wiring AssistantRuntimeProvider, or reading and mutating thread, message, composer, and attachment state"), plus concrete error-routing triggers; the explicit 'Use when' clause satisfies the top anchor.

5 / 5

Trigger Term Quality

It includes the exact natural terms a developer would say: hook names (useLocalRuntime, useExternalStoreRuntime, AssistantRuntimeProvider, useAui), symptoms ("infinite re-render from an object literal selector", "state not updating"), and a verbatim error string ("Cannot read property of undefined"), giving comprehensive trigger coverage.

5 / 5

Distinctiveness Conflict Risk

Clear niche (single-thread runtime state/hooks) with explicit disambiguation against siblings ("For multi-thread list UI use thread-list instead; for toolkit definitions and tool call UI use tools instead"), minimizing conflict risk; third-person voice throughout, so no voice penalty applies.

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 8 suspicious

Warning

Total

15

/

16

Passed

Repository

stevenknowswhy/ProfessionalBuyer

Path

.claude/skills/assistant-ui-runtime/SKILL.md

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.