src/skills/builtin/messaging-agents/SKILL.md
Send messages to other agents on your server. Use when you need to communicate with, query, or delegate tasks to another agent.
npx skillsauth add letta-ai/letta-code messaging-agentsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
This skill enables you to send messages to other agents on the same Letta server using the thread-safe conversations API.
The target agent CANNOT:
The target agent CAN:
Important: This skill is for communication with other agents, not delegation of local work. The target agent runs in their own environment and cannot interact with your codebase.
Need local access? If you need the target agent to access your local environment (read/write files, run commands), use the Task tool instead to deploy them as a subagent:
Task({
agent_id: "agent-xxx", // Deploy this existing agent
subagent_type: "explore", // "explore" = read-only, "general-purpose" = read-write
prompt: "Look at the code in src/ and tell me about the architecture"
})
This gives the agent access to your codebase while running as a subagent.
If you don't have a specific agent ID, use these skills to find one:
Load the finding-agents skill to search for agents:
letta agents list --query "agent-name"
letta agents list --tags "origin:letta-code"
Load the searching-messages skill to find which agent worked on something:
letta messages search --query "topic" --all-agents
Results include agent_id for each matching message.
letta -p --from-agent $LETTA_AGENT_ID --agent <id> "message text"
Arguments:
| Arg | Required | Description |
|-----|----------|-------------|
| --agent <id> | Yes | Target agent ID to message |
| --from-agent <id> | Yes | Sender agent ID (injects agent-to-agent system reminder) |
| "message text" | Yes | Message body (positional after flags) |
Example:
letta -p --from-agent $LETTA_AGENT_ID \
--agent agent-abc123 \
"What do you know about the authentication system?"
Response:
{
"conversation_id": "conversation-xyz789",
"response": "The authentication system uses JWT tokens...",
"agent_id": "agent-abc123",
"agent_name": "BackendExpert"
}
letta -p --from-agent $LETTA_AGENT_ID --conversation <id> "message text"
Arguments:
| Arg | Required | Description |
|-----|----------|-------------|
| --conversation <id> | Yes | Existing conversation ID |
| --from-agent <id> | Yes | Sender agent ID (injects agent-to-agent system reminder) |
| "message text" | Yes | Follow-up message (positional after flags) |
Example:
letta -p --from-agent $LETTA_AGENT_ID \
--conversation conversation-xyz789 \
"Can you explain more about the token refresh flow?"
searching-messages skill with letta messages list --agent <id> targeting the other agentWhen you send a message, the target agent receives it with a system reminder:
<system-reminder>
This message is from "YourAgentName" (agent ID: agent-xxx), an agent currently running inside the Letta Code CLI (docs.letta.com/letta-code).
The sender will only see the final message you generate (not tool calls or reasoning).
If you need to share detailed information, include it in your response text.
</system-reminder>
This helps the target agent understand the context and format their response appropriately.
tools
Schedules reminders and recurring tasks via the letta cron CLI. Use when the user asks to be reminded of something, wants periodic messages, or needs to manage scheduled tasks.
tools
# Skill Execute a skill within the main conversation When users ask you to perform tasks, check if any of the available skills match. Skills provide specialized capabilities and domain knowledge. When users reference a "slash command" or "/<something>" (e.g., "/commit", "/review-pr"), they are referring to a skill. Use this tool to invoke it. How to invoke: - Use this tool with the skill name and optional arguments - Examples: - `skill: "pdf"` - invoke the pdf skill - `skill: "commit", a
documentation
Guide for working in parallel with other agents. Use when another agent is already working in the same directory, or when you need to work on multiple features simultaneously. Covers git worktrees as the recommended approach.
testing
Manage git-backed memory repos. Load this skill when working with git-backed agent memory, setting up remote memory repos, resolving sync conflicts, or managing memory via git workflows.