gemini-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 gemini-advisor-board-consiliency
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gemini-advisor-board
Source: https://github.com/Consiliency/agent-harness/tree/main/skills-src/gemini/gemini-advisor-board
Command: npx skills add https://github.com/Consiliency/agent-harness --skill gemini-advisor-board-consiliency

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? High-stakes changes like plans, implementation diffs, and release closeouts need independent review evidence, but relying on a single model or vendor creates blind spots. This Skill runs a customizable cross-vendor advisor board through the agent-harness runtime so every critical artifact gets structured multi-vendor scrutiny. ## Core Features & Use Cases - Availability-aware board composition: Seats a 4-reviewer board (Claude Fable 5, Grok 4.6, GPT-6 Astra, Gemini 3.8 Flash) with distinct review lenses, backfilling seats onto available vendors so the board never collapses below 3 reviewers. - Three material-feeding modes: Pass artifacts inline, stage local files via artifact_ref/brief_ref, or use true by-reference context_refs for large or private files that legs open with their own tools. - Heartbeat-based liveness and bounded loops: Reclaims stalled legs via heartbeat extinction rather than wall-clock timers, supports optional per-leg hard deadlines, and structures review-fix-re-review loops with delta reviews and round caps. - Use Case: Before merging a risky refactor, run phase-loop advisor-board diff.md to collect AGREE/DISAGREE verdicts from four independent vendor seats, then re-run only dissenting seats against the delta after each fix round. ## Quick Start Run the advisor board on my change by executing phase-loop advisor-board with the path to my review bundle and report each seat's verdict.

Frequently Asked Questions about gemini-advisor-board

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

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

Run `phase-loop advisor-board <artifact>` from the command line, or in-process call compose_review_board() and pass the result to invoke_board with artifact_ref pointing at your review bundle. Each leg returns a verdict of AGREE, PARTIALLY AGREE, or DISAGREE.

How do I pass large or private files to the review board?▼

Use context_refs with a list of file paths for true by-reference mode. The runtime stages only a path and metadata manifest, and each leg opens the files with its own local tools, so raw contents never enter the prompt bundle.

What happens when a vendor CLI is missing or not authenticated?▼

Board composition is availability-aware: vendors not on PATH or not authenticated are dropped, and their seats are backfilled onto available vendors with different review lenses. The board still targets 4 seats and never collapses to 1-2 reviewers.

Why did a review leg end with a TIMEOUT status?▼

A TIMEOUT means either heartbeat extinction (no output or CPU progress for 180s) or a hard wall-clock deadline fired. Check for a [leg-liveness] stall marker to distinguish a silent stall from a deadline expiry, since they are diagnosed and retried differently.

When should I set timeouts_by_leg for a review leg?▼

Set it only when policy requires an absolute ceiling on an actively progressing leg, since it replaces the default backstop and kills the leg even mid-progress. Stalls are already handled by heartbeat extinction, so omit it by default.

Can the advisor board use external research tools during review?▼

Yes, opt in with ResearchPolicy(enabled=True). The runtime requires the published pmcp==1.20.0 scoped_advisor_audit.v1 capability and exposes only audited Firecrawl and Bright Data research tools, with seats that cannot enforce the profile failing closed.