skills/ai/SKILL.md
Use when working with AI agent protocols, standards, interoperability specifications, evaluation contracts, synthetic simulation data, improvement pipelines, and agent steering workflows. Covers MCP, A2A, ACP, Agent Skills, AGENTS.md, ADL, Improve, x402, AP2, MCP Apps, cagent, and learn. USE FOR: agent protocol selection, comparing MCP vs A2A vs ACP, understanding agent standards ecosystem, choosing payment protocols, choosing eval standards, choosing improvement techniques, choosing synthetic data simulation techniques, steering from user feedback DO NOT USE FOR: specific protocol, eval, or improvement implementation details (use the sub-skills: mcp, a2a, acp, improve, learn, x402, etc.)
npx skillsauth add Tyler-R-Kendrick/agent-skills aiInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
This skill covers the emerging ecosystem of open standards and protocols for AI agents. These specifications define how agents discover capabilities, communicate with each other, make payments, render UI, and are described declaratively.
| Protocol | Purpose | Maintained By | |----------|---------|---------------| | MCP | Tool integration — how agents use tools and access context | Anthropic | | A2A | Agent-to-agent communication and task delegation | Google | | ACP | REST-based agent communication (merged into A2A) | IBM / BeeAI / Linux Foundation | | Agent Skills | Skill packaging — how capabilities are discovered and loaded | Anthropic | | Improve | Agent and LLM eval contracts, synthetic simulation data, and self-improvement pipelines for prompts, code, skills, agents, harnesses, and workflows | AgentEvals / AgentV / Simula / QDC / GEPA / Trace / VISTA / SkillOpt / Agent Lightning / ResponsibleAI | | AGENTS.md | Project-level guidance for coding agents | Community | | ADL | Declarative agent definition (identity, tools, permissions) | Next Moca / Eclipse LMOS | | x402 | HTTP-native micropayments using stablecoins | Coinbase | | AP2 | Secure agent-driven commerce and purchases | Google | | MCP Apps | Rich interactive UI served by MCP servers | Anthropic | | cagent | Multi-agent runtime with YAML configuration | Docker | | learn | Feedback-to-steering workflow for generalized agent reasoning preferences | Local |
┌─────────────────────────────────────────────┐
│ Agent Definition (ADL, AGENTS.md) │
│ "What the agent is and what it can do" │
├─────────────────────────────────────────────┤
│ Capability Discovery (Agent Skills, MCP) │
│ "How agents find and load tools/skills" │
├─────────────────────────────────────────────┤
│ Agent Communication (A2A, ACP) │
│ "How agents talk to each other" │
├─────────────────────────────────────────────┤
│ Payments (x402, AP2) │
│ "How agents pay for services" │
├─────────────────────────────────────────────┤
│ UI (MCP Apps) │
│ "How agents render interactive interfaces" │
├─────────────────────────────────────────────┤
│ Runtime (cagent) │
│ "How agents are orchestrated and executed" │
└─────────────────────────────────────────────┘
STEERING.md and linked RDF entries.tools
Use when building or maintaining a design system — the coordinated set of design tokens, component libraries, documentation, and tooling that ensures visual and behavioral consistency across products. USE FOR: design system architecture, choosing token formats vs component frameworks, connecting Figma to code, design-to-development workflows, multi-platform consistency DO NOT USE FOR: specific token authoring (use design-tokens), Figma workflows (use figma), component cataloging (use storybook), token transformation (use style-dictionary), cross-framework components (use mitosis)
tools
Use when implementing the x402 protocol for HTTP-native micropayments. Covers server middleware, client payment flows, facilitator integration, and stablecoin payments for APIs and AI agents. USE FOR: API micropayments, monetizing endpoints, stablecoin HTTP payments, automated agent payments for API access DO NOT USE FOR: full commerce flows with cart/checkout (use ap2), agent communication (use a2a), tool integration (use mcp)
tools
Use when implementing or integrating with the Model Context Protocol (MCP) for AI tool servers, resources, prompts, and context management. USE FOR: building MCP tool servers, exposing resources to agents, prompt templates, connecting agents to external APIs DO NOT USE FOR: agent-to-agent communication (use a2a), interactive UI rendering (use mcp-apps), agent payments (use x402 or ap2)
tools
Use when building MCP Apps that serve interactive UI from MCP servers. Covers the ui:// URI scheme, HTML rendering in sandboxed iframes, and bidirectional communication between UI and host. USE FOR: rich UI in agent conversations, interactive dashboards from MCP servers, sandboxed iframe rendering DO NOT USE FOR: basic tool responses without UI (use mcp), agent communication (use a2a), full web applications