Source profileQuality 84/100

ffroliva/gflow-cli/skills/llm-council/SKILL.md

llm-council

Use when a pr-council-review (PR or branch mode) result needs independent corroboration from a different model family before trusting a GREEN verdict — high-stakes, security-sensitive, or architecturally significant reviews where same-model-family Claude subagents might share a blind spot. Also use when the user asks for "external", "second opinion", "cross-model", or names codex/antigravity (`agy`) or another external CLI coding agent alongside a review.

Source repository stars
96
Declared platforms
1
Static risk flags
1
Last source update
2026-08-04
Source checked
2026-08-04

Decision brief

What it does—and where it fits

Also use when the user asks for "external", "second opinion", "cross-model", or names codex/antigravity (`agy`) or another external CLI coding agent alongside a review.

Best for

  • Any pr-council-review run (PR mode or branch mode) where the artifact is high-stakes enough to want a second, differently-biased opinion before calling it GREEN.
  • Not needed for a quick spot-check or draft iteration — use /review (single-agent) for that; pr-council-review alone for a normal-stakes PR.

Not for

  • Tasks that require unconfirmed production actions or broad system permissions.
  • Environments where the pinned source and install steps cannot be inspected.

Compatibility matrix

Platform support, with evidence labels

PlatformStatusEvidenceWhat to check
CodexDeclaredSource recordInstall path and trigger
Claude CodeNot declaredNo explicit evidencePortability before use
CursorNot declaredNo explicit evidencePortability before use
Gemini CLINot declaredNo explicit evidencePortability before use
Open the compatibility checker

Installation

Inspect first. Install second.

The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

Source-detected install commandSource
npx skills add https://github.com/ffroliva/gflow-cli --skill "skills/llm-council"
Safe inspection promptEditorial

Inspect the Agent Skill "llm-council" from https://github.com/ffroliva/gflow-cli/blob/c64a8d8b246f9551e8a96c7fcf363d15e045c9b2/skills/llm-council/SKILL.md at commit c64a8d8b246f9551e8a96c7fcf363d15e045c9b2. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

Workflow

What the source asks the agent to do

  1. 01

    When to Use

    Any pr-council-review run (PR mode or branch mode) where the artifact is high-stakes enough to want a second, differently-biased opinion before calling it GREEN.

    Any pr-council-review run (PR mode or branch mode) where the artifact is high-stakes enough to want a second, differently-biased opinion before calling it GREEN.Not needed for a quick spot-check or draft iteration — use /review (single-agent) for that; pr-council-review alone for a normal-stakes PR.- Any pr-council-review run (PR mode or branch mode) where the artifact is high-stakes enough to want a second, differently-biased opinion before calling it GREEN. - Not needed for a quick spot-check or draft iteration…
  2. 02

    Quick Reference — Tiers

    Tier controls tool breadth, not review rounds. Fix → re-verify → repeat until GREEN (or a round cap) happens at every tier — that's how council review works, not a tier knob.

    Tier controls tool breadth, not review rounds. Fix → re-verify → repeat until GREEN (or a round cap) happens at every tier — that's how council review works, not a tier knob.
  3. 03

    Tool Registry

    Fixed, tested invocation recipes. Do not improvise a command for a listed tool — the "obvious" invocation is often a trap (see codex below).

    NEVER codex review. Its built-in prompt has gotten stuck in a self-inflicted loop reading skill files via a malformed PowerShell command, then retrying the identical broken command for 20+ minutes with zero progress. Co…Use: codex exec -s read-only -C --skip-git-repo-check "".Probe: codex --version (near-instant; confirms binary health only, not auth/quota).
  4. 04

    codex

    NEVER codex review. Its built-in prompt has gotten stuck in a self-inflicted loop reading skill files via a malformed PowerShell command, then retrying the identical broken command for 20+ minutes with zero progress. Co…

    NEVER codex review. Its built-in prompt has gotten stuck in a self-inflicted loop reading skill files via a malformed PowerShell command, then retrying the identical broken command for 20+ minutes with zero progress. Co…Use: codex exec -s read-only -C --skip-git-repo-check "".Probe: codex --version (near-instant; confirms binary health only, not auth/quota).
  5. 05

    Antigravity (agy)

    What it is: Google's Antigravity harness, invoked via agy. It supplies the high-tier's second, different-model-family opinion.

    What it is: Google's Antigravity harness, invoked via agy. It supplies the high-tier's second, different-model-family opinion.Best-known recipe: agy --agent --new-project --add-dir -p "" (run agy agents to list available agent names, e.g. gsd-plan-checker for reviewing a plan).Probe: agy --version first regardless — a fast binary-health check.

Permission review

Static risk signals and limitations

Reads files

low · line 30

The documentation asks the agent to read local files, directories, or repositories.

**Use:** `codex exec -s read-only -C <absolute-repo-dir> --skip-git-repo-check "<direct, fully self-contained prompt>"`.

Reads files

low · line 56

The documentation asks the agent to read local files, directories, or repositories.

| Running `codex review` because it sounds like the obvious subcommand for a review task | Use `codex exec -s read-only -C <dir> --skip-git-repo-check "<prompt>"` — see registry |

Evidence record

Why each signal appears

EvidenceSourceComputedTestedEditorial
SignalValueEvidence typeMeaning
Quality score84/100ComputedDocumentation, specificity, maintenance, and trust rules
Repository stars96SourceRepository attention, not individual Skill quality
Compatibility1 platformsSourceDeclared in the catalog source record
Usage guideautomated source guideEditorialGenerated or reviewed according to the visible evidence level

Pinned source

Provenance and original SKILL.md

Repository
ffroliva/gflow-cli
Skill path
skills/llm-council/SKILL.md
Commit
c64a8d8b246f9551e8a96c7fcf363d15e045c9b2
License
MIT
Collected
2026-08-04
Default branch
develop
View the original SKILL.md

llm-council — external-tools review layer

Overview

Wraps pr-council-review (unchanged) and adds a layer of external CLI coding agents (codex, plus Antigravity — the agy harness) as additional independent reviewers, then folds their verdicts into the same synthesis. Internal Claude subagents are independent per-dimension but share one model family's blind spots — a phrasing choice, a Windows-vs-POSIX nuance, or a syntax error that reads fine to one Claude reviewer reads fine to all of them. A different model family catches a different error distribution. Confirmed live: on one review, external tools caught 6 real, distinct issues (a wording-accuracy bug, a wrong test count, a Windows-only test-triviality nuance, a test-isolation gap, a missing test, a malformed markdown fence) that 12 internal Claude-subagent dispatches (6 dimensions × 2 rounds) had all missed.

When to Use

  • Any pr-council-review run (PR# mode or branch mode) where the artifact is high-stakes enough to want a second, differently-biased opinion before calling it GREEN.
  • Not needed for a quick spot-check or draft iteration — use /review (single-agent) for that; pr-council-review alone for a normal-stakes PR.

Quick Reference — Tiers

TierInternal (pr-council-review)External tools
small (default)✅ full dimension councilnone — identical to running pr-council-review directly
mediumcodex
highcodex + Antigravity (agy)

Tier controls tool breadth, not review rounds. Fix → re-verify → repeat until GREEN (or a round cap) happens at every tier — that's how council review works, not a tier knob.

Tool Registry

Fixed, tested invocation recipes. Do not improvise a command for a listed tool — the "obvious" invocation is often a trap (see codex below).

codex

  • NEVER codex review. Its built-in prompt has gotten stuck in a self-inflicted loop reading skill files via a malformed PowerShell command, then retrying the identical broken command for 20+ minutes with zero progress. Confirmed reproducible on a clean retry.
  • Use: codex exec -s read-only -C <absolute-repo-dir> --skip-git-repo-check "<direct, fully self-contained prompt>".
  • Probe: codex --version (near-instant; confirms binary health only, not auth/quota).
  • Timeout budget: real calls run 10-20 min at default (xhigh) reasoning effort. Always background it — never block synchronously.
  • Orphan risk: a killed/timed-out codex exec can leave codex.exe / codex-code-mode-host.exe / sandbox-helper processes running on Windows. After any kill, verify via tasklist/ps that the named PIDs are actually gone before retrying — a retry racing an orphan still writing the same output path silently corrupts the result.

Antigravity (agy)

  • What it is: Google's Antigravity harness, invoked via agy. It supplies the high-tier's second, different-model-family opinion.
  • Best-known recipe: agy --agent <gsd-agent-name> --new-project --add-dir <absolute-repo-dir> -p "<prompt>" (run agy agents to list available agent names, e.g. gsd-plan-checker for reviewing a plan).
  • Probe: agy --version first regardless — a fast binary-health check.
  • If it's missing or fails: Antigravity is a newer harness and has failed non-interactively in testing (an interactive workspace prompt even with --add-dir; a bare unexplained termination error even with --agent/--new-project) — plausibly account-quota exhaustion, unconfirmed. Don't silently retry past its probe. When agy isn't installed or won't run non-interactively, suggest installing it (or substituting another external CLI coding agent — e.g. a codex-only medium run) and continue best-effort with whatever did return; never block the whole round on it.

Dispatch Flow

  1. Resolve tier → tool list.
  2. Probe every resolved tool in parallel, short timeout (~10-15s). A tool that doesn't respond is excluded from this round — name it in the report, don't just drop it silently. The probe only catches binary-health failures (not installed, hung shell); a quota-exhausted tool can still pass the probe and fail on the real call — that's what the dispatch-layer disclosure step below is for.
  3. Dispatch pr-council-review (unchanged) for the internal dimension council.
  4. In parallel, dispatch each surviving external tool via its registry recipe, backgrounded.
  5. Fold each returning verdict into the same synthesis table pr-council-review produces — same GREEN/YELLOW/RED vocabulary, tagged by source (e.g. D3 (internal) vs codex (external)). A tool that fails or times out after passing its probe is dropped from this round with an explicit note in the report. Never silently drop, never block the whole round on one flaky tool.
  6. Any finding — internal or external — that warrants a fix gets applied, then re-verified against the specific dimension/tool that flagged it (not necessarily the whole pool again).
  7. Report: pr-council-review's existing shape, plus an "External tools" line noting which ran / were skipped / failed and why.

Common Mistakes

MistakeFix
Running codex review because it sounds like the obvious subcommand for a review taskUse codex exec -s read-only -C <dir> --skip-git-repo-check "<prompt>" — see registry
Dispatching the real (slow) external call before probingProbe first, short timeout — a dead tool costs 10-20 min discovered late vs. ~15s discovered early
Treating one failed external tool as a reason to abandon the whole external layerBest-effort: drop that tool for this round, disclose it, keep going with whatever did return
Blocking synchronously on an external tool callAlways background it — internal dimensions and other external tools shouldn't wait
Retrying a timed-out tool without checking for orphaned processes firsttasklist/ps check + explicit kill before any retry against the same output path
Silently downgrading to codex-only when agy is unavailableDisclose the drop and suggest installing Antigravity or substituting another external CLI agent — don't hide the reduced coverage

Cross-References

REQUIRED SUB-SKILL: the internal council dispatch is pr-council-review (skills/pr-council-review/SKILL.md) — this skill does not reimplement dimension detection, synthesis rules, or report shape, it wraps them.

Alternatives

Compare before choosing