Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →hex/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 (non-agent) council queries.
Passed 1 of 10 test cases with the skill, and 2 of 10 without it.
2 fixed1 passed either way17 still failing3 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
A newer attempt on gemini-3.6-flash on 10/2/2026 did not produce a publishable comparison (not comparable). The snapshot above is the previously measured run.
One of 2 test cases the skill fixed. Same model, same prompt, with and without the skill.
What notification message format and icon should be displayed at the end of a council run to inform the user where the output file `.claude/council-cache/council-1700000000.md` is saved?
| Checked | Without skill | With skill |
|---|---|---|
| Includes the floppy disk icon 💾 in the notification. | Missed | Passed |
| Includes the exact file path .claude/council-cache/council-1700000000.md in the save message. | Passed | Passed |
The instructions your model reads when the skill loads.
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
Pass only the flags the user asked for. Never add --no-pane, --quiet,
--no-cache or --no-auto-context on your own judgment; they are the user's
to choose, and the script already skips a pane that cannot open.
CRITICAL: Always place -- before the prompt to prevent prompt text containing dashes from being parsed as flags.
Run this Bash call with timeout: 600000 (ten minutes). The Bash tool's
two-minute default is shorter than a slow council round, and inside tmux a
provider failure makes the streaming pane offer the user a retry for
COUNCIL_RETRY_WAIT seconds (default 45) and then runs another provider round
if accepted. A call cut off mid-run loses the whole transcript, the answers
that did arrive included.
Use the Read tool to read the output file path returned by Step 1.
If the file's first line is <!-- council: round 1 was shown in the pane -->,
the user already read every round-1 answer in the streaming pane. Do not
reprint them. Instead, output one line per provider in round 1, taken from
its ## header (name, role, model, and any fallback note) followed by
answered or the Error: line under it. When the header says the seat fell
back, add the > <provider>: <reason> line printed under it. Then display VERBATIM the rest of
the file from its ## Round 2 heading, or from ## Synthesis when there is no
round 2 (debate rebuttals never reach the pane), and continue with Step 3 under
the ## Synthesis header. Without that first line, display the whole file as
below.
test cases passed, vs 2 / 10 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.