advisor-board

Run a cross-vendor advisor board for independent review of high-stakes artifacts.

2|1|Updated Jun 25, 2026
One-click install
npx skills add https://github.com/Consiliency/agent-harness --skill advisor-board-consiliency
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: advisor-board
Source: https://github.com/Consiliency/agent-harness/tree/main/phase-loop-skills/advisor-board
Command: npx skills add https://github.com/Consiliency/agent-harness --skill advisor-board-consiliency

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? High-stakes changes like implementation diffs, release closeouts, and plans need independent review evidence, but a single model review can miss defects. This Skill convenes a multi-vendor advisor board through the agent-harness runtime so each artifact is reviewed by several independent model seats with distinct lenses. ## Core Features & Use Cases - Cross-vendor review board: Composes a default 4-seat board (Claude Fable 5, Grok 4.6, GPT-6 Astra, Gemini 3.8 Flash) with distinct review lenses, availability-aware backfilling, and a hard floor of 3 reviewers. - Flexible material input: Feed artifacts inline, stage local files via artifact_ref/brief_ref, or pass large private files by reference with context_refs so legs open them with their own tools. - Bounded review loops: Heartbeat-based liveness detection, input-scaled timeouts, delta re-review of dissenting seats, and round caps that converge a review-fix-re-review loop. - Use Case: Before merging a risky refactor, run phase-loop advisor-board <artifact> to collect AGREE/DISAGREE verdicts from four independent vendors, then re-run only dissenting seats against the delta after each fix. ## Quick Start Ask the agent to run the advisor board on your change artifact, for example: run a cross-vendor advisor board review of my implementation diff at path/to/bundle.md and report each seat's verdict.

Frequently Asked Questions about advisor-board

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a cross-vendor AI review board on a code change?▼

Run `phase-loop advisor-board <artifact>` from the agent-harness runtime, or in-process call compose_review_board() and pass the material path via artifact_ref to invoke_board. Each leg returns a verdict of AGREE, PARTIALLY AGREE, or DISAGREE.

How do I pass large or private files to a multi-model review panel?▼

Use context_refs with a list of local file paths for true by-reference review: the runtime stages only a path and metadata manifest, and each leg opens the files with its own tools. Missing paths fail closed unless context_refs_soft_warn is enabled.

What happens when some review vendors are unavailable or unauthenticated?▼

Board composition is availability-aware: only vendors present on PATH and authenticated get seats, and remaining seats are backfilled onto available vendors with different lenses. Two vendors up still yields a full 4-seat board, and one vendor yields four distinct-lens seats.

Why did an advisor board leg report TIMEOUT or UNAVAILABLE?▼

TIMEOUT means a heartbeat-extinction stall or a hard wall-clock deadline fired; UNAVAILABLE means the seat could not run, such as tui_adapter_required for Claude seats inside a host where the nested TUI adapter cannot run. Both are structured evidence, not successful reviews.

Can I use API keys instead of subscription CLIs for the Claude review seat?▼

No. Fable and Opus seats run only through the homebrew Claude Code self-PTY TUI adapter after a probe proves first-party claude.ai subscription auth. Gateways, APIs, SDKs, and native Task agents fail closed and are never substituted.