agentleFS
fmindfmind/dot/skills/agent-protocols/SKILL.md

agent-protocols

Skill13 starsChanged 4 days agoMITView on GitHub

Implement A2A agents, MCP servers, and ACP editor integrations in Python.

4 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read only the needed guide: read only the A2A, MCP, or ACP guide needed below.

    line 19

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Agent Protocols

Connect agents and tools through the protocol required by the peers. A2A exchanges agent tasks, MCP exposes tools and context, and ACP connects agent clients such as editors to agents; these protocols are not interchangeable.

Workflow

  1. Read only the needed guide: read only the A2A, MCP, or ACP guide needed below. Use mcp-setup for registering an existing MCP server in a host; registration is separate from implementing a client or server.
  2. Vet vendor skills through policy: take vendor skills only from each guide's official-skill guidance, reviewed through the vendor policy and installed project-scoped. A protocol capability named skill is not an installable Agent Skill.

Task guides

<!-- guides:start -->
  • a2a: A2A clients, servers, Agent Cards, task lifecycle, and official guidance.
  • acp: ACP editor-agent sessions, capability negotiation, streamed updates, and permission handling.
  • mcp: MCP tool and context clients/servers, transports, schemas, and protocol tests.
<!-- guides:end -->

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.