Agent Council

Complete toolkit for creating and managing autonomous AI agents with Discord integration for OpenClaw.

What This Skill Does

Agent Creation:

• - Creates autonomous AI agents with self-contained workspaces
• Generates SOUL.md (personality & responsibilities)
• Generates HEARTBEAT.md (cron execution logic)
• Sets up memory system (hybrid architecture)
• Configures gateway automatically
• Binds agents to Discord channels (optional)
• Sets up daily memory cron jobs (optional)

Discord Channel Management:

• - Creates Discord channels via API
• Configures OpenClaw gateway allowlists
• Sets channel-specific system prompts
• Renames channels and updates references
• Optional workspace file search

Installation

CODEBLOCK0

Part 1: Agent Creation

Quick Start

CODEBLOCK1

Workflow

1. Gather Requirements

Ask the user:

• - Agent name (e.g., "Watson")
• Agent ID (lowercase, hyphenated, e.g., "watson")
• Emoji (e.g., "🔬")
• Specialty (what the agent does)
• Model (which LLM to use)
• Workspace (where to create agent files)
• Discord channel ID (optional)

2. Run Creation Script

CODEBLOCK2

The script automatically:

• - ✅ Creates workspace with memory subdirectory
• ✅ Generates SOUL.md and HEARTBEAT.md
• ✅ Updates gateway config (preserves existing agents)
• ✅ Adds Discord channel binding (if specified)
• ✅ Restarts gateway to apply changes
• ✅ Prompts for daily memory cron setup

3. Customize Agent

After creation:

• - SOUL.md - Refine personality, responsibilities, boundaries
• HEARTBEAT.md - Add periodic checks and cron logic
• Workspace files - Add agent-specific configuration

Agent Architecture

Self-contained structure:
CODEBLOCK3

Memory system:

• - Agent-specific memory: INLINECODE0
• Shared memory access: Agents can read shared workspace
• Daily updates: Optional cron job for summaries

Cron jobs:
If your agent needs scheduled tasks:

1. 1. Create HEARTBEAT.md with execution logic
2. Add cron jobs with INLINECODE1
3. Document in SOUL.md

Examples

Research agent:
CODEBLOCK4

Image generation agent:
CODEBLOCK5

Health tracking agent:
CODEBLOCK6

Part 2: Discord Channel Management

Channel Creation

Quick Start

CODEBLOCK7

Workflow

1. 1. Run setup script:

1. 2. Apply gateway config (command shown by script):

Options

With category:
CODEBLOCK10

Use existing channel:
CODEBLOCK11

Channel Renaming

Quick Start

CODEBLOCK12

Workflow

1. 1. Run rename script:

1. 2. Apply gateway config if systemPrompt needs updating (shown by script)

1. 3. Commit workspace file changes (if --workspace used)

With Workspace Search

CODEBLOCK14

This will:

• - Rename Discord channel via API
• Update gateway config systemPrompt
• Search and update workspace files
• Report files changed for git commit

Complete Multi-Agent Setup

Full workflow from scratch:

CODEBLOCK15

Configuration

Discord Category ID

Option 1: Command line
CODEBLOCK16

Option 2: Environment variable
CODEBLOCK17

Finding Discord IDs

Enable Developer Mode:

• - Settings → Advanced → Developer Mode

Copy IDs:

• - Right-click channel → Copy ID
• Right-click category → Copy ID

Scripts Reference

create-agent.sh

Arguments:

• - --name (required) - Agent name
• INLINECODE4 (required) - Agent ID (lowercase, hyphenated)
• INLINECODE5 (required) - Agent emoji
• INLINECODE6 (required) - What the agent does
• INLINECODE7 (required) - LLM to use (provider/model-name)
• INLINECODE8 (required) - Where to create agent files
• INLINECODE9 (optional) - Discord channel ID to bind

Output:

• - Creates agent workspace
• Generates SOUL.md and HEARTBEAT.md
• Updates gateway config
• Optionally creates daily memory cron

setup-channel.py

Arguments:

• - --name (required) - Channel name
• INLINECODE11 (required) - Channel purpose/context
• INLINECODE12 (optional) - Existing channel ID
• INLINECODE13 (optional) - Discord category ID

Output:

• - Creates Discord channel (if doesn't exist)
• Generates gateway config.patch command

rename-channel.py

Arguments:

• - --id (required) - Channel ID
• INLINECODE15 (required) - Current channel name
• INLINECODE16 (required) - New channel name
• INLINECODE17 (optional) - Workspace directory to search

Output:

• - Renames Discord channel
• Updates gateway systemPrompt (if needed)
• Lists updated files (if workspace search enabled)

Gateway Integration

This skill integrates with OpenClaw's gateway configuration:

Agents:
CODEBLOCK18

Bindings:
CODEBLOCK19

Channels:
CODEBLOCK20

Agent Coordination

Your main agent coordinates with specialized agents using OpenClaw's built-in session management tools.

List Active Agents

See all active agents and their recent activity:

CODEBLOCK21

Send Messages to Agents

Direct communication:
CODEBLOCK22

Wait for response:
CODEBLOCK23

Spawn Sub-Agent Tasks

For complex work, spawn a sub-agent in an isolated session:

CODEBLOCK24

The sub-agent will:

1. 1. Execute the task in isolation
2. Announce completion back to your session
3. Self-delete (if cleanup: "delete")

Check Agent History

Review what an agent has been working on:

CODEBLOCK25

Coordination Patterns

1. Direct delegation (Discord-bound agents):

• - User messages agent's Discord channel
• Agent responds directly in that channel
• Main agent doesn't need to coordinate

2. Programmatic delegation (main agent → sub-agent):
CODEBLOCK26

3. Spawn for complex tasks:
CODEBLOCK27

4. Agent-to-agent communication:
Agents can send messages to each other:
CODEBLOCK28

Best Practices

When to use Discord bindings:

• - ✅ Domain-specific agents (research, health, images)
• ✅ User wants direct access to agent
• ✅ Agent should respond to channel activity

When to use sessions_send:

• - ✅ Programmatic coordination
• ✅ Main agent delegates to specialists
• ✅ Need response in same session

When to use sessions_spawn:

• - ✅ Long-running tasks (>5 minutes)
• ✅ Complex multi-step work
• ✅ Want isolation from main session
• ✅ Background processing

Example: Research Workflow

CODEBLOCK29

Communication Flow

Main Agent (You) ↔ Specialized Agents:

CODEBLOCK30

Discord-Bound Agents:

CODEBLOCK31

Hybrid Approach:

CODEBLOCK32

Troubleshooting

Agent Creation Issues:

"Agent not appearing in Discord"

• - Verify channel ID is correct
• Check gateway config bindings section
• Restart gateway: INLINECODE19

"Model errors"

• - Verify model name format: INLINECODE20
• Check model is available in gateway config

Channel Management Issues:

"Failed to create channel"

• - Check bot has "Manage Channels" permission
• Verify bot token in OpenClaw config
• Ensure category ID is correct (if specified)

"Category not found"

• - Verify category ID is correct
• Check bot has access to category
• Try without category ID (creates uncategorized)

"Channel already exists"

• - Use --id <channel-id> to configure existing channel
• Or script will auto-detect and configure it

Use Cases

• - Domain specialists - Research, health, finance, coding agents
• Creative agents - Image generation, writing, design
• Task automation - Scheduled monitoring, reports, alerts
• Multi-agent systems - Coordinated team of specialized agents
• Discord organization - Structured channels for different agent domains

Advanced: Multi-Agent Coordination

For larger multi-agent systems:

Coordination Patterns:

• - Main agent delegates tasks to specialists
• Agents report progress and request help
• Shared knowledge base for common information
• Cross-agent communication via INLINECODE22

Task Management:

• - Integrate with task tracking systems
• Route work based on agent specialty
• Track assignments and completions

Documentation:

• - Maintain agent roster in main workspace
• Document delegation patterns
• Keep runbooks for common workflows

Best Practices

1. 1. Organize channels in categories - Group related agent channels
2. Use descriptive channel names - Clear purpose from the name
3. Set specific system prompts - Give each channel clear context
4. Document agent responsibilities - Keep SOUL.md updated
5. Set up memory cron jobs - For agents with ongoing work
6. Test agents individually - Before integrating into team
7. Update gateway config safely - Always use config.patch, never manual edits

Requirements

Bot Permissions:

• - Manage Channels - To create/rename channels
• INLINECODE24 - To read channel list
• INLINECODE25 - To post in channels

System:

• - OpenClaw installed and configured
• Node.js/npm via nvm
• Python 3.6+ (standard library only)
• Discord bot token (for channel management)

See Also

• - OpenClaw documentation: https://docs.openclaw.ai
• Multi-agent patterns: https://docs.openclaw.ai/agents
• Discord bot setup: https://docs.openclaw.ai/channels/discord