council
Send an idea to the Council of the Wise for multi-perspective feedback. Spawns sub-agents to analyze from multiple expert perspectives. Auto-discovers agent personas from agents/ folder.
Best use case
council is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Send an idea to the Council of the Wise for multi-perspective feedback. Spawns sub-agents to analyze from multiple expert perspectives. Auto-discovers agent personas from agents/ folder.
Teams using council should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/council/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How council Compares
| Feature / Agent | council | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Send an idea to the Council of the Wise for multi-perspective feedback. Spawns sub-agents to analyze from multiple expert perspectives. Auto-discovers agent personas from agents/ folder.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Council of the Wise When the user says "send it to the council" or "council of the wise" or similar, spawn a sub-agent to analyze the idea from multiple expert perspectives. ## Usage ``` "Send this to the council: [idea/plan/document]" "Council of the wise: [topic]" "Get the council's feedback on [thing]" ``` ## Council Members The skill **auto-discovers** agent personas from the `agents/` folder. Any `.md` file in that folder becomes a council member. **Default members:** - `DevilsAdvocate.md` — Challenges assumptions, finds weaknesses, stress-tests - `Architect.md` — Designs systems, structure, high-level approach - `Engineer.md` — Implementation details, technical feasibility - `Artist.md` — Voice, style, presentation, user experience ### Adding New Council Members Simply add a new `.md` file to the `agents/` folder: ```bash # Add a security reviewer echo "# Pentester\n\nYou analyze security implications..." > agents/Pentester.md # Add a QA perspective echo "# QATester\n\nYou find edge cases..." > agents/QATester.md ``` The skill will automatically include any agents it finds. No config file needed. ### Custom Agent Location (Optional) If the user has custom PAI agents at `~/.claude/Agents/`, those can be used instead: - Check if `~/.claude/Agents/` exists and has agent files - If yes, prefer custom agents from that directory - If no, use the bundled agents in this skill's `agents/` folder ## Process 1. Receive the idea/topic from the user 2. Discover available agents (scan `agents/` folder or custom path) 3. Send a loading message to the user: `🏛️ *The Council convenes...* (this takes 2-5 minutes)` 4. Spawn a sub-agent with **5-minute timeout** using this task template: ``` Analyze this idea/plan from multiple expert perspectives. **The Idea:** [user's idea here] **Your Task:** Read and apply these agent perspectives from [AGENT_PATH]: [List all discovered agents dynamically] For each perspective: 1. Key insights (2-3 bullets) 2. Concerns or questions 3. Recommendations End with: - **Synthesis** section combining best ideas and flagging critical decisions - Note where council members **disagree** with each other — that's where the insight is - **Token Usage** with estimated input/output tokens (based on content length) Use the voice and personality defined in each agent file. Don't just list points — embody the perspective. ``` 5. Return the consolidated feedback to the user ## Output Format ```markdown ## 🏛️ Council of the Wise — [Topic] ### 👹 Devil's Advocate [challenges and risks — sharp, probing voice] ### 🏗️ Architect [structure and design — strategic, principled voice] ### 🛠️ Engineer [implementation notes — practical, direct voice] ### 🎨 Artist [voice and presentation — evocative, user-focused voice] ### ⚖️ Synthesis [combined recommendation + key decisions needed] [note where council members disagreed and why — that's the gold] --- 📊 **Token Usage:** ~X input / ~Y output tokens *(estimated)* ``` ## Configuration No config file needed. The skill auto-discovers agents and uses sensible defaults: - **Timeout:** 5 minutes (enforced via sub-agent spawn) - **Agents:** All `.md` files in `agents/` folder - **Output:** Markdown with synthesis and token usage - **Model:** Uses session default (can override via Clawdbot) ## Notes - Council review takes 2-5 minutes depending on complexity - Use for: business ideas, content plans, project designs, major decisions - Don't use for: quick questions, simple tasks, time-sensitive requests - Token usage is estimated based on content length (not precise API measurement) - Add specialized agents for domain-specific analysis (security, legal, etc.)
Related Skills
llm-council
Orchestrate a configurable, multi-member CLI planning council (Codex, Claude Code, Gemini, OpenCode, or custom) to produce independent implementation plans, anonymize and randomize them, then judge and merge into one final plan. Use when you need a robust, bias-resistant planning workflow, structured JSON outputs, retries, and failure handling across multiple CLI agents.
council-2
Council Chamber orchestration with Memory Bridge. Single session, multiple personas, structured deliberation.
portfolio-watcher
Monitor stock/crypto holdings, get price alerts, track portfolio performance
portainer
Control Docker containers and stacks via Portainer API. List containers, start/stop/restart, view logs, and redeploy stacks from git.
portable-tools
Build cross-device tools without hardcoding paths or account names
polymarket
Trade prediction markets on Polymarket. Analyze odds, place bets, track positions, automate alerts, and maximize returns from event outcomes. Covers sports, politics, entertainment, and more.
polymarket-traiding-bot
No description provided.
polymarket-analysis
Analyze Polymarket prediction markets for trading edges. Pair Cost arbitrage, whale tracking, sentiment analysis, momentum signals, user profile tracking. No execution.
polymarket-agent
Autonomous prediction market agent - analyzes markets, researches news, and identifies trading opportunities
polymarket-5
Query Polymarket prediction markets. Use for questions about prediction markets, betting odds, market prices, event probabilities, or when user asks about Polymarket data.
polymarket-4
Query Polymarket prediction markets. Use for questions about prediction markets, betting odds, market prices, event probabilities, or when user asks about Polymarket data.
polymarket-3
Query Polymarket prediction market odds and events via CLI. Search for markets, get current prices, list events by category. Supports sports betting (NFL, NBA, soccer/EPL, Champions League), politics, crypto, elections, geopolitics. Real money markets = more accurate than polls. No API key required. Use when asked about odds, probabilities, predictions, or "what are the chances of X".