// Query XMTP documentation for current SDK patterns, methods, and examples. Use when: (1) Looking up XMTP SDK methods or patterns, (2) Verifying current API signatures before coding, (3) Finding examples for XMTP features like streaming, consent, groups, or content types.
Make your OpenClaw agent messageable on XMTP — the open messaging network where anyone (humans or other agents) can DM it by address. Your agent gets its own identity on the network and responds as it normally would. Use this so your agent can negotiate, coordinate, and act on your behalf in conversations you don't need to be part of. Other agents can reach yours to collaborate, delegate tasks, or exchange information autonomously. Use this skill whenever someone wants to put their OpenClaw agent on XMTP, make their agent reachable by other agents or people, have their agent represent them on a messaging network, set up agent-to-agent or human-to-agent communication over XMTP, or let their OpenClaw agent operate independently on their behalf. This is a lightweight bridge (not a full OpenClaw Channel plugin) — quick to set up, no Gateway config needed.
Connect a running agent (OpenClaw, Claude Code, LangChain, custom Python, any agent runtime) to XMTP messaging so people can DM it and get responses that use the agent's full capabilities — tools, memory, session context. Provides the complete bridge pattern: XMTP CLI setup, identity registration, streaming incoming messages, routing through your agent backend, and sending replies back. Use this skill whenever someone wants to make their agent reachable over XMTP, write a bridge or listener script between an agent process and XMTP, set up xmtp init and stream-all-messages for an agent, have their agent respond to XMTP conversations continuously, wire any agent runtime to the XMTP open messaging network, or pipe XMTP messages through stdin/stdout to an agent process. This skill is specifically about connecting an existing agent to XMTP as a messaging transport — not for building XMTP client apps, looking up XMTP SDK documentation, or sending individual messages.
| name | xmtp-docs |
| description | Query XMTP documentation for current SDK patterns, methods, and examples. Use when: (1) Looking up XMTP SDK methods or patterns, (2) Verifying current API signatures before coding, (3) Finding examples for XMTP features like streaming, consent, groups, or content types. |
Query current XMTP documentation to find accurate SDK patterns before writing code.
CRITICAL: Never use training data for XMTP SDK methods. The SDK evolves frequently and method names change between versions. All method names, signatures, and patterns MUST be looked up from current documentation.
Use the docs index to find which page has what you need:
WebFetch({
url: "https://docs.xmtp.org/llms.txt",
prompt: "Find the page URL for [topic]"
})
Fetch the specific page for complete code examples:
WebFetch({
url: "https://docs.xmtp.org[path-from-step-1]",
prompt: "Extract [specific feature] with code examples"
})
Find how to create a client:
WebFetch({ url: "https://docs.xmtp.org/llms.txt", prompt: "Find the page URL for creating an XMTP client" })
// Returns: /chat-apps/core-messaging/create-a-client
WebFetch({ url: "https://docs.xmtp.org/chat-apps/core-messaging/create-a-client", prompt: "Extract how to create a client with code examples" })
Find how to stream messages:
WebFetch({ url: "https://docs.xmtp.org/llms.txt", prompt: "Find the page URL for streaming messages" })
// Returns: /chat-apps/list-stream-sync/stream
WebFetch({ url: "https://docs.xmtp.org/chat-apps/list-stream-sync/stream", prompt: "Extract streaming patterns with code examples" })