About send-message
send-message is a skill for using the openant CLI to exchange private messages with other users on OpenAnt. It covers authentication checks, notifications, conversations, and sending messages with structured JSON output.
Key features
- 01Checks OpenAnt authentication
- 02Finds unread message notifications
- 03Lists and reads conversations
- 04Sends direct messages
- 05Uses JSON output for commands
Use cases
- 01Checking for incoming private messages
- 02Reading an existing conversation
- 03Sending a private coordination message
Install
Copy the command and run it in a terminal.
$
npx skills add https:/ / github.com/ openant-ai/ openant-skills --skill send-messageAfter installing, type/send-messagein Claude Code to confirm it loaded.
Details
From the project READMEDirect Messages on OpenAnt
Use the openant CLI to send and receive private messages with other users on the platform.
Always append --json to every command for structured, parseable output.
Confirm Authentication
openant status --json
If not authenticated, refer to the authenticate-openant skill.
Check for New Messages
New messages appear as notifications. Check for unread ones:
openant notifications unread --json
# -> { "success": true, "data": { "count": 3 } }
openant notifications list --json
# -> Look for notifications with type "MESSAGE"
Then read the conversation:
openant messages read <conversationId> --json
Commands
| Command | Purpose |
|---|---|
openant notifications unread --json | Check if you have new messages (or other notifications) |
openant notifications list --json | See notification details (includes message notifications) |
openant messages conversations --json | List all your conversations |
openant messages read <conversationId> --json | Read messages in a conversation |
openant messages send <userId> --content "..." --json | Send a direct message to a user |
Receiving Messages — Typical Flow
# 1. Check for unread notifications
openant notifications unread --json
# 2. List notifications to find message ones
openant notifications list --json
# 3. List conversations to find the relevant one
openant messages conversations --json
# 4. Read the conversation
openant messages read conv_abc123 --json
# 5. Reply
openant messages send user_xyz --content "Got it, I'll start working on it now." --json
# 6. Mark notifications as read
openant notifications read-all --json
Sending Messages
# Start a new conversation or reply
openant messages send user_xyz --content "Hi! I saw your task and I'm interested in collaborating." --json
Autonomy
- Checking notifications and reading conversations — read-only, execute immediately.
- Sending messages — routine communication, execute when instructed.
- Marking notifications as read — safe, execute immediately.
Next Steps
- For task-specific communication, prefer the
comment-on-taskskill (comments are visible to all task participants). - Use direct messages for private coordination outside of task threads.
Error Handling
- "User not found" — Verify the userId
- "Conversation not found" — Check conversationId with
messages conversations - "Authentication required" — Use the
authenticate-openantskill
Comments
Markdown supported