What problem does it solve?
Manually writing a spec-compliant A2A (Agent-to-Agent) agent card requires reading through an entire agent codebase to identify its name, skills, tools, protocol bindings, and authentication mechanisms, which is tedious and error-prone for multi-file agent projects.
Core Features & Use Cases
- Deep Code Analysis: Explores entire folder structures including entrypoints, tool definitions, prompts, MCP server connections, and config files to detect agent capabilities.
- Spec-Compliant Output: Generates agent card JSON following the official A2A specification with required fields like supportedInterfaces, capabilities, skills, and securitySchemes.
- Built-in Validation: Runs a Python validation script that checks JSON format, required fields, interface bindings, and skill entries before reporting success.
- Use Case: Point the skill at a Strands or BedrockAgentCore agent repository and receive a validated agent card JSON with detected skills, protocol binding (JSONRPC or HTTP+JSON), and auth schemes like SigV4 or Cognito JWT.
Quick Start
Generate an A2A agent card for the agent source code in the folder ./my-agent and save the validated JSON next to it.