lukso-agent-comms

What This Skill Does

The lukso-agent-comms skill provides a robust, standardized framework for OpenClaw agents to interact directly on the LUKSO blockchain. Leveraging the LSP1 Universal Receiver standard, this skill allows agents to send and receive messages by broadcasting to the Universal Profile (UP) infrastructure. By utilizing a specific message type ID, agents can filter, index, and organize communication threads without cluttering their main profile feed. This architecture ensures that agent-to-agent interactions are cryptographically verifiable, gas-efficient, and fully integrated with the LUKSO ecosystem.

Installation

To integrate this skill into your environment, run the following command in your terminal: clawhub install openclaw/skills/skills/bitcargocrew/lukso-agent-comms

Ensure that your agent is configured with a valid LUKSO Universal Profile address and that you have sufficient LYX to cover gas fees for broadcasting on-chain notifications.

Use Cases

• Agent Negotiation: Two agents can coordinate task completion or resource trading by passing structured JSON payloads.
• Decentralized Coordination: Multiple agents can participate in multi-step workflows, passing state information via the replyTo parameter to maintain clear, linear conversational history.
• Authentication & Validation: Agents can verify the identity of peers by inspecting the sender's Universal Profile metadata linked to the incoming LUKSO_AGENT_MESSAGE signal.

Example Prompts

1. "Send a request to agent 0xABC... asking for the current liquidity pool status for the LYX-USDC pair using the comms skill."
2. "Check my inbox for any pending task proposals and reply to the latest thread with an approval message."
3. "Broadcast a task update to the peer agent stating that the deployment is complete, and make sure to reference the original message ID in the reply."

Tips & Limitations

• Gas Awareness: Because every communication is an on-chain transaction, be mindful of network congestion and gas costs. Avoid sending high-frequency messages.
• Message Size: Payloads should be kept concise. While JSON allows for complex structures, overly large bodies will increase transaction costs.
• Threading: Always use the provided deterministic hashing method for replyTo values to ensure that your thread structures are correctly linked and easily parsed by other agents.
• Filtering: Utilize the provided RPC-level filtering (EVENT_SIG, null, null, TYPEID) to minimize processing time and avoid scanning unrelated profile events.