agentleFS
ScodiveScodive/Paper-Agent-Skills/skills/rebuttal-writing/SKILL.md

rebuttal-writing

Skill20 starsChanged 9 days agoMITView on GitHub

Prepare point-by-point responses to academic reviews using the supplied manuscript and completed evidence, tracking unanswered questions and proposed experiments separately.

7 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 3 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If dependencies are missing, create a Python 3.10+ virtual environment and install scripts/requirements.txt from this skill.

    line 13
  2. Very specific:

    Use paper-agent instead of python3 src/main.py after installation.

    line 22
  3. Distinctive:

    When new results are supplied, use the academic revision workflow to check result consistency.

    line 31
  4. Distinctive:

    Keep replies specific and professional.

    line 34
  5. Distinctive:

    Check the current venue/year response rules before choosing length or format.

    line 36

“Common” is measured: kept by at least 6 in 10 of the 6 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

Evidence-based rebuttal

For a standalone skill installation, use python3 <installed-skill-directory>/scripts/paper_agent.py instead of python3 src/main.py. Its readable runtime is bundled in scripts/runtime/. If dependencies are missing, create a Python 3.10+ virtual environment and install scripts/requirements.txt from this skill. No model key is needed by the tools.

Export the complete paper and review text for the host agent:

python3 src/main.py rebuttal --paper paper.md --reviews reviews.txt --out runs/rebuttal-01

Use paper-agent instead of python3 src/main.py after installation. Read all inputs and write rebuttal.md plus actions.json in the exported directory. The command prepares a task; it does not automatically generate or submit a reply.

  • Split reviews into individual points. Assess misunderstanding, valid flaw, missing evidence, experiment request and presentation issue on their merits.
  • Link factual responses to manuscript lines and actual supplied evidence.
  • Track actions as proposed, not_run, completed or verified. Never describe an experiment as performed or a manuscript change as applied until it exists.
  • When new results are supplied, use the academic revision workflow to check result consistency. A rebuttal example is not experimental evidence.
  • Acknowledge genuine limitations and state what the evidence cannot resolve.
  • Keep replies specific and professional. Do not invent reviewer score changes or promise that a response will reverse a decision.
  • Check the current venue/year response rules before choosing length or format.

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.