reviewer-defense

Featured

Use when the user wants to anticipate reviewer questions, select the strongest ablations to present, prepare rebuttals, or identify paper weaknesses before submission. Triggers on phrases like "reviewer questions", "anticipate reviewers", "rebuttal", "paper weaknesses", "defend the paper", or "strengthen the paper".

Code & Development 408 stars 34 forks Updated 1 weeks ago MIT

Install

View on GitHub

Quality Score: 88/100

Stars 20%
87
Recency 20%
90
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Reviewer Defense Methodology You are helping a researcher prepare for peer review by identifying weaknesses, selecting the strongest results, and drafting responses to likely questions. ## Step 1: Vulnerability Analysis Read the paper and 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 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 2: Venue-Specific Anticipation Different venues have different review cultures: **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 ev...

Details

Author
fcakyon
Repository
fcakyon/phd-skills
Created
6 months ago
Last Updated
1 weeks ago
Language
Shell
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Listed

academic-rebuttal-simulator

Simulates 'Reviewer 2' for ML papers (NeurIPS, ICLR). Critiques methodology, novelty, baselines, and related work. Outputs structured OpenReview-format reviews with sub-scores, suggests target venues with verified acceptance rates, and drafts conference rebuttals. Authored by João P. M. Silva.

0 Updated 1 months ago
jpmsilva1
AI & Automation Featured

kill-argument

Two-thread adversarial review: a fresh reviewer constructs the strongest 200-word rejection memo, then a second fresh reviewer defends the paper point-by-point and surfaces still-unresolved critical issues. Use when user says "kill argument", "adversarial review", "hostile review", "rebuttal preparation", "reviewer-2 simulation", or before submitting a theory paper that has already passed standard review rounds.

16,670 Updated 1 weeks ago
wanshuiyin
Code & Development Listed

adversarial-review

Review a research paper, proposal, or technical writeup by spawning five constructive reviewer archetypes — the Steelman-Builder, Assumption Auditor, Mechanism Seeker, Generous Skeptic, and Contextualizer — each of whom reads critically and curiously and writes a focused review, then synthesizes them into a meta-review with the crux and a decision. Use whenever the user wants a paper, draft, abstract, experiment plan, or research idea pressure-tested, red-teamed, or "reviewed like ICLR/NeurIPS," asks for "reviews of my paper," wants to know how reviewers will react before submitting, or asks to find the weaknesses in a technical argument. Trigger even when the user just says "review this," "tear this apart," or "what would reviewers say," as long as the artifact is a research or technical document.

3 Updated 4 weeks ago
goirik-chakrabarty