SkillAgentSearch skills...

rebuttal

Prepare a paper for peer review. Reads the paper and experiment results, selects the strongest ablations, anticipates reviewer questions, finds weaknesses before submission, and drafts rebuttals to actual reviews

Install / Use

npx skills add fcakyon/phd-skills --skill rebuttal

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

85/100

Category

Marketing

Supported Platforms

Universal

Our assessment of rebuttal

rebuttal scores 85/100 on our quality scale, 448th of 642 Marketing skills we index.

Its SKILL.md is 5.0 KB long, well organised into 17 sections with 3 code examples: a solid amount of guidance for an agent.

It has 406 GitHub stars, a meaningful sign that others use it.

Substance
26/30
Structure
18/20
Description
15/15
Adoption
11/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so rebuttal is actively maintained.
  • 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 found

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.

AI review by kimi-k2.7-code on 2026-11-12. Automated pattern scan on 2026-11-12. 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.

SkillScoreStarsUpdatedFormat
rebuttal (this skill)by fcakyon854062mo agoSKILL.md
x402by browser-use100121.0k3d agoSKILL.md
algorithmic-artby anthropics100177.9k55d agoSKILL.md
pptxby anthropics100177.9k55d agoSKILL.md
designby nextlevelbuilder100149.0k6d agoSKILL.md

Frequently asked questions

How do I install rebuttal?
Run npx skills add fcakyon/phd-skills --skill rebuttal. The install tabs above show the steps for each supported agent.
Which AI agents does rebuttal work with?
It is written for Universal, 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 about 2 months ago, so rebuttal is actively maintained.

name: rebuttal description: > Prepare a paper for peer review. Reads the paper and experiment results, selects the strongest ablations, anticipates reviewer questions, finds weaknesses before submission, and drafts rebuttals to actual reviews. Use when the user asks about "reviewer questions", "anticipate reviewers", "rebuttal", "paper weaknesses", "defend the paper", "strengthen the paper", "select the strongest ablations", "fortify the paper", or "prepare for peer review". argument-hint: "<venue name (optional)>"

Rebuttal: Prepare for Peer Review

Venue: $ARGUMENTS

Step 1: Read the Paper and Results

Discover the paper, result and config files as in Step 1 (Discover Files) of /labrat:paper-check, including wandb logs and checkpoint directories. Then list the paper's claims (contributions and experiments), its metrics and baselines, and every available run and its outcome, including the ablation variants the configs define.

Step 2: Vulnerability Analysis

Identify weaknesses from a reviewer's perspective:

Technical Weaknesses

  • Missing baselines that reviewers would expect
  • Evaluation metrics that don't fully capture the contribution
  • Assumptions stated without justification
  • Scalability or generalization concerns not addressed
  • Missing error analysis or failure case discussion

Presentation Weaknesses

  • Claims stronger than evidence supports
  • Missing related work that a reviewer in the area would know
  • Unclear methodology (could someone reimplement from the paper alone?)
  • Figures that don't clearly convey the intended message
  • Inconsistencies between sections

Experimental Weaknesses

  • Small dataset size without justification
  • Missing statistical significance tests
  • No comparison with state-of-the-art on standard benchmarks
  • Hyperparameter sensitivity not explored
  • No computational cost comparison

Step 3: Venue-Specific Anticipation

If a venue was given, use its matching entry below.

Top-tier ML/CV conferences (CVPR, NeurIPS, ICLR, ECCV):

  • Expect extensive ablation studies
  • Strong baseline comparisons required
  • Novelty must be clearly articulated
  • Reproducibility is valued

Workshops:

  • More tolerant of work-in-progress
  • Interesting ideas valued over exhaustive evaluation
  • Novel applications of existing methods are acceptable

Journals:

  • Expect thorough related work discussion
  • Deeper analysis and more experiments than conferences
  • Writing quality and organization matter more

Step 4: Question Generation

List the 10 most likely reviewer questions, most likely first, phrased as a reviewer would write them, in this form:

Q: [Reviewer question]
Motivation: [Why this would be asked]
Answerable: [Yes, cite Table X / No, would need experiment Y]
Draft response: [If answerable, 2-3 sentences]

Step 5: Ablation Selection

Take each delta from Ablation analysis in /labrat:compare (same-step, interaction-checked), then rank:

| Run | Factor Changed | Primary Metric Delta | Narrative Strength | Include? | |-----|---------------|--------------------|--------------------|----------|

Ranking criteria:

  • Impact magnitude: how much does it change the primary metric? The largest improvement is the most convincing.
  • Narrative strength: does it directly support a specific paper claim?
  • Uniqueness: does it show something no other ablation shows?
  • Anticipated questions: does it preemptively answer likely reviewer concerns?
  • Cost: main paper vs appendix (based on space constraints)
  • Coverage: together the picks prove the core contribution, show each component's value and answer the top questions from Step 4

Recommend: main paper (top 3-5) vs supplementary (rest).

Step 6: Negative Results

Frame negative results as analysis, not failure ("We explored X but found it did not improve over Y because Z"), and put them in the supplementary if they do not fit the main paper.

Step 7: Rebuttal Preparation

If responding to actual reviews:

  1. Read ALL reviews before responding to any
  2. Identify common concerns across reviewers
  3. Prioritize: address factual errors first, then major concerns, then minor ones
  4. Be respectful: thank reviewers, acknowledge valid points
  5. Be specific: point to exact sections, tables, figures
  6. New experiments: only promise what you can deliver in the rebuttal period

Rebuttal structure per reviewer:

We thank Reviewer X for their thoughtful feedback.

**[Major concern]**: [Direct response with evidence]

**[Specific question]**: [Concrete answer]

**[Suggestion]**: [How we will incorporate it]

Output Format

## Rebuttal Report

### Weaknesses
[Table of categorized weaknesses with severity, prioritized]

### Recommended Ablation Subset
[Table with justification for each]

### Top 10 Anticipated Questions
[Numbered list with answerability and draft responses]

### Suggested Edits
[Specific paragraph-level improvements to strengthen before submission]

Add the per-reviewer rebuttal drafts from Step 7 when responding to actual reviews.

Related Skills

View on GitHub
GitHub Stars406
CategoryMarketing
Updated2mo ago
Forks34

Languages

Shell

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions