kill-argument

Generate a strongest rejection argument and adjudicate it against a theory paper's source text.

2|1|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/raja21068/AutoResearch --skill kill-argument-raja21068
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kill-argument
Source: https://github.com/raja21068/AutoResearch/tree/main/skills/aris/kill-argument
Command: npx skills add https://github.com/raja21068/AutoResearch --skill kill-argument-raja21068

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It identifies the single most damaging reason a paper could be rejected, then forces a point-by-point defense to reveal what is truly load-bearing versus what is merely claimed.

Core Features & Use Cases

  • Adversarial attack memo (~200 words): Produces a worst-case rejection paragraph that commits to the most lethal critique.
  • Independent adjudication and classification: Decomposes the attack into 3–7 atomic points and labels each as answered_by_current_text, partially_answered, or still_unresolved with evidence and recommended fixes.
  • Rebuttal- and submission-ready outputs: Writes KILL_ARGUMENT.md and a machine-readable KILL_ARGUMENT.json into the target paper directory for downstream planning.
  • Theory-paper focus: Most effective for papers with substantive theorem/lemma/proposition material where headline scope depends on proof obligations.

Quick Start

Run the kill-argument skill against your paper directory indicated by the argument variable $ARGUMENTS to generate KILL_ARGUMENT.md and KILL_ARGUMENT.json for adversarial review and defenses.

Frequently Asked Questions about kill-argument

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

FAQPage Schema
How do I stress-test a LaTeX theory paper before submission?

Stress-testing a LaTeX theory paper involves running an adversarial critique to generate a worst-case rejection argument, then adjudicating that attack point-by-point against your source text. This reveals whether your theorems and proofs truly support your claimed scope.

Can I use adversarial review to check if my theorem scope overclaims?

Adversarial review specifically decomposes a worst-case rejection into atomic points and labels each as answered_by_current_text, partially_answered, or still_unresolved. This classification exposes scope overclaims by validating whether your theorems and assumptions fulfill actual proof obligations.

What is the best way to prepare a rebuttal for unresolved reviewer attacks?

Rebuttal preparation requires identifying the most lethal critique and matching it against existing source text. By generating an attack memo and classifying each point by its resolution status, you get a machine-readable KILL_ARGUMENT.json for targeted downstream planning and fixes.

How does an independent reviewer thread find citation-evidence gaps in my paper?

An independent reviewer thread reads your relevant .tex and .bib files to locate citation-evidence gaps. It runs two fresh adversarial passes against your current text, isolating claims that lack supporting evidence and flagging them as still_unresolved for recommended fixes.

Does this adversarial critique method work for empirical papers without theorems?

Adversarial critique is most effective for theory papers with substantive theorem, lemma, or proposition material. Papers without formal proof obligations may not benefit fully, since the adjudication process specifically targets headline scope dependencies tied to mathematical assumptions.

What files do I need to run a point-by-point defense check on my research paper?

A point-by-point defense check requires your paper directory containing relevant .tex and .bib files, with an optional main.pdf. The process locates the LaTeX entry point, reads the source files, and outputs KILL_ARGUMENT.md plus KILL_ARGUMENT.json directly into that directory.