santa-method

Verifies generated output through dual independent review agents with a convergence loop.

1|Updated Oct 11, 2025
One-click install
npx skills add https://github.com/ibytechaos/claude --skill santa-method-ibytechaos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: santa-method
Source: https://github.com/ibytechaos/claude/tree/main/plugins/everything-claude-code/skills/santa-method
Command: npx skills add https://github.com/ibytechaos/claude --skill santa-method-ibytechaos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? A single agent reviewing its own output shares the same biases and blind spots that produced the errors, so hallucinations, compliance violations, and factual mistakes slip into shipped content and code. ## Core Features & Use Cases - Dual Independent Review: Two context-isolated reviewer agents evaluate output against the same rubric, and both must pass before anything ships. - Convergence Loop: Failed outputs enter a fix-and-re-review cycle with fresh reviewers each round, capped at 3 iterations before human escalation. - Structured Rubrics: Objective pass/fail criteria for factual accuracy, hallucination detection, completeness, compliance, and technical correctness, with domain extensions for code, marketing, and regulated content. - Use Case: Before publishing 200 AI-generated product descriptions, run Santa Method on a 15% sample to catch systematic hallucinated claims, batch-fix the pattern, and re-verify until the sample passes clean. ## Quick Start Review this generated output using the Santa Method with two independent reviewers and a rubric covering factual accuracy and completeness.

Frequently Asked Questions about santa-method

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

FAQPage Schema
How do I verify AI-generated content for hallucinations before publishing?

Use dual independent review: spawn two reviewer agents with no shared context, give both the same rubric covering factual accuracy and hallucination checks, and ship only when both return PASS. Single self-review misses errors because the reviewer shares the generator's biases.

What is multi-agent adversarial verification?

Multi-agent adversarial verification runs two or more independent review agents against generated output, each instructed to find problems rather than approve. Both must pass for the output to ship, and failures trigger a fix-and-re-review loop with fresh reviewers each round.

When should I not use dual-agent output review?

Skip it for internal drafts, exploratory research, and tasks with deterministic verification like build, lint, or test pipelines. It is designed for output that ships to users, carries compliance risk, or has elevated hallucination risk such as statistics and API references.

How do I prevent infinite review loops in automated verification?

Cap iterations at a maximum of 3 rounds and escalate to a human when the cap is exhausted. Use rubrics with objective pass/fail criteria to prevent reviewers from flagging subjective style preferences that never converge.

Can I verify large batches of generated content without reviewing every item?

Yes, use stratified sampling: run full dual review on 10-15% of the batch with a minimum of 5 items, classify failures by type, apply targeted fixes to the whole batch when patterns emerge, then re-sample until a clean sample passes.