santa-method

Enforce independent dual review with a strict PASS gate before shipping outputs.

Updated Sep 13, 2025
One-click install
npx skills add https://github.com/llmh333/employee_management_spring --skill santa-method-llmh333
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: santa-method
Source: https://github.com/llmh333/employee_management_spring/tree/main/.gemini/skills/santa-method
Command: npx skills add https://github.com/llmh333/employee_management_spring --skill santa-method-llmh333

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill reduces the risk of publishing incorrect or hallucinated outputs by forcing an adversarial, two-reviewer verification step before anything ships.

Core Features & Use Cases

  • Independent Dual Review: Two separate reviewers check the same output using the same rubric, without shared context.
  • Structured Verdict Gate: Reviewers must return PASS/FAIL plus concrete issues, with both having to pass to proceed.
  • Fix-Until-Nice Convergence Loop: Iteratively fixes only the flagged critical issues and re-runs both reviewers until convergence or escalation.
  • When to Use: Best for production-bound content, compliance-sensitive writing, technical documentation, and high-stakes claims where accuracy matters.

Quick Start

Use the santa-method skill to verify a draft output by running two independent reviewers against the same rubric and shipping only if both return PASS.

Frequently Asked Questions about santa-method

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

FAQPage Schema
How do I prevent hallucinated content from shipping in technical documentation?

Independent dual review prevents hallucinated content in technical documentation by forcing two context-isolated reviewers to evaluate the same output against an identical rubric, shipping only if both return a strict PASS verdict.

What is the best way to verify compliance-sensitive messaging for accuracy?

Verifying compliance-sensitive messaging for accuracy is best handled by an adversarial two-reviewer verification step, where isolated reviewers check the same output against an identical rubric and return structured PASS or FAIL verdicts with concrete issues.

How do I run a convergence loop for quality assurance on production-bound content?

To run a quality assurance convergence loop on production-bound content, iteratively fix only the flagged critical issues and re-run both reviewers until they pass or escalation occurs, ensuring accuracy through structured convergence.

Does dual review verification work for high-stakes claims without shared reviewer context?

Yes, dual review verification works for high-stakes claims by intentionally keeping reviewers context-isolated. Without shared context, two separate reviewers evaluate the same output against an identical objective rubric to ensure strict accuracy.

When should I not use an independent dual review gate for content verification?

You should not use an independent dual review gate for low-stakes or rapidly iterated content where speed matters more than strict accuracy. It is designed for production-bound content, compliance-sensitive writing, and technical documentation.