agentleFS
NilsHellwigNilsHellwig/acl-paper-skills/skills/rebuttal/SKILL.md

rebuttal

Skill3 starsChanged 15 days agoMITView on GitHub

Plan and draft the ARR author response from the reviews in reviews/, following the current ARR author guidelines. Writes rebuttal.md.

15 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use daily-arxiv, exp-eval and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • LambenthanSkill

    daily-arxiv

    每日从 arXiv 拉取新论文,过滤相关性,auto-ingest 高优先级论文,检测 SOTA 更新

    Also in 5 projects that use this

  • LambenthanSkill

    exp-eval

    实验判决门:Review LLM 独立评判实验结果 → 4 种判决路径 → 自动更新 claims confidence、ideas status、graph edges

    Also in 5 projects that use this

  • skyllwtSkill

    exp-pilot-eval

    Pilot result evaluation — read pilot results, apply success criteria, update idea page (pilot_result, failure_reason if failed), generate PILOT_VERDICT_REPORT. Called by /ideate Phase 5 after /exp-pilot-run.

    Also in 4 projects that use this

  • skyllwtSkill

    exp-pilot-run

    Pilot experiment execution — read Pilot Spec YAML, write pilot code, run experiment(Confirm with the user before operation and require the applicant to conduct manual inspection), return results. Called by /ideate Phase 5. Does NOT modify wiki pages or judge pass/fail.

    Also in 4 projects that use this

  • phanghonghaoSkill

    poster

    HTML/CSS A4 海报生成。从沙龙/活动 Markdown 文件生成科技风 A4 海报 PDF/PNG。Use when user mentions: poster, 海报, 海报生成, make poster, generate poster, 活动海报, 沙龙海报.

    Also in 4 projects that use this

  • +6 more from Lambenthan
  • +1 more from skyllwt

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 13 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Add a general response for points several reviewers share, if the fetched rules allow one.

    line 32

“Common” is measured: kept by at least 6 in 10 of the 13 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

This skill is ARR-only. When paper.config.json has venue semeval, say that SemEval has no ARR response process and stop.

Help the authors answer their reviews. The authors decide what to concede, what to argue and what to promise; this skill organizes the reviews, checks each point against the paper and drafts the answers.

PK means python3 ${CLAUDE_PLUGIN_ROOT}/scripts/paperkit.py, run from the project root.

1. Inputs

  • Reviews and meta-review: one file per review in reviews/ (R1.md, R2.md, ..., meta.md), pasted from OpenReview. No folder yet: create it and ask the user to paste the reviews.
  • Rules: run PK guidelines rebuttal. It fetches the ARR author guide (the section on responding to reviews, and on reporting review issues) and the reviewer guidelines. On ⚠️ say which rules are missing. Read the response section in full: length limits, what may and may not go in a response, how the process works this cycle. A limit the user gives in the argument wins.
  • Context: ask with AskUserQuestion what the files do not show: the response deadline and format (OpenReview comment per reviewer, general response, character limit), whether new experiments can still be run, and whether this is a resubmission (then also the previous reviews and how they were addressed).

2. Triage

Split every review into atomic points. For each point record: reviewer, quote, type (misunderstanding, missing experiment, missing related work, clarity, presentation, factual error by the reviewer, question), and what the paper actually says (section, line, quote).

Check each point against the paper and, for related work, against the papers themselves (literature skill; fetch with the source skills when the reviewer names a paper). Mark points that the reviewer guidelines treat as unhelpful (e.g. "not novel" without a reference, demanding comparisons to work after the deadline) and point the user to the issue-reporting route the fetched guide describes. Name each such point with the issue code the fetched guide uses (e.g. H9) and the guide's URL as PK guidelines prints it, so the report to ARR can be pasted as is. The answers to the reviewers in rebuttal.md carry no such references.

Show the triage to the user as a table. Then ask with AskUserQuestion, point by point for the important ones: concede, argue, or answer with new results, and which new results exist. Wait for the answers.

3. Draft

Write rebuttal.md: per reviewer, the points in order of importance, each with a short quote of the point and a direct answer. Answers cite sections, tables and line numbers of the paper, report only numbers the authors gave you, and promise only the changes the authors agreed to. Polite, specific, no thanks paragraphs beyond one line. Follow the writing skill.

Add a general response for points several reviewers share, if the fetched rules allow one. Check the length against the limit and report the count.

4. Follow-up

List the promised changes as items in report.md (category Review, 🔴), so the camera-ready or resubmission version keeps the promises.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.