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.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

75%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 developer-facing skill with a clear workflow, real reference files, and concrete actionable pointers. The main gap is the dangling sources.md reference and validation details being delegated rather than surfaced inline.

Suggestions

Create or remove the dangling `sources.md` reference listed at the end of the References section, since the file is not present in the bundle.

Surface one or two concrete validation checkpoints inline in the Workflow (e.g. the AG-UI stream/RUN_FINISHED check) rather than fully delegating to references/verification.md.

Tighten the Overview and 'AG-UI Framework Support' prose to cut remaining explanatory sentences that restate what the reference files already cover.

Dimension	Reasoning	Score
Conciseness	Mostly lean and well-organized with no padding about what AG-UI/A2UI conceptually are; the CLI flag table and Key Rules are efficient, though the Overview and Framework Support sections carry a little explanatory prose that could be trimmed.	4 / 5
Actionability	Provides concrete, executable pointers—named packages, specific CLI flags, code-shaped snippets (agent.use(new A2UIMiddleware(...)), a2ui={{ catalog }})—and an explicit verification reference, though most code detail lives in references rather than inline copy-paste blocks.	4 / 5
Workflow Clarity	The six-step Workflow is clearly sequenced with a decision point (fixed vs dynamic schema) and a final verification step pointing to references/verification.md; however validation checkpoints within steps are mostly delegated to the reference rather than made explicit inline.	4 / 5
Progressive Disclosure	SKILL.md serves as an overview with clearly signaled one-level-deep references (framework-adapters.md, a2ui-runtime-and-renderer.md, verification.md), all of which exist as real files; however it also references sources.md which is not present in the bundle.	4 / 5
	Total	16 / 20 Passed

Description

91%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 with explicit 'Use when' trigger guidance and concrete capabilities tied to named components. Minor room to add a few more natural synonym terms, but otherwise exemplary.

Dimension	Reasoning	Score
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 comprehensive coverage of the integration surface.	5 / 5
Completeness	Opens with an explicit 'Use when...' trigger clause and lists concrete 'what' actions across the same sentence, clearly answering both what the skill does and when Claude should invoke it.	5 / 5
Trigger Term Quality	Uses natural developer phrasing ('adding A2UI rendering', 'scaffolding an AG-UI app', 'emit A2UI surfaces', 'compatible renderer') but lacks file-extension-style synonyms or common variation terms; technical jargon dominates over everyday user vocabulary.	4 / 5
Distinctiveness Conflict Risk	The tightly scoped AG-UI + A2UI intersection with explicit named packages (@ag-ui/a2ui-middleware, A2UI toolkit) carves a clear niche unlikely to trigger for unrelated skills.	5 / 5
	Total	19 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
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
Path: skills/ag-ui-a2ui-integration/SKILL.md
Commit: 821b8c2

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.