Awesome-openclaw-skills 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.
install
source · Clone the upstream repo
git clone https://github.com/sundial-org/awesome-openclaw-skills
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/sundial-org/awesome-openclaw-skills "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/council" ~/.claude/skills/sundial-org-awesome-openclaw-skills-council && rm -rf "$T"
OpenClaw · Install into ~/.openclaw/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/sundial-org/awesome-openclaw-skills "$T" && mkdir -p ~/.openclaw/skills && cp -r "$T/skills/council" ~/.openclaw/skills/sundial-org-awesome-openclaw-skills-council && rm -rf "$T"
manifest:
skills/council/SKILL.mdsource content
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:
— Challenges assumptions, finds weaknesses, stress-testsDevilsAdvocate.md
— Designs systems, structure, high-level approachArchitect.md
— Implementation details, technical feasibilityEngineer.md
— Voice, style, presentation, user experienceArtist.md
Adding New Council Members
Simply add a new
.md file to the agents/ folder:
# 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
exists and has agent files~/.claude/Agents/ - If yes, prefer custom agents from that directory
- If no, use the bundled agents in this skill's
folderagents/
Process
- Receive the idea/topic from the user
- Discover available agents (scan
folder or custom path)agents/ - Send a loading message to the user:
🏛️ *The Council convenes...* (this takes 2-5 minutes) - 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.
- Return the consolidated feedback to the user
Output Format
## 🏛️ 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
files in.md
folderagents/ - 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.)