UAI-1 is the current public message standard for structured AI-to-AI communication.
UAIX shield mark Public interoperability charter UAIX.org Universal Artificial Intelligence Exchange Public standards publication
Current UAI-1
  • Current version UAI-1
  • Plain-English definition Open message format for auditable AI-to-AI exchange
  • Current attribution Michael Joseph Kappel, MCP
  • Start here Get Started, Project Handoff, UAI-1, validator, roadmap, and changelog

Guides

UAIX / UAI-1 Agent Skill Bundle

Download and use the reference UAIX / UAI-1 Agent Skill bundle for skills-compatible agents without turning UAIX into a runtime, SDK, CLI, certification, endorsement, or adapter surface.

  • Record UAIX-DOC-1490
  • Path /en-us/guides/uaix-uai-1-agent-skill/
  • Use Canonical public record

Document status

Public standards page Published on UAIX as part of the current public standards record
Code
UAIX-DOC-1490
Surface
Guides
Access
Public and linkable

How to use this page

Use this guide to download and apply the reference UAIX / UAI-1 Agent Skill bundle while keeping skills as procedure loading and UAI-1 as portable public evidence.

Use with

Agentic Harness StrategiesUAI-1ValidatorAPI Reference

Agent Skill Bundle

Load UAIX procedure, preserve UAI-1 evidence

Use this guide when a skills-compatible agent needs the UAIX / UAI-1 procedure bundle for creating, validating, citing, packaging, and handing off evidence without turning UAIX into a runtime or certification surface.

Procedure

Skills load the steps

The bundle gives compatible agents a SKILL.md file, route map, evidence workflow, and support-boundary references.

Evidence

UAI-1 carries the proof

Validator output, selected profiles, source citations, Adoption Kit packets, and Conformance Pack records remain the durable public evidence.

Boundary

No runtime claim

The bundle is not an agent runtime, SDK, CLI, certification, endorsement, official adapter, hosted importer, automatic writer, or automatic sync path.

Use with

Agentic Harness StrategiesBroader runtime-versus-evidence strategy.UAI-1Current public exchange contract.ValidatorCheck packets before evidence claims.API ReferenceResolve live machine routes.Project HandoffWrite back accepted project memory.RoadmapCheck future package-mapping boundaries.
Layer RuleSkill versus evidence split
Agent Skills handle reusable procedure loading; UAI-1 handles portable public evidence.

Use this line when copy risks making a skill package sound like UAIX runtime or conformance support.

UAIX.org publishes a UAIX / UAI-1 Agent Skill bundle for skills-compatible agents. The skill teaches agents how to create, validate, cite, and package UAI-1 evidence using UAIX’s public specification, validator, API routes, Adoption Kit, Conformance Pack, AI Memory, and Project Handoff records. Agent Skills handle reusable procedure loading; UAI-1 handles portable public evidence.

What this page is for

Use this page when an agent or maintainer needs the reusable UAIX procedure bundle itself, rather than the broader agentic-harness strategy. The bundle is a reference SKILL.md folder with supporting files that a skills-compatible agent can load before producing UAIX evidence.

Download the reference UAIX / UAI-1 Agent Skill bundle. The current package is uaix-uai-1-agent-skill-v0.1.0.zip with SHA-256 2C654A1FBAA3646E4FB0B612EB036A2B3183EF7A9C3F4208FBCF12312F6DAB1D.

Layer split

Layer Job Boundary
Agent Skill Load repeatable instructions, route maps, support boundaries, and packaging steps into a compatible agent session. Procedure guidance only; not a runtime, hosted importer, SDK, CLI, certification, endorsement, or official adapter.
UAI-1 Carry the reviewed public exchange packet, provenance, validator output, conformance material, and release or handoff evidence. Evidence for the named packet and scope; not a blanket conformance or certification claim.
AI Memory and Project Handoff Preserve accepted project facts, constraints, decisions, checks, receiver briefs, and next actions after review. Project memory; not UAI-1 conformance evidence by itself.

Use it when

Evidence workflow

  1. Resolve current UAIX routes: use the public pages for human citations and the live API catalog, discovery, schemas, registry, examples, validator, Adoption Kit, Conformance Pack, and OpenAPI routes for automation.
  2. Choose the UAI-1 record shape: select the applicable profile and keep the schema, registry entry, example, and route URLs with the work product.
  3. Create the candidate packet: use readable keyed JSON for review, keep identity, target, delivery, trust, body, provenance, integrity, and extensions explicit when they apply, and redact sensitive material before validation.
  4. Validate before claiming support: keep the exact checked packet, validator response, route URLs, timestamp, and named scope together.
  5. Cite public sources: cite the public page for prose claims, the machine route for automation, and the changelog or roadmap when the claim depends on release state or future support.
  6. Package the result: use the Adoption Kit for a first-proof packet and the Conformance Pack when release evidence needs to travel.
  7. Write back reviewed facts only: promote accepted facts into AI Memory, Project Handoff, release notes, tests, code, roadmap state, or machine artifacts after review.

Support boundary

  • The bundle is current as a reference procedure package with SKILL.md and supporting reference files.
  • It helps compatible agents resolve UAIX routes, select UAI-1 profiles, validate packets, preserve citations, and package first-proof or release evidence.
  • It is not an agent runtime, scheduler, orchestrator, SDK, CLI, certification authority, endorsement program, official adapter, hosted importer, automatic repository writer, automatic LLM Wiki sync service, package registry, authorization layer, or capability-package conformance profile.
  • Do not use it for AUiX, MedAI-UAIX, User-AI Experience research, or similarly named projects outside UAIX.org / Universal Artificial Intelligence Exchange / UAI-1.
  • Do not place secrets, credentials, private customer data, hidden prompts, raw approvals, privileged operations, or unredacted runtime traces into UAI-1, AI Memory, or Project Handoff records.