Generate venue-compliant rebuttals from reviewer feedback with provenance constraints.
npx skills add https://github.com/Shallow-W/llm-wiki --skill rebuttal-shallow-w
Please help me install this Agent Skill. Skill: rebuttal Source: https://github.com/Shallow-W/llm-wiki/tree/main/.claude/skills/rebuttal Command: npx skills add https://github.com/Shallow-W/llm-wiki --skill rebuttal-shallow-w
Reviews often arrive with multiple, overlapping concerns, and authors need a venue-compliant rebuttal that answers every issue without inventing evidence or making unapproved promises.
Use the rebuttal skill to draft a text-only ICML rebuttal by providing the paper path or review bundle and the target venue/limits.
High-intent search queries and answers about installing and using this skill.
Drafting an ICML rebuttal requires parsing reviewer feedback into atomized issues and generating a venue-compliant response. This process normalizes concerns into an actionable board with severity and priority, then drafts text that respects strict limits and provenance constraints.
Managing overlapping concerns in an OpenReview response involves atomizing reviewer feedback into distinct issues. Each issue is assigned a response mode and priority, ensuring every factual statement is traceable and every commitment is approved without inventing evidence.
Yes, you can generate per-reviewer thread responses that are self-contained instead of a single shared rebuttal document. The drafting process supports both single-document and per-reviewer thread formats while enforcing coverage and commitment gates.
Tracking changes across multiple rebuttal rounds uses follow-up round management to monitor deltas. It maintains an auditable revision checklist, ensuring subsequent rounds remain compliant and properly address reviewer deltas with safety validation.
Stress-testing a rebuttal identifies weak coverage, unsupported claims, tone issues, and backfiring phrasing. This validation process checks the draft against evidence grounding rules to ensure no fabricated evidence is introduced and all claims are properly supported.
Generating a rebuttal requires YAML-defined inputs including the paper path, review bundle, venue rules, and current stage. These inputs enforce provenance and commitment gates to produce paste-ready or thread-ready rebuttal artifacts.
jkfeeAlign external reviews with a structured rebuttal workflow and draft artifacts.
lightrain-aParse external reviews and draft venue-compliant rebuttals with provenance gates.
zhuyingqinGenerate venue-compliant rebuttal drafts from paper source and reviewer feedback.
catlog22Parse reviewer comments and generate structured rebuttal and revision plans.
