kill-argument

Generate a hostile reviewer rejection memo and adjudicate defenses for LaTeX papers.

Updated May 20, 2026
One-click install
npx skills add https://github.com/lightrain-a/medtrace-aris --skill kill-argument
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kill-argument
Source: https://github.com/lightrain-a/medtrace-aris/tree/main/.vendor/aris/skills/kill-argument
Command: npx skills add https://github.com/lightrain-a/medtrace-aris --skill kill-argument

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you identify the single most damaging reviewer argument that could sink your paper, then verifies whether the current text actually answers it.

Core Features & Use Cases

  • Adversarial attack memo generation: Produces a ~200-word “strongest rejection paragraph” written by a hostile reviewer focusing on the most vulnerable claim (e.g., scope overreach, missing proof obligations, assumption–claim mismatch).
  • Independent defense adjudication: Decomposes the attack into 3–7 points and classifies each as answered, partially answered, or still unresolved using only the current paper source.
  • Actionable remediation guidance: Surfaces the highest-priority fixes based on unresolved (especially critical) attack points.

Use cases: theory/theorem-heavy papers before submission, rebuttal preparation to anticipate “reviewer-2”-style objections, and post-standard-review stabilization to close headline-vs-body gaps.

Quick Start

Run kill-argument on your paper directory path so it outputs KILL_ARGUMENT.md and KILL_ARGUMENT.json after running an attack-then-defense review on your LaTeX sources.

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 theory paper for reviewer rejection before submission?

An adversarial review generates a hostile reviewer's strongest rejection memo and adjudicates whether your current LaTeX source text successfully defends against each attack point, surfacing critical remediation guidance for unresolved vulnerabilities.

What is the best way to prepare a LaTeX rebuttal for reviewer-2 objections?

The best way to prepare a rebuttal is by simulating a worst-case rejection on your paper directory, which decomposes a hostile attack into 3-7 points and classifies each as answered, partially answered, or unresolved using your current source files.

Can I use this adversarial review process on papers without formal proofs?

This adversarial review process specifically targets theory or scope-sensitive papers where the headline depends on theorems, lemmas, assumptions, and proof obligations, making it unsuitable for papers lacking these formal mathematical structures.

How do I check if my paper has missing proof obligations or scope overreach?

To check for missing proof obligations, run a two independent fresh-reviewer analysis on your paper directory, which evaluates vulnerability to scope overreach and assumption-claim mismatches before outputting a structured KILL_ARGUMENT.md and KILL_ARGUMENT.json report.

Does the scope validation review require specific LaTeX files or dependencies?

This scope validation review requires reading the LaTeX entry and associated .tex sources from your provided paper directory, optionally including main.pdf, and operates without external dependencies to generate its attack and defense adjudication reports.