kill-argument

Runs a two-thread adversarial review that attacks a theory paper's headline claims and adjudicates each rejection point.

Updated Jul 9, 2026
One-click install
npx skills add https://github.com/Lingjie-wang/autoRL --skill kill-argument-lingjie-wang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kill-argument
Source: https://github.com/Lingjie-wang/autoRL/tree/main/Auto-claude-code-research-in-sleep/skills/kill-argument
Command: npx skills add https://github.com/Lingjie-wang/autoRL --skill kill-argument-lingjie-wang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Standard score-based paper reviews produce balanced weakness lists that never commit to the single most damaging rejection argument a hostile reviewer would write. This Skill stress-tests a LaTeX theory paper by forcing one fresh reviewer to write the strongest ~200-word rejection memo, then having a second independent reviewer adjudicate each atomic rejection point against the current source. ## Core Features & Use Cases - Adversarial attack memo: A fresh cross-model reviewer (gpt-5.5 via Codex MCP, zero prior context) constructs the single strongest rejection paragraph targeting theorem validity, scope overclaim, missing proof obligations, and claim-vs-evidence gaps. - Point-by-point adjudication: A second fresh reviewer decomposes the attack into 3-7 atomic points and classifies each as answered_by_current_text, partially_answered, or still_unresolved, with file:line evidence and severity. - Computed verdict ledger: The skill maps per-point counts to a PASS/WARN/FAIL/NOT_APPLICABLE/BLOCKED/ERROR verdict and writes KILL_ARGUMENT.md, KILL_ARGUMENT.json, and optional HTML, with sha256 input hashes for staleness detection. - Use Case: Before submitting a NeurIPS theory paper that has plateaued at 7-8/10 in standard review rounds, run the kill-argument exercise to surface the headline-vs-body scope gap a senior area chair would seize on, then prepare rebuttal responses in advance. ## Quick Start Run the kill-argument adversarial review on my paper directory to find the strongest rejection argument and check whether the current text answers it.

Frequently Asked Questions about kill-argument

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

FAQPage Schema
How do I simulate a hostile reviewer before submitting a paper?

Run the kill-argument skill on your paper directory. It spawns a fresh reviewer thread that writes the single strongest ~200-word rejection memo, then a second independent thread that defends the paper point-by-point and surfaces still-unresolved critical issues.

What is the difference between adversarial review and standard peer review?

Standard reviews produce balanced weakness lists ranked by severity without committing. Adversarial review forces the reviewer to pick the single most damaging rejection argument, which empirically surfaces scope-overclaim and headline-vs-body gaps that score-based reviews miss.

When should I run a kill-argument check on a paper?

Run it after one or two standard improvement rounds have settled at a stable score, before submission or during rebuttal preparation. It works best for theory papers with at least five theorem-class environments; empirical papers without theorems should use a standard deep review instead.

Does the adversarial review modify my paper files?

No. Direct invocation is detect-only: it writes KILL_ARGUMENT.md and KILL_ARGUMENT.json reports but never edits paper sources. When invoked from an auto-improvement loop, the loop separately consumes the JSON and applies fixes.

Why does the review use fresh threads instead of continuing a conversation?

Fresh threads enforce zero prior context so neither the attacker nor the adjudicator sees earlier reviews, fix lists, or summaries. This prevents bias toward optimism and ensures the adjudicator reads the paper as a genuinely independent reviewer would.

When should I not use adversarial kill-argument review?

Skip it for empirical papers without theorems or scope claims, very early drafts with unstable headlines, and papers with ongoing experiments. The skill emits NOT_APPLICABLE or BLOCKED verdicts in these cases rather than producing a misleading attack.