CtrlK
BlogDocsLog inGet started
Tessl Logo

ag-ui-a2ui-integration

Use when adding A2UI rendering to any AG-UI-supported framework or custom AG-UI application, scaffolding an AG-UI app that should render A2UI, adapting an AG-UI integration to emit A2UI surfaces, or wiring the AG-UI A2UI middleware/toolkit with a compatible renderer.

65

Quality

78%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/ag-ui-a2ui-integration/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%

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

A well-organized, AG-UI-first integration guide with clear sequencing and excellent progressive disclosure into real reference files. Its main weakness is the absence of executable code or in-body validation feedback loops, which leaves the otherwise concrete guidance short of copy-paste readiness.

Suggestions

Add at least one minimal executable snippet per mode — e.g. a runtime A2UIMiddleware instantiation and an agent.use(new A2UIMiddleware(...)) example — so the wiring guidance is copy-paste ready rather than identifier-naming only.

Inline a short validate→fix→retry loop (or a checklist drawn from verification.md) so the verification checkpoint in the Workflow is explicit rather than deferred to a reference.

Tighten the Overview and the CLI-flags caveats (e.g. collapse 'The table is a quick reference for known scaffold paths, not the full AG-UI support matrix. Do not invent flags.' into a single line) to reduce prose without losing the guardrail.

DimensionReasoningScore

Conciseness

Largely efficient and free of basic-concept padding, but the Overview layering framing and several caveat sentences ('The table is a quick reference... not the full AG-UI support matrix. Do not invent flags.') could be tightened without losing meaning.

2 / 3

Actionability

Names concrete identifiers and flags (createSurface, generate_a2ui, A2UIMiddleware, a2ui={{ catalog }}, --langgraph-py) but provides no executable code blocks or copy-paste wiring snippets, leaving a developer-facing skill without runnable examples.

2 / 3

Workflow Clarity

The six numbered steps are clearly sequenced with an explicit verification step (step 6), but the validate→fix→retry feedback loop is deferred to verification.md rather than stated inline, leaving checkpoints implicit in the body.

2 / 3

Progressive Disclosure

A concise overview points to three real, one-level-deep reference files (framework-adapters.md, a2ui-runtime-and-renderer.md, verification.md) plus sources.md, all of which exist and are clearly signaled in both the Workflow and a References section.

3 / 3

Total

9

/

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 precise, third-person description with an explicit 'Use when' trigger and several concrete, distinguishable actions tightly scoped to the AG-UI/A2UI integration niche. It avoids vague fluff and over-claims entirely.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'adding A2UI rendering', 'scaffolding an AG-UI app', 'adapting an AG-UI integration to emit A2UI surfaces', 'wiring the AG-UI A2UI middleware/toolkit with a compatible renderer' — matching the multiple-specific-actions anchor.

3 / 3

Completeness

An explicit 'Use when...' clause states when to invoke it, and the enumerated actions state what it does, satisfying both halves with explicit triggers.

3 / 3

Trigger Term Quality

Covers the natural domain terms a developer would actually say — 'A2UI rendering', 'AG-UI app', 'AG-UI integration', 'A2UI surfaces', 'A2UI middleware' — across several triggering scenarios, which are the genuine vocabulary for this niche.

3 / 3

Distinctiveness Conflict Risk

The narrow AG-UI-plus-A2UI integration niche with highly specific triggers makes it unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
ag-ui-protocol/ag-ui
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.