agent-card-templates

# Agent Card Templates

**Purpose:** Provide reusable JSON templates for creating A2A (Agent-to-Agent) protocol agent cards following the official specification.

**Activation Triggers:**
- Creating new A2A agent cards
- Implementing agent discovery endpoints
- Configuring authentication schemes
- Defining agent capabilities and skills
- Setting up service endpoints
- Validating agent card JSON structure

**Key Resources:**
- `templates/schema.json` - Complete JSON schema for validation
- `templates/basic-agent-card.json` - Simple agent card template
- `templates/multi-capability-agent-card.json` - Agent with multiple skills
- `templates/authenticated-agent-card.json` - Agent with auth requirements
- `templates/streaming-agent-card.json` - Agent with streaming support
- `examples/` - Real-world agent card examples
- `scripts/validate-agent-card.sh` - Schema validation script
- `scripts/generate-agent-card.sh` - Interactive card generator
- `scripts/test-agent-card.sh` - Format and structure testing

## Security: API Key Handling

**CRITICAL:** When generating any configuration files or code:

❌ NEVER hardcode actual API keys or secrets
❌ NEVER include real credentials in examples
❌ NEVER commit sensitive values to git

✅ ALWAYS use placeholders: `your_service_key_here`
✅ ALWAYS create `.env.example` with placeholders only
✅ ALWAYS add `.env*` to `.gitignore` (except `.env.example`)
✅ ALWAYS read from environment variables in code
✅ ALWAYS document where to obtain keys

**Placeholder format:** `{service}_{env}_your_key_here`

## Agent Card Structure

### Required Fields

**Basic Identity:**
- `id` - Unique identifier (URI or UUID)
- `name` - Human-readable display name
- `protocolVersion` - A2A protocol version (e.g., "0.3")
- `serviceEndpoint` - Base URL for agent's A2A service
- `provider` - Organization information (name, contactEmail, url)

**Security:**
- `securitySchemes` - Authentication scheme definitions
- `security` - Required auth combinations

**Capabilit