{"skill":{"slug":"qqbot-multi-account","displayName":"QQBot Multi-Account","summary":"QQBot 多账号运维排障技能。用于 OpenClaw 多 Bot、多 Agent 场景下的账号绑定检查、重复会话诊断、主动发送与本地插件打包导出。触发词：QQBot多账号、双机器人、双Agent、账号绑定、重复会话、appId隔离。","description":"---\nname: qqbot-multi-account\nslug: qqbot-multi-account\nversion: 1.0.1\nauthor: OpenClaw Community\ndescription: QQBot 多账号运维排障技能。用于 OpenClaw 多 Bot、多 Agent 场景下的账号绑定检查、重复会话诊断、主动发送与本地插件打包导出。触发词：QQBot多账号、双机器人、双Agent、账号绑定、重复会话、appId隔离。\nmetadata:\n  openclaw:\n    emoji: 🤖\n    tags: [qqbot, multi-account, multi-agent, routing, troubleshooting, diagnostics]\n---\n\n# QQBot Multi-Account\n\nA publishable skill for OpenClaw operators who run QQBot in multi-account, multi-agent environments.\n\n## Prerequisite\n\nInstall the QQBot plugin first:\n\n```bash\nopenclaw plugins install @tencent-connect/openclaw-qqbot@latest\n```\n\n## Best for\n\n- `K1 -> main`, `K2 -> agent2` style deployments\n- Diagnosing duplicate sessions caused by cross-account event handling\n- Verifying `bindings`, `accounts`, `appId`, gateway port, and runtime state\n- Sending proactive QQ messages or files through a specific bot account\n- Exporting the local `qqbot` plugin as a portable archive for handoff or backup\n\n## What this skill helps you do\n\n- Understand the minimal config needed for multi-account QQBot routing\n- Check whether bindings and account definitions match the intended agent map\n- Recognize the real root cause of duplicate-session bugs in runtime state\n- Inspect the local OpenClaw + QQBot deployment quickly\n- Package the locally modified plugin for transfer or release workflows\n\n## Minimal config skeleton\n\n```json\n{\n  \"bindings\": [\n    {\n      \"agentId\": \"main\",\n      \"match\": {\n        \"channel\": \"qqbot\",\n        \"accountId\": \"K1\"\n      }\n    },\n    {\n      \"agentId\": \"agent2\",\n      \"match\": {\n        \"channel\": \"qqbot\",\n        \"accountId\": \"K2\"\n      }\n    }\n  ],\n  \"channels\": {\n    \"qqbot\": {\n      \"enabled\": true,\n      \"accounts\": {\n        \"K1\": {\n          \"appId\": \"YOUR_APP_ID_1\",\n          \"clientSecretFile\": \"/path/to/qqbot_k1.secret\",\n          \"name\": \"K1\"\n        },\n        \"K2\": {\n          \"appId\": \"YOUR_APP_ID_2\",\n          \"clientSecretFile\": \"/path/to/qqbot_k2.secret\",\n          \"name\": \"K2\"\n        }\n      }\n    }\n  }\n}\n```\n\n## Critical implementation note\n\nIf one QQ message reaches two agents, do not assume the `bindings` are wrong first. In multi-account deployments, the plugin runtime must isolate account state by `appId`, especially:\n\n- access token cache\n- token singleflight promise\n- background token refresh controller\n\nIf these are global instead of account-scoped, one account can consume another account's event stream and create duplicate sessions.\n\n## Recommended workflow\n\n### 1. Inspect local status\n\n```bash\nbash {baseDir}/scripts/inspect-qqbot.sh\n```\n\n### 2. Review bundled references\n\n- `references/multi-account-routing.md`\n- `references/proactive-send.md`\n\n### 3. Export the local plugin when needed\n\n```bash\nbash {baseDir}/scripts/export-local-qqbot.sh\n```\n\nBy default this writes a portable archive into `{baseDir}/dist/`.\n","tags":{"latest":"1.0.1"},"stats":{"comments":0,"downloads":799,"installsAllTime":30,"installsCurrent":1,"stars":0,"versions":2},"createdAt":1773318198464,"updatedAt":1778998442723},"latestVersion":{"version":"1.0.1","createdAt":1773324383118,"changelog":"Remove README publish tips and add required qqbot plugin prerequisite.","license":"MIT-0"},"metadata":{"setup":[],"os":null,"systems":null},"owner":{"handle":"naluko","userId":"s179xsrt8ezw9jwy6g8q9pwg918848n6","displayName":"Naluko","image":"https://avatars.githubusercontent.com/u/81939781?v=4"},"moderation":null}