rebuttal
Workflow 4: Submission rebuttal pipeline. Parses external reviews, enforces coverage and grounding, drafts a safe text-only rebuttal under venue limits, and manages follow-up rounds
Install / Use
npx skills add wanshuiyin/Auto-claude-code-research-in-sleep --skill rebuttalInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
AutomationSupported Platforms
Our assessment of rebuttal
rebuttal scores 96/100 on our quality scale, 180th of 2,780 Automation skills we index (top 7%).
Its SKILL.md is 24 KB long, well organised into 21 sections with 3 code examples: a thorough specification that gives an agent plenty to work with.
With 19,197 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated 2 days ago, so rebuttal is actively maintained.
- Our last check on 2026-11-14 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-09-28. Automated pattern scan on 2026-09-28. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
rebuttal compared with similar skills
All 4 of these similar skills score higher than rebuttal; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| rebuttal (this skill)by wanshuiyin | 96 | 19.2k | 2d ago | SKILL.md |
| Agent-Reachby Panniantong | 100 | 112.3k | 8d ago | CLAUDE.md |
| rufloby ruvnet | 100 | 81.9k | today | CLAUDE.md |
| headroomby headroomlabs-ai | 100 | 79.8k | today | CLAUDE.md |
| CowAgentby zhayujie | 100 | 48.0k | today | CLAUDE.md |
Frequently asked questions
- How do I install rebuttal?
- Run
npx skills add wanshuiyin/Auto-claude-code-research-in-sleep --skill rebuttal. The install tabs above show the steps for each supported agent. - Which AI agents does rebuttal work with?
- It is written for OpenAI Codex, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is rebuttal safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is rebuttal still maintained?
- The repository was last updated 2 days ago, so rebuttal is actively maintained.
Skill content
View source on GitHubname: rebuttal description: "Workflow 4: Submission rebuttal pipeline. Parses external reviews, enforces coverage and grounding, drafts a safe text-only rebuttal under venue limits, and manages follow-up rounds. Use when user says "rebuttal", "reply to reviewers", "ICML rebuttal", "OpenReview response", or wants to answer external reviews safely." argument-hint: "[paper-path-or-review-bundle]" allowed-tools: Bash(*), Read, Grep, Glob, Write, Edit, Skill, mcp__codex__codex, mcp__codex__codex-reply, mcp__manual_review__review, mcp__manual_review__review_reply
Workflow 4: Rebuttal
Prepare and maintain a grounded, venue-compliant rebuttal for: $ARGUMENTS
Scope
This skill is optimized for:
- text-only rebuttal under strict character/word limits (e.g. ICML single-document)
- per-reviewer thread responses where each reviewer renders independently (e.g. OpenReview-style)
- multiple reviewers with shared and reviewer-specific concerns
- follow-up rounds after the initial rebuttal
- safe drafting with no fabrication, no overpromise, and full issue coverage
This skill does not:
- run new experiments automatically
- generate new theorem claims automatically
- edit or upload a revised PDF
- submit to OpenReview / CMT / HotCRP
If the user already has new results, derivations, or approved commitments, the skill can incorporate them as user-confirmed evidence.
Lifecycle Position
Workflow 1: idea-discovery
Workflow 1.5: experiment-bridge
Workflow 2: auto-review-loop (pre-submission)
Workflow 3: paper-writing
Workflow 4: rebuttal (post-submission external reviews)
Constants
- VENUE =
ICML— Default venue. Override if needed. - RESPONSE_MODE =
TEXT_ONLY— v1 default. - REVIEWER_MODEL =
gpt-6-astra— Default model for the Codex backend. Used for internal stress-testing. Manual backend uses a model the user chooses — it must be a recognized model from a different family (OpenAI, Anthropic, Google, DeepSeek, Moonshot/Kimi, Qwen). - REVIEWER_BACKEND =
codex— Default: Codex MCP (xhigh). Override with— reviewer: oracle-profor Oracle MCP, or— reviewer: manualfor Manual Review MCP. If manual-review MCP is unavailable, stop and print the install command; do not fall back to Codex. Seeshared-references/reviewer-routing.md. - MAX_INTERNAL_DRAFT_ROUNDS = 2 — draft → lint → revise.
- VENUE_MODE =
single_document—single_documentfor one shared author response, orper_reviewer_threadwhen each reviewer thread renders independently. Confirm the venue/interface before drafting if unclear. Affects Phase 4/7 output shape. - STRESS_TEST_ROUNDS_BASE = 1 — One external reviewer critique round on the full response set. Add focused rounds for
reviewer_priority: pivotalresponses, terminating when the reviewer returns no new substantive issues. Hard cap at 5. - MAX_FOLLOWUP_ROUNDS = 3 — per reviewer thread.
- AUTO_EXPERIMENT = false — When
true, automatically invoke/experiment-bridgeto run supplementary experiments when the strategy plan identifies reviewer concerns that require new empirical evidence. Whenfalse(default), pause and present the evidence gap to the user for manual handling. - QUICK_MODE = false — When
true, only run Phase 0-3 (parse reviews, atomize concerns, build strategy). OutputsISSUE_BOARD.md+STRATEGY_PLAN.mdand stops — no drafting, no stress test. Useful for quickly understanding what reviewers want before deciding how to respond. - REBUTTAL_DIR =
rebuttal/ - RENDER_HTML = true — When
true(default), auto-renderrebuttal/REBUTTAL_DRAFT_rich.md(the detailed reviewer-facing draft) to HTML after Phase 6 / Phase 8 finalization. Uses full Codex review gate (final pre-submission deliverable — reviewer-facing content, render fidelity matters). The plain-textPASTE_READY.txtis NOT rendered (it's character-counted plain text by design). Setfalseto skip, or pass— render html: false.
Override:
/rebuttal "paper/" — venue: NeurIPS, character limit: 5000
Reviewer Calling Convention
When calling the reviewer for stress-testing, branch on REVIEWER_BACKEND:
If REVIEWER_BACKEND = codex:
Use mcp__codex__codex for new review threads.
Use mcp__codex__codex-reply for follow-up rounds (reuse threadId).
If REVIEWER_BACKEND = manual:
Use mcp__manual_review__review for new review threads with:
prompt: [exact same prompt that would go to Codex]
config: {"model_reasoning_effort": "xhigh", "executor_model": "<actual executor model>", "require_reviewer_model": true}
Save the returned threadId.
Use mcp__manual_review__review_reply for follow-up rounds with:
threadId: [saved manual-review threadId]
prompt: [follow-up prompt]
config: {"model_reasoning_effort": "xhigh", "executor_model": "<actual executor model>", "require_reviewer_model": true}
Prompt fidelity: the manual prompt must be exactly the same text that Codex would receive. Review tracing applies equally to both backends.
Required Inputs
- Paper source — PDF, LaTeX directory, or narrative summary
- Raw reviews — pasted text, markdown, or PDF with reviewer IDs
- Venue rules — venue name, character/word limit, text-only or revised PDF allowed, rendering mode (one shared response or independent reviewer threads)
- Current stage — initial rebuttal or follow-up round
If venue rules, limit, or rendering mode are missing, stop and ask before drafting.
Safety Model
Three hard gates — if any fails, do NOT finalize:
- Provenance gate — every factual statement maps to:
paper,review,user_confirmed_result,user_confirmed_derivation, orfuture_work. No source = blocked. - Commitment gate — every promise maps to:
already_done,approved_for_rebuttal, orfuture_work_only. Not approved = blocked. - Coverage gate — every reviewer concern ends in:
answered,deferred_intentionally, orneeds_user_input. No issue disappears.
Workflow
Phase 0: Resume or Initialize
- If
rebuttal/REBUTTAL_STATE.mdexists → resume from recorded phase - Otherwise → create
rebuttal/, initialize all output documents - Load paper, reviews, venue rules, any user-confirmed evidence
Phase 1: Validate Inputs and Normalize Reviews
- Validate venue rules are explicit
- Normalize all reviewer text into
rebuttal/REVIEWS_RAW.md(verbatim) - Record metadata in
rebuttal/REBUTTAL_STATE.md - If ambiguous, pause and ask
Phase 2: Atomize and Classify Reviewer Concerns
Create rebuttal/ISSUE_BOARD.md.
For each atomic concern:
issue_id(e.g., R1-C2)reviewer,round,raw_anchor(short quote)issue_type: assumptions / theorem_rigor / novelty / empirical_support / baseline_comparison / complexity / practical_significance / clarity / reproducibility / otherseverity: critical / major / minorreviewer_stance: positive / swing / negative / unknownreviewer_priority: standard / pivotalpivotal— a reviewer whose response is likely to affect the decision if addressed well: low or borderline rating, addressable concerns, and enough confidence/influence to matter. Phase 3 allocates extra drafting and stress-test budget here.
response_mode: direct_clarification / grounded_evidence / nearest_work_delta / assumption_hierarchy / narrow_concession / future_work_boundary / structural_distinctionstructural_distinction— for "your method reduces to X / is just generic Y / is subsumed by Z" attacks. Pattern: agree on the local reduction; show the structural feature your parameterization preserves that X/Y/Z does not capture, backed by a concrete mechanism (theorem dependency, derivation step, or empirical consequence). Never use rhetorically without the supporting mechanism.
status: open / answered / deferred / needs_user_input
Phase 3: Build Strategy Plan
Create rebuttal/STRATEGY_PLAN.md.
- Identify 2-4 global themes resolving shared concerns
- Choose response mode per issue
- Build character budget (10-15% opener, 75-80% per-reviewer, 5-10% closing) — applies in
single_documentmode; inper_reviewer_threadmode, set per-thread word/char targets instead - Identify pivotal reviewer(s) — reviewers whose vote or confidence shift would most affect the decision, especially when concerns are addressable rather than ideological. Mark them
reviewer_priority: pivotalinISSUE_BOARD.md. There may be more than one. Allocate disproportionate drafting + stress-test budget here. - Identify blocked claims (ungrounded or unapproved)
- If unresolved blockers → pause and present to user
A verdict-bearing manual response MUST begin with
Reviewer-Model: <exact-model-id>— pass the model THIS session is actually running as inexecutor_model. Missing, unknown, or same-family identity cannot acquit; emitREVIEW_UNAVAILABLErather than guessing. If the executor model cannot be named, manual review's cross-family claim is unprovable — say so in the report instead of asserting it.
QUICK_MODE exit: If QUICK_MODE = true, stop here. Present ISSUE_BOARD.md + STRATEGY_PLAN.md to the user and summarize: how many issues per reviewer, shared vs unique concerns, recommended priorities, and evidence gaps. The user can then decide to continue with full rebuttal (/rebuttal — quick mode: false) or write manually.
Phase 3.5: Evidence Sprint (when AUTO_EXPERIMENT = true)
Skip entirely if AUTO_EXPERIMENT is false — instead, pause and present the evidence gaps to the user.
If the strategy plan identifies issues that require new empirical evidence (tagged response_mode: grounded_evidence with evidence_source: needs_experiment):
-
Generate a mini experiment plan from the reviewer concerns:
- What to run (ablation, baseline comparison, scale-up, condition check)
- Success criterion (what result would satisfy the reviewer)
- Estimated GPU-hours
-
Invoke
/experiment-bridgewith the mini plan:/experiment-bridge "rebuttal/REBUTTAL_EXPERIMENT_PLAN.md" -
Wait for results, then update
ISSUE_BOARD.md:- Tag completed experiments as
user_confirmed_result - Update evidence source for relevant issue cards
- Tag completed experiments as
-
If experiments fail or are inconclusive:
- Switch response mode to
narrow_concessionorfuture_work_boundary - Do NOT fabricate positive results
- Switch response mode to
-
Save experiment results to
rebuttal/REBUTTAL_EXPERIMENTS.mdfor provenance tracking.
Time guard: If estimated GPU-hours exceed rebuttal deadline, skip and flag for manual handling.
Phase 4: Draft Initial Rebuttal
Create the draft artifact(s) per VENUE_MODE:
single_documentmode → onerebuttal/REBUTTAL_DRAFT_v1.mdper_reviewer_threadmode → onerebuttal/Reviewer_<ID>_response.mdper reviewer (no top-levelREBUTTAL_DRAFT_v1.md)
Structure depends on VENUE_MODE:
-
single_document— oneREBUTTAL_DRAFT_v1.md:- Short opener — thank reviewers + 2-4 global resolutions
- Per-reviewer numbered responses — answer → evidence → implication
- Short closing — resolved / remaining / acceptance case
-
per_reviewer_thread— one self-containedReviewer_<ID>_response.mdper reviewer:- Brief acknowledgment of that reviewer's main thrust
- Numbered W#/Q# responses (answer → evidence → implication)
- Optional shared experimental-setup paragraph (see "Reusable setup block" below)
- Each file must be readable standalone. No "see Reviewer X's response" references. No global opener.
Default reply pattern per issue:
- Sentence 1: direct answer
- Sentence 2-4: grounded evidence
- Last sentence: implication for the paper
Reusable setup block (per_reviewer_thread mode).
If multiple reviewer-thread responses need the same experimental setup or metric definitions, write a canonical SETUP_METRICS_BLOCK.md. Reuse it consistently i
Truncated for display — read the full file on GitHub.
Related Skills
Agent-Reach
112.3kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
ruflo
81.9k🌊 The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory, self-learning intelligence, federation, vector RAG integration, and native Claude Code / Codex / Hermes and many more Integrated
headroom
79.8kCompress tool outputs, logs, files, and RAG chunks before they reach the LLM. 20% fewer tokens for coding agents, 60-95% fewer tokens for JSON, same answers. Library, proxy, MCP server.
CowAgent
48.0kOpen-source personal AI assistant & Agent Harness. Plans tasks, runs tools and skills, self-evolves with memory and knowledge. Multi-agent, multi-model, multi-channel. Lightweight, extensible, one-line install.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
