querying-council
The querying-council skill executes multi-provider AI queries across Gemini, OpenAI, Grok, and Perplexity by running a query pipeline, displaying each provider's formatted response verbatim, and generating a synthesis analyzing consensus, divergence, and recommendations. Use this skill when invoking the ask command for standard council queries that require perspectives from multiple AI providers rather than a single response.
git clone --depth 1 https://github.com/hex/claude-council /tmp/querying-council && cp -r /tmp/querying-council/skills/council-execution ~/.claude/skills/querying-councilSKILL.md
# Council Query Execution
## Step 1: Run Query and Save to File
```bash
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 ||-
One independent member of a local (provider-less) council. Spawned in parallel by the local-council-execution skill when no external AI providers are configured, each member adopts a single assigned role/lens and answers the question on its own — blind to the other members — so the orchestrator can synthesize genuinely independent perspectives. Not invoked directly by users.
Query multiple AI agents (Gemini, OpenAI, Grok, Perplexity, Kimi, and a local ollama model) for diverse perspectives on architecture decisions, technology choices, debugging dead-ends, and security tradeoffs. Use this whenever the user names the council directly, whatever the topic — ask the council, council review, full council review, what does the council think, get a second opinion from the council, run this past the council — including reviews of code, documents, plans or artifacts. Also suggest it unprompted when the user is choosing between competing approaches (e.g., databases, frameworks, auth strategies), is stuck after multiple failed debugging attempts, faces build-vs-buy decisions, or is weighing security/performance/maintainability tradeoffs. Do NOT suggest it unprompted for simple implementation tasks, quick fixes, or questions with clear single answers; a direct request for the council overrides that exclusion.
Fetch, list, or cancel background council jobs started with --async
Check connectivity and configuration status of all council providers
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 when complex architectural decisions are detected.
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 when the user accepts the local-council offer after no providers are found. This is a same-model (Claude-only) panel, not a cross-vendor council.
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 agent", "provider not working", "API configuration", or "extend council".