/council-execution
Executes council queries by running the query pipeline across selected AI providers (Gemini, OpenAI, Grok, Perplexity), displaying formatted responses verbatim, and generating a synthesis of consensus, divergence, and recommendations. Invoked by the ask command during standard
$ npx -y skills add hex/claude-council --skill council-execution --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/council-execution
Context preview
The summary Claude sees to decide when to auto-load this skill.
Executes council queries by running the query pipeline across selected AI providers (Gemini, OpenAI, Grok, Perplexity), displaying formatted responses verbatim, and generating a synthesis of consensus, divergence, and recommendations. Invoked by the ask command during standard
SKILL.md
council-execution.SKILL.mdname: council-execution
description: Executes council queries by running the query pipeline across selected AI providers (Gemini, OpenAI, Grok, Perplexity), displaying formatted responses verbatim, and generating a synthesis of consensus, divergence, and recommendations. Invoked by the ask command during standard (non-agent) council queries.
Council 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. Read `${CLAUDE_PLUGIN_ROOT}/prompts/synthesis.md` and write your synthesis UNDER that header following its structure (Consensus / Divergence / Recommendation) and calibration rules.
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.
Output Format: Provider Names
The output file uses emoji prefixes to visually distinguish providers. Preserve this format when displaying results:
| Provider | Prefix | |----------|--------| | Gemini | ๐ฆ Gemini | | OpenAI | ๐ณ OpenAI | | Grok | ๐ฅ Grok | | Perplexity | ๐ฉ Perplexity |
Read more
name: council-execution description: Executes council queries by running the query pipeline across selected AI providers (Gemini, OpenAI, Grok, Perplexity), displaying formatted responses verbatim, and generating a synthesis of consensus, divergence, and recommendations. Invoked by the ask command during standard (non-agent) council queries.
Council 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. Read `${CLAUDE_PLUGIN_ROOT}/prompts/synthesis.md` and write your synthesis UNDER that header following its structure (Consensus / Divergence / Recommendation) and calibration rules.
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.
Output Format: Provider Names
The output file uses emoji prefixes to visually distinguish providers. Preserve this format when displaying results:
| Provider | Prefix | |----------|--------| | Gemini | ๐ฆ Gemini | | OpenAI | ๐ณ OpenAI | | Grok | ๐ฅ Grok | | Perplexity | ๐ฉ Perplexity |
A Claude Code plugin that consults multiple AI coding agents in parallel and shows you their answers side-by-side.
Repo: hex/claude-council
Other skills on claude-council.
- /deep-execution
Executes agent-enhanced council queries by spawning parallel Claude subagents that each query a provider, evaluate response quality, ask follow-up questions, and return structured insights with confidence ratings and blind spot analysis. Invoked when the --agents flag is used or
Open skill - /local-council-execution
Runs a local council when no external AI providers are configured. Spawns N independent Claude subagents (one per role, blind to each other) that each answer the question from a single assigned lens, then synthesizes their perspectives. Invoked by the ask command via --local, or
Open skill - /provider-integration
Adds new AI providers to claude-council, configures provider API settings, troubleshoots provider connections, and documents the provider script interface. Covers creating provider shell scripts, setting API keys, and validating connectivity. Triggers on "add provider", "new AI
Open skill

