jury

Verifies a single claim by spawning parallel subagents that attempt to refute it and tallying their votes.

1|Updated Jun 1, 2026
One-click install
npx skills add https://github.com/kridaydave/My_Skills --skill jury-kridaydave
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: jury
Source: https://github.com/kridaydave/My_Skills/tree/main/jury
Command: npx skills add https://github.com/kridaydave/My_Skills --skill jury-kridaydave

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Plausible-but-wrong findings survive when nobody's job is to refute them. This Skill stress-tests one specific claim by spawning multiple independent skeptic subagents whose explicit mandate is to break it, then applies a refute-vote so you only act on claims that withstand adversarial attack. ## Core Features & Use Cases - Blind parallel skeptics: Dispatches N subagents in one batch, each isolated from the others and each instructed to refute the claim, defaulting to "refuted" when uncertain. - Adjustable kill threshold: Choose lenient (majority-refute kills), strict (zero refutes allowed), or supermajority bars, with jury sizes of 3, 5, or 7 matched to the stakes. - Distinct attack lenses: Optionally assign each juror a different angle — correctness, reproducibility, counterexample, security — so diverse failure modes get caught. - Use Case: Before gating an expensive training run on the premise "the data pipeline deduplicates correctly," run 5 jurors at a strict bar; if even one produces a counterexample, you fix the pipeline first instead of wasting the run. ## Quick Start Ask the AI to jury the claim "the login fix resolves the timeout bug" with 5 jurors at a strict bar before deploying it.

Frequently Asked Questions about jury

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

FAQPage Schema
How do I verify a claim with AI subagents before acting on it?▼

State the claim precisely, then dispatch multiple parallel subagents whose explicit job is to refute it, each blind to the others. Tally their structured verdicts and apply a preset threshold: the claim survives only if fewer than the majority refute it.

What is adversarial verification of AI-generated findings?▼

Adversarial verification means each checking agent is mandated to break the claim, not give a balanced assessment, and defaults to "refuted" when uncertain. A claim that survives several honest attempts to kill it is far more trustworthy than one that merely sounds plausible.

How many jurors should I use to fact-check a claim?▼

Use 3 jurors for a quick check, 5 for a real verification, and 7 when a wrong "survives" verdict is costly. Odd numbers avoid ties, and each juror is a full subagent, so size the panel to the stakes of the decision.

When should I not use a refute-vote panel to check a claim?▼

Skip it for vague or unfalsifiable claims, which get refuted on technicalities or survive on ambiguity; sharpen the claim first. It is also wasteful for low-stakes checks where a single direct test would settle the question faster.

Why must skeptic subagents run in parallel and blind?▼

Serial jurors leak context and bias later verdicts, defeating the purpose of a vote. Each juror must see only the claim and minimal test context, never another verdict or the running tally, so the votes stay independent.