Use when designing agent communication languages.
Scanned 9/10/2026
Install to Claude Code
npx -y skills add LoopyLuci/Skills --skill agent-communication-languages --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Agent Communication Languages?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/loopyluci-agent-communication-languages)More formats (shields.io, HTML) on the badges page.
---
name: agent-communication-languages
description: "Use when designing agent communication languages."
version: 1.0.0
author: Hermes Agent
license: MIT
metadata:
hermes:
tags: [agent-communication, ACL, FIPA, speech-acts, agent-protocols]
related_skills: [swarm-communication-protocols, multi-agent-collaboration-patterns, tool-augmented-agents, agent-framework-design]
---
# Agent Communication Languages
Designing agent communication languages and protocols — from FIPA ACL through structured messaging, ontologies, and protocol negotiation.
## When to Use
- Designing how agents communicate in multi-agent systems
- Defining message schemas and interaction protocols
- Implementing agent conversation policies
- Creating agent negotiation protocols
## Communication Framework
```python
class AgentMessage:
"""FIPA ACL-style agent message."""
def __init__(self, sender: str, receiver: str, performative: str,
content: dict, ontology: str = ''):
self.sender = sender
self.receiver = receiver
self.performative = performative
self.content = content
self.conversation_id = str(uuid.uuid4())
self.timestamp = datetime.now().isoformat()
PERFORMATIVES = ['inform', 'query', 'request', 'propose', 'accept', 'reject', 'cfp']
```
## Common Pitfalls
1. **Over-complex schemas** — 50-field messages obscure intent; keep it simple
2. **No ontology** — agents using different terms for the same concept
3. **Synchronous only** — design async by default; don't block on responses
4. **No conversation state** — multi-turn interactions need context tracking
## Verification Checklist
- [ ] Message schema defined (sender, receiver, performative, content)
- [ ] Core performatives defined
- [ ] Conversation IDs for multi-turn interactions
- [ ] Async communication support
- [ ] Ontology documented (shared vocabulary)
- [ ] Timeout handling for unanswered messages
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!