Run structured multi-perspective decisions with Council of High Intelligence
Use Council of High Intelligence when an agent should convene a structured panel, force disagreement, and return a decision with dissent, kill criteria, and next actions.
npx skills add agentskillexchange/skills --skill run-structured-multi-perspective-decisions-with-council-of-high-intelligence
Use Council of High Intelligence when an operator wants a hard decision handled through a repeatable deliberation protocol instead of a single-pass answer. The agent runs the /council workflow, selects a full council, triad, duo, or named member panel, keeps first analyses independent, forces cross-examination, labels evidence quality, and synthesizes a verdict with unresolved questions, dissent, acceptable compromises, kill criteria, and the next concrete action. Invoke this for architectural, product, risk, strategy, AI-safety, design, or shipping decisions where competing frames and downside matter. The boundary is structured decision deliberation inside supported agent hosts; it is not a generic prompt pack, debate toy, or replacement for primary research and experiments.
What this skill actually does
Inputs and prerequisites: Council of High Intelligence plugin or cloned repository, one supported agent host such as Claude Code, Codex, Gemini CLI, or OpenCode, and optional model/provider routing configuration.
Setup notes: In Claude Code, run /plugin marketplace add 0xNyk/council-of-high-intelligence and /plugin install council@council-of-high-intelligence. For Codex, Gemini CLI, or OpenCode, clone the repository and run ./install.sh with the matching –codex-only, –gemini-only, or –opencode-only flag, then restart the target client.
Source and verification boundary: use https://www.nyk.dev/oss/council-of-high-intelligence as the canonical reference before running the workflow; keep commands, API calls, CLI usage, and generated outputs reviewable against that upstream source.
Framework fit: publish this as a Multi-Framework workflow only when the operator can invoke the documented toolchain directly, rather than treating the upstream project as a generic product listing.