← ClaudeAtlas

agent-protocol-interoperability-reviewlisted

Review interoperability across agent, tool, and service protocols using exact versions, discovery records, schemas, identity, authorization, delegation, streaming, errors, retries, idempotency, cancellation, and trust zones. Use for A2A, MCP, or another agent-facing protocol boundary; use api-contract-compatibility-review for an ordinary API change without agent delegation semantics.
JovaniPink/skills · ★ 0 · AI & Automation · score 73
Install: claude install-skill JovaniPink/skills
# Agent Protocol Interoperability Review Review whether independently operated agent components can communicate without losing identity, authority, compatibility, or failure semantics. Read [the protocol boundaries reference](references/protocol-boundaries.md) when comparing two or more protocol surfaces. ## Preconditions Identify the protocols, exact versions, roles, owners, trust zones, transports, discovery mechanisms, authentication, authorization, and decision under review. Obtain schemas and security requirements from current primary specifications and implementation evidence. ## Workflow 1. Map each participant as client, server, agent, tool host, remote agent, gateway, or application. Record which party controls discovery and trust. 2. Pin protocol and implementation versions. Distinguish required specification behavior, optional behavior, extensions, implementation-specific behavior, and normative schemas from rendered or generated convenience artifacts. 3. Trace discovery documents, signature verification, caching and refresh, capability advertisement, schema negotiation, protocol binding selection, content types, task or request identifiers, streaming, artifacts, errors, cancellation, and completion. 4. Trace end-user identity, service identity, delegated authority, credentials, consent, and tenant context across every hop. Reject ambient or silently expanded authority. 5. Review argument and output validation, content injection, URL fetching, redirects, SSRF,