fanout-pattern

Fan one question out across two Bots and merge answers with dissent preserved.

Updated Sep 11, 2026
One-click install
npx skills add https://github.com/JYeswak/grok_bot_playground --skill fanout-pattern-jyeswak
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fanout-pattern
Source: https://github.com/JYeswak/grok_bot_playground/tree/main/plugin/skills/fanout-pattern
Command: npx skills add https://github.com/JYeswak/grok_bot_playground --skill fanout-pattern-jyeswak

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Single-Bot answers hide disagreement, and a lone answer can be wrong without anyone noticing. This Skill cross-checks one question across two documented Bots and merges the results with citations, so agreement, dissent, and abstentions are all visible instead of averaged away. ## Core Features & Use Cases - Two-Bot fan-out: Run the same verbatim question through two documented Bots and capture each answer with its source and date. - Citation-gated merge: Agreement counts only with dual citations, dissent is quoted with sources, and a sourceless 1-1 split is marked UNRESOLVED rather than tie-broken. - Dissent spotlight: Surface the single disagreement that most needs the reader's attention, with both citations attached. - Use Case: Before acting on a claim from one Bot, run a cross-check run across two Bots and get a dated verdict showing where they agree, where they diverge, and what could not be verified. ## Quick Start Ask the assistant to cross-check a specific claim across two named Bots using the fan-out pattern and return a merged verdict with citations.

Frequently Asked Questions about fanout-pattern

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

FAQPage Schema
How do I cross-check a claim across two Bots?

State the claim as one verbatim question, name two documented Bots, and agree on merge rules up front. Run the same question through both Bots, then merge: dual-cited agreement, quoted dissent, recorded abstentions, and UNRESOLVED for sourceless splits.

How do I compare answers from two Bots without losing disagreement?

Use a fan-out merge that keeps every answer attached to its Bot, date, and source. Agreement is reported as both Bots said X with citations, dissent is quoted with sources, and the merge adds no new claims of its own.

Can I fan out a question to more than two Bots at once?

No. This pattern is scoped to exactly two Bots per run. It also excludes undocumented or experimental agents, chained workflows, and anything that sends, posts, or publishes.

What happens when the two Bots disagree with no clear source advantage?

A 1-1 split with no source edge is marked UNRESOLVED. It is never tie-broken by preference or eloquence, and the verdict explains why the question could not be settled.

What if one Bot is unreachable or refuses to answer?

An unreachable Bot is recorded as unreachable, never simulated or substituted. A Bot that abstains on a question records an abstention, which is treated as a finding rather than a failure.