Council Execution
npx machina-cli add skill hex/claude-council/council-execution --openclawCouncil Query Execution
Step 1: Run Query and Save to File
bash ${CLAUDE_PLUGIN_ROOT}/scripts/run-council.sh --providers=gemini,openai -- "Your question"
This outputs the path to the saved file (e.g., .claude/council-cache/council-1734567890.md).
Flag syntax: Use = with no spaces: --providers=gemini,openai
CRITICAL: Always place -- before the prompt to prevent prompt text containing dashes from being parsed as flags.
Step 2: Read and Display the Output VERBATIM
Use the Read tool to read the output file path returned by Step 1.
CRITICAL: Display the file content EXACTLY as written. Do NOT:
- Reformat or reinterpret any text
- Add your own headers or structure
- Summarize or abbreviate responses
- Skip any lines including separator lines (
---)
Simply copy-paste the entire file content into your response.
Step 3: Complete the Synthesis Section
The file ends with a ## Synthesis header. Write your synthesis UNDER that header:
- Consensus: Where providers agree
- Divergence: Where they disagree
- Recommendation: Best approach
Step 4: Notify User of Saved Output
After displaying the synthesis, tell the user:
(use this emoji 💾) Full output saved to
.claude/council-cache/council-TIMESTAMP.md(use the actual filename)
This lets them review the complete responses later.
Provider Names
ALWAYS use emoji + space when mentioning a provider:
- 🟦 Gemini (blue square)
- 🔳 OpenAI (white square button)
- 🟥 Grok (red square)
- 🟩 Perplexity (green square)
Format: 🟦 Gemini not 🟦Gemini - always include the space.
Source
git clone https://github.com/hex/claude-council/blob/main/skills/council-execution/SKILL.mdView on GitHub Overview
Council Execution guides you through running a council query, saving the result to a file, and producing a structured synthesis. It ensures you present the raw output verbatim and then summarize consensus, divergence, and a recommended approach under the Synthesis header.
How This Skill Works
It runs a shell command to query providers (for example, Gemini and OpenAI) via the run-council.sh script and returns the path to a saved markdown file. You must display the file content exactly as written (verbatim) and then complete the synthesis under the Synthesis header with Consensus, Divergence, and Recommendation, after which you notify the user of the saved output. CRITICAL: Always place -- before the prompt to prevent prompt text containing dashes from being parsed as flags.
When to Use It
- When you need a cross-provider answer and want to preserve raw outputs for audit.
- When the question requires corroboration across Gemini and OpenAI.
- When you must display content verbatim before synthesis to stakeholders.
- When you need a saved, reviewable record of council results.
- When you’re preparing a decision brief requiring Consensus, Divergence, and Recommendation.
Quick Start
- Step 1: Run the council script with --providers=gemini,openai -- "Your question".
- Step 2: Read the saved file path from the script output and copy the file content verbatim.
- Step 3: Under the Synthesis header, write Consensus, Divergence, and Recommendation, then notify the user of the saved output.
Best Practices
- Use --providers=gemini,openai with no spaces around "=".
- Always place -- before the prompt to prevent prompt text containing dashes from being parsed as flags.
- Copy and display the entire file content verbatim; do not reformat.
- Ensure the Synthesis section contains clear Consensus, Divergence, and Recommendation.
- Save outputs to the cache path and verify the TIMESTAMP filename.
Example Use Cases
- Query 🟦 Gemini and 🔳 OpenAI for a feature decision and produce a synthesis with Consensus, Divergence, and Recommendation.
- Audit cross-provider results by saving raw council output for a compliance review.
- Resolve conflicting guidance from 🟦 Gemini, 🔳 OpenAI, and 🟩 Perplexity and present a unified recommendation.
- Prepare a decision brief for stakeholders by extracting the verbatim outputs and detailing the synthesis.
- Archive full council outputs to .claude/council-cache/council-TIMESTAMP.md for future reference.
