Agent skill

Agent Council

by LeoYeAI in LeoYeAI/openclaw-master-skills

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

MITAuto-check passedAgent Workflows

Install Agent Council

skills CLI
$ npx skills add LeoYeAI/openclaw-master-skills --skill agent-council -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install LeoYeAI/openclaw-master-skills agent-council --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/agent-council .claude/skills/agent-council && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
agent-council
GitHub stars
2.2k
Token cost
~4.1k tokens
SKILL.md length
1,027 words
Files
6 (incl. scripts)
Skills in repo
1,235
Repo updated
First seen
Licence
MIT

At a glance

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

  • Works in 3 steps: Gather Requirements → Run Creation Script → Customize Agent
  • Setting up multi-agent systems
  • SKILL.md covers What This Skill Does, Installation, Part 1: Agent Creation and Part 2: Discord Channel…, plus 6 more sections
  • Runs Python and Shell scripts from its folder; calls python3

What it does

Agent Council is an agent skill from LeoYeAI/openclaw-master-skills. Complete toolkit for creating autonomous AI agents and managing Discord channels for OpenClaw. Use when setting up multi-agent systems, creating new agents, or managing Discord channel organization.

Its SKILL.md is about 4.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including scripts (for example `README.md`, `_meta.json` and `scripts/create-agent.sh`).

It sits in Agent Workflows, covering Multi-agent orchestration. It works with Discord. The repository describes itself as: 🧠 Curated collection of 1209+ best OpenClaw skills — weekly updated by MyClaw.ai. The licence is MIT.

When your agent uses it

  • Setting up multi-agent systems
  • Creating new agents
  • Managing Discord channel organization

Example prompts

  • “/agent-council”

Requirements

  • Python 3
  • A Bash shell

Workflow steps

3 steps, taken from the step headings in SKILL.md.

  1. Gather Requirements
  2. Run Creation Script
  3. Customize Agent

What it can do on your machine

Read from SKILL.md and the folder at commit e5199b5. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 3 files in scripts/ (Python and Shell), which the agent can run.

    Shell commands in SKILL.md call:

    • python3

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • docs.openclaw.ai

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Agent Council loads about 4.1k tokens when it runs. Until then it costs about 53 tokens; SKILL.md has 1,027 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~53
When it runs · the whole SKILL.md, loaded when a task matches
~4.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from LeoYeAI/openclaw-master-skills at commit e5199b5, republished under its MIT licence (© LeoYeAI). 1,027 words, ~4,137 tokens.

Download SKILL.mdSave it as .claude/skills/agent-council/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.
name
agent-council
description
Complete toolkit for creating autonomous AI agents and managing Discord channels for OpenClaw. Use when setting up multi-agent systems, creating new agents, or managing Discord channel organization.

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

bash
# Install from ClawHub
clawhub install agent-council

# Or manual install
cp -r . ~/.openclaw/skills/agent-council/
openclaw gateway config.patch --raw '{
  "skills": {
    "entries": {
      "agent-council": {"enabled": true}
    }
  }
}'

Part 1: Agent Creation

Quick Start
bash
scripts/create-agent.sh \
  --name "Watson" \
  --id "watson" \
  --emoji "🔬" \
  --specialty "Research and analysis specialist" \
  --model "anthropic/claude-opus-4-5" \
  --workspace "$HOME/agents/watson" \
  --discord-channel "1234567890"
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
bash
scripts/create-agent.sh \
  --name "Agent Name" \
  --id "agent-id" \
  --emoji "🤖" \
  --specialty "What this agent does" \
  --model "provider/model-name" \
  --workspace "/path/to/workspace" \
  --discord-channel "1234567890"  # Optional

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:

agents/
├── watson/
│   ├── SOUL.md              # Personality and responsibilities
│   ├── HEARTBEAT.md         # Cron execution logic
│   ├── memory/              # Agent-specific memory
│   │   ├── 2026-02-01.md   # Daily memory logs
│   │   └── 2026-02-02.md
│   └── .openclaw/
│       └── skills/          # Agent-specific skills (optional)

Memory system:

  • Agent-specific memory: <workspace>/memory/YYYY-MM-DD.md
  • Shared memory access: Agents can read shared workspace
  • Daily updates: Optional cron job for summaries

Cron jobs: If your agent needs scheduled tasks:

  1. Create HEARTBEAT.md with execution logic
  2. Add cron jobs with --session <agent-id>
  3. Document in SOUL.md
Examples

Research agent:

bash
scripts/create-agent.sh \
  --name "Watson" \
  --id "watson" \
  --emoji "🔬" \
  --specialty "Deep research and competitive analysis" \
  --model "anthropic/claude-opus-4-5" \
  --workspace "$HOME/agents/watson" \
  --discord-channel "1234567890"

Image generation agent:

bash
scripts/create-agent.sh \
  --name "Picasso" \
  --id "picasso" \
  --emoji "🎨" \
  --specialty "Image generation and editing specialist" \
  --model "google/gemini-3-flash-preview" \
  --workspace "$HOME/agents/picasso" \
  --discord-channel "9876543210"

Health tracking agent:

bash
scripts/create-agent.sh \
  --name "Nurse Joy" \
  --id "nurse-joy" \
  --emoji "💊" \
  --specialty "Health tracking and wellness monitoring" \
  --model "anthropic/claude-opus-4-5" \
  --workspace "$HOME/agents/nurse-joy" \
  --discord-channel "5555555555"

Part 2: Discord Channel Management

Channel Creation
Quick Start
bash
python3 scripts/setup-channel.py \
  --name research \
  --context "Deep research and competitive analysis"
Workflow
  1. Run setup script:
bash
python3 scripts/setup-channel.py \
  --name <channel-name> \
  --context "<channel-purpose>" \
  [--category-id <discord-category-id>]
  1. Apply gateway config (command shown by script):
bash
openclaw gateway config.patch --raw '{"channels": {...}}'
Options

With category:

bash
python3 scripts/setup-channel.py \
  --name research \
  --context "Deep research and competitive analysis" \
  --category-id "1234567890"

Use existing channel:

bash
python3 scripts/setup-channel.py \
  --name personal-finance \
  --id 1466184336901537897 \
  --context "Personal finance management"
Channel Renaming
Quick Start
bash
python3 scripts/rename-channel.py \
  --id 1234567890 \
  --old-name old-name \
  --new-name new-name
Workflow
  1. Run rename script:
bash
python3 scripts/rename-channel.py \
  --id <channel-id> \
  --old-name <old-name> \
  --new-name <new-name> \
  [--workspace <workspace-dir>]
  1. Apply gateway config if systemPrompt needs updating (shown by script)

  2. Commit workspace file changes (if --workspace used)

bash
python3 scripts/rename-channel.py \
  --id 1234567890 \
  --old-name old-name \
  --new-name new-name \
  --workspace "$HOME/my-workspace"

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:

bash
# 1. Create Discord channel
python3 scripts/setup-channel.py \
  --name research \
  --context "Deep research and competitive analysis" \
  --category-id "1234567890"

# (Note the channel ID from output)

# 2. Apply gateway config for channel
openclaw gateway config.patch --raw '{"channels": {...}}'

# 3. Create agent bound to that channel
scripts/create-agent.sh \
  --name "Watson" \
  --id "watson" \
  --emoji "🔬" \
  --specialty "Deep research and competitive analysis" \
  --model "anthropic/claude-opus-4-5" \
  --workspace "$HOME/agents/watson" \
  --discord-channel "1234567890"

# Done! Agent is created and bound to the channel

Configuration

Discord Category ID

Option 1: Command line

bash
python3 scripts/setup-channel.py \
  --name channel-name \
  --context "Purpose" \
  --category-id "1234567890"

Option 2: Environment variable

bash
export DISCORD_CATEGORY_ID="1234567890"
python3 scripts/setup-channel.py --name channel-name --context "Purpose"
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
  • --id (required) - Agent ID (lowercase, hyphenated)
  • --emoji (required) - Agent emoji
  • --specialty (required) - What the agent does
  • --model (required) - LLM to use (provider/model-name)
  • --workspace (required) - Where to create agent files
  • --discord-channel (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
  • --context (required) - Channel purpose/context
  • --id (optional) - Existing channel ID
  • --category-id (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
  • --old-name (required) - Current channel name
  • --new-name (required) - New channel name
  • --workspace (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:

json
{
  "agents": {
    "list": [
      {
        "id": "watson",
        "name": "Watson",
        "workspace": "/path/to/agents/watson",
        "model": {
          "primary": "anthropic/claude-opus-4-5"
        },
        "identity": {
          "name": "Watson",
          "emoji": "🔬"
        }
      }
    ]
  }
}

Bindings:

json
{
  "bindings": [
    {
      "agentId": "watson",
      "match": {
        "channel": "discord",
        "peer": {
          "kind": "channel",
          "id": "1234567890"
        }
      }
    }
  ]
}

Channels:

json
{
  "channels": {
    "discord": {
      "guilds": {
        "YOUR_GUILD_ID": {
          "channels": {
            "1234567890": {
              "allow": true,
              "requireMention": false,
              "systemPrompt": "Deep research and competitive analysis"
            }
          }
        }
      }
    }
  }
}

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:

typescript
sessions_list({
  kinds: ["agent"],
  limit: 10,
  messageLimit: 3  // Show last 3 messages per agent
})
Send Messages to Agents

Direct communication:

typescript
sessions_send({
  label: "watson",  // Agent ID
  message: "Research the competitive landscape for X"
})

Wait for response:

typescript
sessions_send({
  label: "watson",
  message: "What did you find about X?",
  timeoutSeconds: 300  // Wait up to 5 minutes
})
Spawn Sub-Agent Tasks

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

typescript
sessions_spawn({
  agentId: "watson",  // Optional: use specific agent
  task: "Research competitive landscape for X and write a report",
  model: "anthropic/claude-opus-4-5",  // Optional: override model
  runTimeoutSeconds: 3600,  // 1 hour max
  cleanup: "delete"  // Delete session after completion
})

The sub-agent will:

  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:

typescript
sessions_history({
  sessionKey: "watson-session-key",
  limit: 50
})
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):

typescript
// Main agent delegates task
sessions_send({
  label: "watson",
  message: "Research X and update memory/research-X.md"
})

// Watson works independently, updates files
// Main agent checks later or Watson reports back

3. Spawn for complex tasks:

typescript
// For longer-running, isolated work
sessions_spawn({
  agentId: "watson",
  task: "Deep dive: analyze competitors A, B, C. Write report to reports/competitors.md",
  runTimeoutSeconds: 7200,
  cleanup: "keep"  // Keep session for review
})

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

typescript
// In Watson's context
sessions_send({
  label: "picasso",
  message: "Create an infographic from data in reports/research.md"
})
Show full SKILL.md (391 more words)Show less
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
typescript
// Main agent receives request: "Research competitor X"

// 1. Check if Watson is active
const agents = sessions_list({ kinds: ["agent"] })

// 2. Delegate to Watson
sessions_send({
  label: "watson",
  message: "Research competitor X: products, pricing, market position. Write findings to memory/research-X.md"
})

// 3. Watson works independently:
//    - Searches web
//    - Analyzes data
//    - Updates memory file
//    - Reports back when done

// 4. Main agent retrieves results
const results = Read("agents/watson/memory/research-X.md")

// 5. Share with user
"Research complete! Watson found: [summary]"
Communication Flow

Main Agent (You) ↔ Specialized Agents:

User Request
    ↓
Main Agent (Claire)
    ↓
sessions_send("watson", "Research X")
    ↓
Watson Agent
    ↓
- Uses web_search
- Uses web_fetch
- Updates memory files
    ↓
Responds to main session
    ↓
Main Agent synthesizes and replies

Discord-Bound Agents:

User posts in #research channel
    ↓
Watson Agent (bound to channel)
    ↓
- Sees message directly
- Responds in channel
- No main agent involvement

Hybrid Approach:

User: "Research X" (main channel)
    ↓
Main Agent delegates to Watson
    ↓
Watson researches and reports back
    ↓
Main Agent: "Done! Watson found..."
    ↓
User: "Show me more details"
    ↓
Main Agent: "@watson post your full findings in #research"
    ↓
Watson posts detailed report in #research channel

Troubleshooting

Agent Creation Issues:

"Agent not appearing in Discord"

  • Verify channel ID is correct
  • Check gateway config bindings section
  • Restart gateway: openclaw gateway restart

"Model errors"

  • Verify model name format: provider/model-name
  • 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 sessions_send

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. 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
  • View Channels - To read channel list
  • Send Messages - 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

© LeoYeAI, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 5 other files (scripts) in skills/agent-council of LeoYeAI/openclaw-master-skills.

  • SKILL.md
  • README.md
  • _meta.json
  • scripts/create-agent.sh
  • scripts/rename_channel.py
  • scripts/setup_channel.py

Open the folder on GitHubat commit e5199b5

Compare with similar skills

Agent Council next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Agent Council compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Agent Council this skillLeoYeAI/openclaw-master-skills2.2k—~4.1kAutomated safety check: PassMIT
Cao Pluginawslabs/cli-agent-orchestrator1.4k—~3.1kAutomated safety check: NotesApache-2.0
Feishu Multi Agenthyperlist/feishu-multi-agent273—~419Automated safety check: PassNone
agtx One-Shot Project Runnerfynnfluegge/agtx1.7k—~3.8kAutomated safety check: PassApache-2.0
Fleet Manager for Agent Sessionsasgeirtj/system_prompts_leaks69k—~2.5kAutomated safety check: PassCC0-1.0
Project Developmentguanyang/open-agent-hub9772 repos~4.7kAutomated safety check: PassMIT

Similar skills

  • Cao Plugin

    awslabs/cli-agent-orchestrator

    Official

    Create a new CAO (CLI Agent Orchestrator) plugin. An agent skill from awslabs/cli-agent-orchestrator.

    1.4k GitHub stars~3.1k tokensUpdated today
    Agent WorkflowsAuto-check: notes
  • Feishu Multi Agent

    hyperlist/feishu-multi-agent

    飞书多 Agent 系统搭建指南。当用户要求创建新的功能 Agent、配置飞书群聊绑定、 搭建多 Agent 协作系统时激活此 skill。

    273 GitHub stars~419 tokensUpdated 7 mo ago
    Agent WorkflowsAuto-check passed
  • Runs a whole project unattended on an agtx kanban board, decomposing the goal, starting tasks, unblocking workers and merging each result.

    1.7k GitHub stars~3.8k tokensUpdated 8 days ago
    Agent WorkflowsAuto-check passed
  • Fleet Manager for Agent Sessions

    asgeirtj/system_prompts_leaks

    Shows one digest of coding-agent sessions across your connected machines and lets you open, read, steer, approve, stop and close them, over Herdr, tmux or MSP.

    69k GitHub stars~2.5k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Project Development

    guanyang/open-agent-hub

    This skill should be used for project-level decisions about LLM-powered systems: whether an LLM is the right primitive for the task at hand, the shape of a multi-stage batch or agent pipeline, token…

    977 GitHub starsUsed in 2 repos~4.7k tokens
    Agent WorkflowsAuto-check passed
  • WebGPT

    Nhahan/WebGPT

    Hands bounded tasks from Codex to a signed-in ChatGPT web session at a chosen reasoning level, or opens a terminal chat in your project that you control.

    122 GitHub stars~1.4k tokensUpdated 17 days ago
    Agent WorkflowsAuto-check passed

More from LeoYeAI/openclaw-master-skills

All 1,235 skills in this repo
  • DevOps Pipeline Management

    LeoYeAI/openclaw-master-skills

    Manages pipelines on a DevOps quality and efficiency platform through its OpenAPI: list workspaces and templates, create, update, run and cancel pipelines, and read run records.

    2.2k GitHub stars~4.2k tokensUpdated 2 mo ago
    Auto-check: notes
  • Feishu Document Collaboration

    LeoYeAI/openclaw-master-skills

    Patches OpenClaw's Feishu extension so an edited document triggers an isolated agent session that reads the doc and replies inline, turning it into a live chat space.

    2.2k GitHub stars~2k tokensUpdated 2 mo ago
    Auto-check passed
  • Files Memory System

    LeoYeAI/openclaw-master-skills

    Multi-context memory management system for OpenClaw agents with group-isolated storage, global shared memory, workspace organization, and group-specific skills isolation.

    2.2k GitHub stars~3.8k tokensUpdated 2 mo ago
    Auto-check passed
  • GEO-Claw AI Visibility Agent

    LeoYeAI/openclaw-master-skills

    Runs a brand's AI-search visibility work end to end: diagnosing how AI platforms represent it, repositioning it, producing AI-optimized content and monitoring ongoing mentions.

    2.2k GitHub stars~4.7k tokensUpdated 2 mo ago
    Auto-check passed
  • Google Workspace CLI

    LeoYeAI/openclaw-master-skills

    Installs and authenticates the gws CLI, then automates Gmail, Drive, Sheets, Calendar, Docs, Chat and Tasks with ready-made recipes, persona bundles and security audits.

    2.2k GitHub stars~2.6k tokensUpdated 2 mo ago
    Auto-check: notes
  • HealthFit Health Advisors

    LeoYeAI/openclaw-master-skills

    Runs four advisor roles, a fitness coach, nutritionist, data analyst and TCM practitioner, to build a health profile and track workouts, diet and wellness over time.

    2.2k GitHub stars~4.4k tokensUpdated 2 mo ago
    Auto-check passed

Works with

Questions about Agent Council

What does Agent Council do?

Complete toolkit for creating autonomous AI agents and managing Discord channels for OpenClaw. Agent Council is an agent skill from LeoYeAI/openclaw-master-skills. Complete toolkit for creating autonomous AI agents and managing Discord channels for OpenClaw.

When should I use Agent Council?

Agent Council fits situations like: setting up multi-agent systems; creating new agents; managing Discord channel organization.

How do I install Agent Council in Claude Code?

Run `npx skills add LeoYeAI/openclaw-master-skills --skill agent-council -a claude-code`. Or copy the skill folder (skills/agent-council in LeoYeAI/openclaw-master-skills) into .claude/skills/agent-council in your project. Claude Code loads it when a task matches its description.

How do I install Agent Council in Codex?

Run `npx skills add LeoYeAI/openclaw-master-skills --skill agent-council -a codex`. Or copy the skill folder (skills/agent-council in LeoYeAI/openclaw-master-skills) into .agents/skills/agent-council in your project. Codex loads it when a task matches its description.

Can I use Agent Council in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add LeoYeAI/openclaw-master-skills --skill agent-council -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/agent-council, .gemini/skills/agent-council, .github/skills/agent-council and .opencode/skills/agent-council in your project.

What does Agent Council need to run?

Going by SKILL.md and its folder, Agent Council needs Python and a shell for the scripts in its folder and the command-line tools its instructions call (python3). Our summary lists: Python 3; A Bash shell.

Does Agent Council access the network?

SKILL.md names 1 domain. As links in the text: docs.openclaw.ai. This is read from the text; nothing was executed.

Is Agent Council safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Agent Council use?

Agent Council is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Agent Council use?

About 4.1k tokens (SKILL.md is roughly 17k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Agent Council?

Skills that share tags, products or a category with Agent Council: Cao Plugin (awslabs/cli-agent-orchestrator, 1.4k stars), Feishu Multi Agent (hyperlist/feishu-multi-agent, 273 stars), agtx One-Shot Project Runner (fynnfluegge/agtx, 1.7k stars) and Fleet Manager for Agent Sessions (asgeirtj/system_prompts_leaks, 69k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Agent Council?

LeoYeAI (a GitHub user) maintains it in LeoYeAI/openclaw-master-skills, which has 2,161 GitHub stars. The repository holds 1,235 skills in this directory. The repository was last updated on July 20, 2026.

Source: LeoYeAI/openclaw-master-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.