Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Connect OpenClaw to OneBot protocol for QQ bot integration. Use when receiving or sending QQ messages via NapCat or other OneBot servers.
Connect OpenClaw to OneBot protocol for QQ bot integration. Use when receiving or sending QQ messages via NapCat or other OneBot servers.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Connect OpenClaw to OneBot protocol servers like NapCat for QQ bot functionality.
Set OneBot server URL in environment or config: export ONEBOT_WS_URL="ws://127.0.0.1:3001" export ONEBOT_HTTP_URL="http://127.0.0.1:3000" export ONEBOT_TOKEN="your-token"
Use the WebSocket listener script to receive QQ messages: python scripts/onebot_ws_listener.py
Use HTTP API to send messages: from scripts.onebot_client import OneBotClient client = OneBotClient() client.send_private_msg(user_id=123456, message="Hello!") client.send_group_msg(group_id=789012, message="Group message")
Real-time bidirectional communication Receives events instantly Supports both sending and receiving
Request-response model Good for simple sending Requires polling for receiving
client.get_login_info()
client.get_friend_list() client.get_group_list()
See references/message-handling.md for message parsing and response patterns.
NapCat is a OneBot11 implementation based on NTQQ. Default ports: WebSocket: 3001 HTTP: 3000 WebUI: 6099 Token authentication is optional but recommended for public deployments.
Connection refused: Check if OneBot server is running and ports are correct. Authentication failed: Verify token matches OneBot server configuration. Message not delivered: Check user_id/group_id exists and bot has permission.
Messaging, meetings, inboxes, CRM, and teammate communication surfaces.
Largest current source with strong distribution and engagement signals.