proof-review-adversarial

Stress-tests theorem-level and step-level proof claims for counterexamples and hidden gaps.

65|2|Updated Aug 10, 2026
One-click install
npx skills add https://github.com/DechenZhang/VALG-ML-Theory-Agent --skill proof-review-adversarial-dechenzhang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: proof-review-adversarial
Source: https://github.com/DechenZhang/VALG-ML-Theory-Agent/tree/main/skills/proof-review-adversarial
Command: npx skills add https://github.com/DechenZhang/VALG-ML-Theory-Agent --skill proof-review-adversarial-dechenzhang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Mathematical proofs assembled from multi-stage workflows can contain hidden gaps, unsupported scope upgrades, or counterexample-vulnerable claims that standard reviews miss. This Skill provides a final adversarial review pass that actively tries to break the weakest claims before a theorem candidate is accepted. ## Core Features & Use Cases - Adversarial Attack Surface Construction: Identifies the weakest theorem-level claims, assembly links, and step-level local units, then prioritizes obligations that would invalidate the theorem if false. - Stress-Case Testing: Tests claims against boundary regimes, degenerate cases, parameter extremes, and assumption-minimal examples, tracking convergence modes, explicit rate dependence, and notation provenance. - Repair Depth Localization: Classifies attacks as verified breaks, candidate counterexamples, or tentative concerns, and routes each blocking issue to the shallowest repair target (assembly, step, sketch, or idea). - Use Case: After assembling a LaTeX proof bundle from accepted proof steps, run this reviewer to verify the main theorem is self-contained, that no step exported an unproved invariant, and that simplified corollaries do not hide dropped dependencies. ## Quick Start Run the adversarial proof reviewer on the assembled LaTeX bundle and accepted step artifacts for perspective 1 idea 2 to produce proof_review_adversarial.md with a PASS or BLOCKING verdict.

Frequently Asked Questions about proof-review-adversarial

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

FAQPage Schema
How do I adversarially review a mathematical proof for hidden gaps?

Load the setting file, LaTeX bundle, assembly report, and accepted step artifacts, then build an attack surface targeting the weakest claims. Test them against boundary regimes, degenerate cases, and assumption-minimal examples, and classify findings as verified breaks, candidate counterexamples, or tentative concerns.

What does the proof-review-adversarial skill check in a theorem proof?

It checks target alignment, scope and convergence-mode upgrades, hidden subclaims, notation and assumption provenance, explicit rate dependence, baseline reduction behavior, and LaTeX bundle self-containedness. It also attacks step-level claims like PSD assertions, Taylor remainders, and illegal limit interchanges.

When should adversarial proof review run in the workflow?

It runs after proof assembly, once the LaTeX bundle, assembly report, accepted proof sketch, and all required step proofs and reviews exist. It is a diagnostic final reviewer and must not modify proofs, trackers, or accepted results.

What verdicts can an adversarial proof review produce?

The review emits PASS when no acceptance-blocking issue exists, or BLOCKING with numbered blocking issues, a suggested repair depth, and a smallest candidate repair target. Repair depths are assembly, step, sketch, or idea, aligned to the corresponding producer skill.

Can the adversarial reviewer use the global proof as evidence to accept a claim?

No. The global proof and its review are diagnostic context only for locating likely weak points. Neither artifact counts as proof evidence or authority to accept a final claim, and the assembly report is likewise status context only.