agentsclimarketplace
Sign in

Aap

Skill agentapplicationprotocol/skills/aap

Expert knowledge on the Agent Application Protocol (AAP) — spec, concepts, endpoints, schema, tutorials, and resources. Use this skill whenever the user asks about AAP, agent application protocol, how to build an AAP app or agent, AAP endpoints, AAP schema, tool calls, SSE streaming, client-side vs server-side tools, or anything related to connecting applications to agents using AAP. Trigger even if the user just mentions "AAP", "agent protocol", or "application protocol" in passing.From its SKILL.md

Install
npx -y skills add agentapplicationprotocol/skills --skill aap

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

3.9 KB, 762 tokens by cl100k_base, as published. Nobody here has run it

AAP Protocol Skill

Help the user understand and work with the Agent Application Protocol (AAP).

What is AAP

AAP defines how Applications (clients) and Agents (servers) communicate over HTTP + SSE. It's like MCP or USB — a standard connector between M applications and N agents.

  • Application: owns the UI, accepts user input, provides client-side tools
  • Agent: runs the agent loop, manages history, provides server-side tools, handles LLM interaction

Sources — fetch in this order

  1. Live website (preferred, always up to date):

  2. GitHub (fallback if web fetch fails):

    • Pick an unused temp directory (e.g. via mktemp -d)
    • Try SSH first: git clone [email protected]:agentapplicationprotocol/agent-application-protocol.git <tmp_dir>
    • Then HTTPS: git clone https://github.com/agentapplicationprotocol/agent-application-protocol.git <tmp_dir>
    • Docs are in the docs/ directory of the cloned repo

How to answer

  • Fetch the relevant page(s) from the live website first. Only fall back to local files or GitHub if the fetch fails.
  • When answering questions about a specific topic (e.g. endpoints, schema, tool calls), fetch that specific page rather than loading everything.
  • Cite the source URL when quoting spec details.
  • For code examples, match the user's language/framework if known; otherwise use TypeScript.

Key concepts to know

  • Client-side tools: declared by the application in the request body with full JSON schema. Agent emits tool_call events and pauses; application executes and re-submits with results.
  • Server-side tools: declared by the agent in GET /meta. Application references by name only. If trust: true, agent invokes inline and streams result back.
  • Transport: HTTP + SSE (Server-Sent Events). Stateless server — session history stored externally.

Additional resources

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 326,401. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.