rebuttal

Parse external reviews and draft venue-compliant rebuttals with provenance gates.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you transform external reviewer feedback into a venue-compliant rebuttal that covers every concern using only grounded, provenance-backed statements.

Core Features & Use Cases

  • Review parsing and issue atomization: Converts raw reviews into an ISSUE_BOARD with per-issue metadata (type, severity, stance, and priority).
  • Grounded strategy planning: Produces a STRATEGY_PLAN that sets global themes, character/word budgeting, and evidence gaps (with a QUICK_MODE that stops before drafting).
  • Safe drafting with strict gates: Drafts a text-only rebuttal (single-document or per-reviewer threads) while enforcing provenance, commitment, and full coverage rules.
  • Follow-up maintenance: Tracks follow-up rounds in stateful artifacts and updates a revision checklist rather than rewriting blindly.

Quick Start

Use the rebuttal skill to generate a rebuttal for your paper and pasted reviewer text within the ICML character limit.

Frequently Asked Questions about rebuttal

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

FAQPage Schema
How do I write an ICML rebuttal that stays within the character limit and addresses every reviewer concern?

To write an ICML rebuttal within the character limit, you need to parse reviewer feedback into discrete issues, allocate word budgets, and draft text-only responses with strict provenance enforcement to ensure full coverage of every concern.

Can I generate per-reviewer thread responses for OpenReview?

Yes, you can generate per-reviewer thread responses for OpenReview by parsing external reviews into an issue board and drafting safe, grounded replies tailored to each individual reviewer's specific comments.

What is the best way to ensure an academic rebuttal only uses provenance-backed claims?

The best way to ensure an academic rebuttal uses provenance-backed claims is to enforce strict drafting gates that prevent generating statements unless they are directly grounded in the provided paper inputs and external review evidence.

How do I track follow-up rebuttal rounds without rewriting the entire response?

To track follow-up rounds without rewriting, maintain persisted stateful artifacts and update a revision checklist that logs new issues and strategies, preserving the original grounded responses while appending necessary follow-up maintenance.

Do I need to provide explicit venue rules and limits to draft a reviewer response?

Yes, you must provide explicit venue rules, character limits, paper inputs, and raw review text to accurately generate a venue-compliant reviewer response that adheres to specific formatting and coverage requirements.

What happens if my academic rebuttal drafting is missing supporting evidence for a claim?

If drafting is missing supporting evidence for a claim, the process pauses to flag the evidence gap within the strategy plan, ensuring no ungrounded statements are written until the required proof is supplied.