Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Set up and operate dual Discord bots on one machine with isolated memory, channel allowlists, mention-gated reviewer bot behavior, optional one-way reviewer-...
Set up and operate dual Discord bots on one machine with isolated memory, channel allowlists, mention-gated reviewer bot behavior, optional one-way reviewer-...
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.
Use placeholders only. Never store real secrets in this skill.
BOT_A_NAME BOT_B_NAME BOT_A_TOKEN BOT_B_TOKEN BOT_A_ID BOT_B_ID GUILD_ID CHANNEL_ID_LIST (comma-separated) BASE_DIR (example: ~/.openclaw/bots)
Create isolated workspaces for bot-a and bot-b. Write .env files from template using placeholders. Apply channel allowlist policy: Bot-A: primary chat policy Bot-B: requireMention=true on allowlisted channels Optional: enable one-way bridge (bot-b -> bot-a) for reviewer feedback. Create backup snapshot before each risky iteration. If behavior regresses, rollback snapshot and restart both gateways.
Run: scripts/init_dual_bot.sh
Run: scripts/apply_policy.sh
Run: scripts/backup_state.sh
Run: scripts/rollback_state.sh <BACKUP_DIR>
Keep BOT_B_TOKEN separate from BOT_A_TOKEN. Keep bot-b mention-gated in group channels. Never enable bidirectional auto-bridge (avoids reply loops). Always backup before patching runtime files.
Messaging, meetings, inboxes, CRM, and teammate communication surfaces.
Largest current source with strong distribution and engagement signals.