Back to Skills

design-a2a-agent-card

pjt222
Updated 2 days ago
8 views
17
2
17
View on GitHub
Metadesign

About

This skill generates a standards-compliant A2A Agent Card manifest (`agent.json`) to make your agent discoverable and interoperable within multi-agent systems. It defines the agent's capabilities, skills, authentication, and supported content types as a public contract. Use it when building, migrating, or integrating an agent that must work with other A2A-compliant agents and registries.

Quick Install

Claude Code

Recommended
Primary
npx skills add pjt222/agent-almanac -a claude-code
Plugin CommandAlternative
/plugin add https://github.com/pjt222/agent-almanac
Git CloneAlternative
git clone https://github.com/pjt222/agent-almanac.git ~/.claude/skills/design-a2a-agent-card

Copy and paste this command in Claude Code to install this skill

Documentation

Design A2A Agent Card

Standards-compliant A2A Agent Card → advertises identity, skills, auth, caps for discovery.

Use When

  • Discoverable by other A2A agents
  • Expose caps → multi-agent orchestration
  • Migrate agent → A2A protocol
  • Public contract before impl
  • Integrate → registries

In

  • Required: Agent name + desc
  • Required: Skills list (name, desc, I/O schemas)
  • Required: Base URL host
  • Optional: Auth (none, oauth2, oidc, api-key)
  • Optional: Content types beyond text/plain
  • Optional: Cap flags (streaming, push, state history)
  • Optional: Provider org + URL

Do

Step 1: Identity + desc

1.1. Identity fields:

{
  "name": "data-analysis-agent",
  "description": "Performs statistical analysis, data visualization, and report generation on tabular datasets.",
  "url": "https://agent.example.com",
  "provider": {
    "organization": "Example Corp",
    "url": "https://example.com"
  },
  "version": "1.0.0"
}

1.2. Desc answers:

  • Domains?
  • Tasks?
  • Limitations?

1.3. Canonical URL → /.well-known/agent.json.

→ Complete identity: name, desc, URL, provider, ver.

If err: Multi-domain → one agent w/ many skills vs many focused agents. A2A favors focused w/ clear bounds.

Step 2: Skills + I/O schemas

2.1. Define each:

{
  "skills": [
    {
      "id": "analyze-dataset",
      "name": "Analyze Dataset",
      "description": "Run descriptive statistics, correlation analysis, or hypothesis tests on a CSV dataset.",
      "tags": ["statistics", "data-analysis", "csv"],
      "examples": [
        "Analyze the correlation between columns A and B in my dataset",
        "Run a t-test comparing group 1 and group 2"
      ],
      "inputModes": ["text/plain", "application/json"],
      "outputModes": ["text/plain", "application/json", "image/png"]
    },
    {
      "id": "generate-chart",
      "name": "Generate Chart",
      "description": "Create bar, line, scatter, or histogram charts from tabular data.",
      "tags": ["visualization", "charts"],
      "examples": [
        "Create a scatter plot of height vs weight",
        "Generate a histogram of the age column"
      ],
      "inputModes": ["text/plain", "application/json"],
      "outputModes": ["image/png", "image/svg+xml"]
    }
  ]
}

2.2. Each skill:

  • id: Unique (kebab-case)
  • name: Display
  • description: 1-2 sentences
  • tags: Searchable
  • examples: NL task examples
  • inputModes: MIME accepts
  • outputModes: MIME produces

2.3. Bounds clear + non-overlap. Each task → one skill.

→ Skills array w/ id, name, desc, tags, examples, I/O.

If err: Skills overlap → merge broader w/ more examples. Too broad → split focused.

Step 3: Auth

3.1. Scheme by deploy:

No auth (local/trusted):

{
  "authentication": {
    "schemes": []
  }
}

OAuth 2.0 (rec prod):

{
  "authentication": {
    "schemes": ["oauth2"],
    "credentials": {
      "oauth2": {
        "authorizationUrl": "https://auth.example.com/authorize",
        "tokenUrl": "https://auth.example.com/token",
        "scopes": {
          "agent:invoke": "Invoke agent skills",
          "agent:read": "Read task status"
        }
      }
    }
  }
}

API Key (shared-secret):

{
  "authentication": {
    "schemes": ["apiKey"],
    "credentials": {
      "apiKey": {
        "headerName": "X-API-Key"
      }
    }
  }
}

3.2. Min viable:

  • Local dev → none
  • Internal svc → apiKey
  • Public → oauth2 / oidc

3.3. Doc token/key provisioning → provider section or external docs.

→ Auth block matches deploy sec reqs.

If err: No OAuth infra → start apiKey + plan migration. NEVER public w/ none.

Step 4: Caps

4.1. Protocol features:

{
  "capabilities": {
    "streaming": true,
    "pushNotifications": false,
    "stateTransitionHistory": true
  }
}

4.2. Flags by impl:

  • streaming: true if SSE via tasks/sendSubscribe. Real-time progress.
  • pushNotifications: true if webhook callbacks on state. Requires store + call webhooks.
  • stateTransitionHistory: true if full history (submitted, working, completed). Audit.

4.3. Only true if fully supported. Advertising unsupported → breaks interop.

→ Caps obj w/ flags matching impl.

If err: Unsure → false. Add in future. Removing = breaking change.

Step 5: Validate + publish

5.1. Assemble:

{
  "name": "data-analysis-agent",
  "description": "Performs statistical analysis and visualization on tabular datasets.",
  "url": "https://agent.example.com",
  "version": "1.0.0",
  "provider": {
    "organization": "Example Corp",
    "url": "https://example.com"
  },
  "authentication": {
    "schemes": ["oauth2"],
    "credentials": { ... }
  },
  "capabilities": {
    "streaming": true,
    "pushNotifications": false,
    "stateTransitionHistory": true
  },
  "skills": [ ... ],
  "defaultInputModes": ["text/plain"],
  "defaultOutputModes": ["text/plain"]
}

5.2. Validate:

  • Parse JSON, no syntax errs
  • Required fields (name, desc, url, skills)
  • Each skill: id, name, desc, ≥1 I/O mode
  • URL reachable, card at /.well-known/agent.json

5.3. Publish:

  • Serve → https://<agent-url>/.well-known/agent.json
  • Content-Type: application/json
  • CORS if cross-origin
  • Register → agent directories

5.4. Test discovery:

curl -s https://agent.example.com/.well-known/agent.json | python3 -m json.tool

→ Valid JSON served at well-known URL, parseable by A2A client.

If err: JSON fail → lint. URL unreachable → DNS, SSL, web server. CORS → Access-Control-Allow-Origin.

Check

  • Valid JSON, no syntax errs
  • Required: name, desc, url, skills
  • Each skill: id, name, desc, inputModes, outputModes
  • Auth matches deploy sec
  • Caps reflect impl
  • Served at /.well-known/agent.json + Content-Type
  • A2A clients fetch + parse OK
  • Examples realistic + trigger correct skill

Traps

  • Overpromising caps: streaming: true / pushNotifications: true w/o impl → client fails. Conservative.
  • Vague skill desc: "does data stuff" → no match. Specific I/O + domains.
  • Missing CORS: Browser A2A clients can't fetch w/o CORS.
  • Skill overlap: 2 skills same task → clients can't pick. Clear bounds.
  • Forget default modes: Missing defaultInputModes/defaultOutputModes → clients no MIME.
  • Ver stagnation: Update ver when skills/caps change. Clients cache.
  • Publish before impl: Card = contract. Publishing un-impl'd → runtime fails.

  • implement-a2a-server — server behind card
  • test-a2a-interop — validate conformance + interop
  • build-custom-mcp-server — MCP alt/complement
  • configure-mcp-server — MCP patterns applicable

GitHub Repository

pjt222/agent-almanac
Path: i18n/caveman-ultra/skills/design-a2a-agent-card
0
agentsagentskillsai-assisted-developmentclaude-codeskillsteams

Related Skills

content-collections

Meta

This skill provides a production-tested setup for Content Collections, a TypeScript-first tool that transforms Markdown/MDX files into type-safe data collections with Zod validation. Use it when building blogs, documentation sites, or content-heavy Vite + React applications to ensure type safety and automatic content validation. It covers everything from Vite plugin configuration and MDX compilation to deployment optimization and schema validation.

View skill

polymarket

Meta

This skill enables developers to build applications with the Polymarket prediction markets platform, including API integration for trading and market data. It also provides real-time data streaming via WebSocket to monitor live trades and market activity. Use it for implementing trading strategies or creating tools that process live market updates.

View skill

creating-opencode-plugins

Meta

This skill helps developers create OpenCode plugins that hook into 25+ event types like commands, files, and LSP operations. It provides the plugin structure, event API specifications, and implementation patterns for JavaScript/TypeScript modules. Use it when you need to intercept, monitor, or extend the OpenCode AI assistant's lifecycle with custom event-driven logic.

View skill

sglang

Meta

SGLang is a high-performance LLM serving framework that specializes in fast, structured generation for JSON, regex, and agentic workflows using its RadixAttention prefix caching. It delivers significantly faster inference, especially for tasks with repeated prefixes, making it ideal for complex, structured outputs and multi-turn conversations. Choose SGLang over alternatives like vLLM when you need constrained decoding or are building applications with extensive prefix sharing.

View skill