adversarial-review

Generate paired defender and attacker prompts for multi-model adversarial artifact review.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/blucsigma05/tbm-apps-script --skill adversarial-review-blucsigma05
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adversarial-review
Source: https://github.com/blucsigma05/tbm-apps-script/tree/main/.claude/skills/adversarial-review
Command: npx skills add https://github.com/blucsigma05/tbm-apps-script --skill adversarial-review-blucsigma05

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps teams run rigorous, multi-model adversarial reviews by producing paired defender/attacker prompts that enforce the same evidence bar and round protocol, reducing rhetoric and unsourced claims.

Core Features & Use Cases

  • Paired defender vs. rival prompt generation for plan, spec, or artifact stress-testing across models
  • Evidence symmetry (Truth + Authenticity + Clarity) so both sides must meet an identical standard
  • Round-based protocol with plan_diff to converge on concrete diffs instead of vague commentary

Quick Start

Ask for adversarial review prompts by stating the artifact path, the defender model and role, the rival model(s) and attack angle(s), the exact evidence standard, and the measurable exit condition for when the loop ends.

Frequently Asked Questions about adversarial-review

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

FAQPage Schema
How do I generate adversarial review prompts for multi-model plan stress-testing?

Adversarial review prompts are generated by defining an artifact path, defender and rival models, attack angles, evidence standards, and exit conditions to produce paired defender and attacker prompts for multi-model evaluation.

What is evidence symmetry in multi-model adversarial evaluation?

Evidence symmetry enforces identical standards for Truth, Authenticity, and Clarity across both defender and attacker roles, ensuring both sides meet the same evidence bar to reduce rhetoric and unsourced claims.

How do I enforce a round-based protocol with plan diffs during a spec audit?

A round-based protocol with plan diffs is enforced by iterating through attacker and defender rounds until a measurable exit condition is met, converging on concrete diffs and counter_proposal tags instead of vague commentary.

Can I use different evidence standards for the defender and attacker models?

No, you cannot use different evidence standards. The protocol requires an identical TACT canon and forbidden-moves lists across roles, strictly enforcing evidence symmetry to prevent biased or unsourced claims.

What information do I need to provide to start an artifact stress-test?

To start an artifact stress-test, provide the artifact path, defender model and role, rival model(s) and attack angle(s), exact evidence standard, and the measurable exit condition for the loop.

Does multi-model adversarial review work without a predefined exit condition?

No, a predefined measurable exit condition is required. The adversarial loop iterates by rounds, classifying claims and attacking or rationalizing them until the explicit exit condition is satisfied.