CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

88%

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

81%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 integration skill: the body stays a lean, concrete overview (packages, flags, versions, rules) while executable code lives in three substantive one-level-deep references, and the workflow is explicitly sequenced with a dedicated verification checklist and failure-modes table. The main defects are a paragraph of non-task meta-commentary, no complete inline code example for the common case, and a dangling reference to a missing sources.md file.

Suggestions

Delete the meta paragraph about being a "developer-facing skill artifact... not published as a docs page" — it addresses how the skill is consumed, not how to execute the task, and adds tokens without guidance (conciseness).

Remove the "sources.md" entry from the References section or actually ship the file — the path does not exist in the bundle, so following the link fails (progressive_disclosure).

Inline one minimal end-to-end snippet (e.g., server middleware registration plus client provider/catalog setup for the CopilotKit path) so the most common wiring is copy-paste ready without opening a reference file (actionability).

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence throughout (no library tutorials, no concept explanations), but the meta paragraph "This is a developer-facing skill artifact. It is meant to be loaded by coding agents and used against a real app or repo, not published as a docs page" is non-task padding, and a few defensive hedges ("not the full AG-UI support matrix") could be trimmed. Not 5 because that paragraph's tokens do not earn their place; well above the verbose anchors.

4 / 5

Actionability

Concrete guidance throughout: named packages ("@ag-ui/a2ui-middleware", "@ag-ui/a2ui-toolkit"), a CLI flags table tied to a source file path, config props ("a2ui={{ catalog }}"), a version pin ("CopilotKit >= 1.61.2"), and API fragments ("agent.use(new A2UIMiddleware(...))"). Not 5 because the body itself contains fragments rather than a complete copy-paste example for the common case; full executable code is deferred to the reference files (which do contain real code blocks), so this sits at "concrete code or commands with minor gaps".

4 / 5

Workflow Clarity

The Workflow section gives six clearly sequenced steps with an explicit decision point before editing code ("Decide the A2UI mode before editing code: Fixed schema... Dynamic schema..."), and step 6 is an explicit validation step enumerating four confirmations (AG-UI stream, a2ui-surface activity snapshots or a2ui_operations, rendered surface, user action flowing back). references/verification.md supplies static and runtime checklists plus a symptom-likely cause-fix failure-modes table for error recovery. No destructive or batch operations, so no cap applies; no validation gaps found to justify the 4 anchor.

5 / 5

Progressive Disclosure

Good two-layer structure: the body is an overview, and three real one-level-deep reference files (references/framework-adapters.md, references/a2ui-runtime-and-renderer.md, references/verification.md) are cited inline at the exact workflow steps where they are needed and again in a References section. Not 5 because the References section also lists "sources.md - source files and docs used by this skill", which does not exist anywhere in the bundle — a dangling pointer that breaks navigation. Not 3 because the split, signaling, and organization are otherwise strong.

4 / 5

Total

17

/

20

Passed

Description

92%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 excellent: third-person, highly specific, and trigger-rich, enumerating four concrete integration actions that double as explicit "Use when" triggers in a well-defined AG-UI + A2UI niche. Its only weakness is modest keyword breadth — the natural framework names users might say are absent.

DimensionReasoningScore

Specificity

The description lists four distinct concrete actions — "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", and "wiring the AG-UI A2UI middleware/toolkit with a compatible renderer" — covering create, scaffold, adapt, and wire comprehensively. Matches the 5 anchor; not 4 because no coverage gap is apparent among the skill's stated scenarios.

5 / 5

Completeness

It opens with an explicit "Use when..." clause listing four concrete trigger scenarios, and the gerund actions (adding, scaffolding, adapting, wiring) explicitly state what the skill does, so both what and when are clearly answered with concrete trigger phrases. Not 4 because the when is already highly explicit and specific — the 4 anchor's caveat ("'when' could be more explicit or specific") does not apply.

5 / 5

Trigger Term Quality

Good natural-term coverage: "A2UI rendering", "AG-UI app", "A2UI surfaces", "middleware/toolkit", "renderer", with useful variations ("AG-UI-supported framework", "custom AG-UI application", "AG-UI integration"). Not 5 because it omits the specific framework names (LangGraph, CrewAI, Mastra, CopilotKit) that users of this domain would naturally mention, fitting "good keyword coverage; a few natural terms missing".

4 / 5

Distinctiveness Conflict Risk

A clear dual-term niche — both AG-UI (transport) and A2UI (UI payload) must be in play for the description to trigger — with distinct triggers and minimal overlap with generic frontend, CopilotKit-only, or AG-UI-protocol-only skills. Matches the 5 anchor's "clear niche with distinct triggers".

5 / 5

Total

19

/

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

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

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.