본문으로 건너뛰기
cccskills
무료GitHub에 공개

reviewer-defense

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".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

설치 방법 보기

포함된 파일(1)

  • SKILL.md4.6 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

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 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 3: Question Generation

Generate likely reviewer questions, ranked by probability:

For each question:

  1. The question — phrased as a reviewer would write it
  2. Why they'd ask — what triggers this concern
  3. Can existing data answer it? — yes (point to specific data) or no (new experiment needed)
  4. Draft response — if answerable, write a concise response

Template:

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]

Generate at least 10 questions, prioritized by likelihood.

Step 4: Ablation Selection

From all available experiments, select the subset that:

  1. Proves the core contribution — the single most important ablation
  2. Shows each component's value — incremental additions showing improvement
  3. Addresses anticipated weaknesses — preemptively answers likely questions
  4. Tells a coherent story — the progression makes narrative sense

Ranking criteria for each ablation:

  • Impact magnitude: how much does it change the primary metric?
  • Narrative strength: does it clearly support a specific claim?
  • Uniqueness: does it show something no other ablation shows?
  • Cost: main paper vs appendix (based on space constraints)

Step 5: Negative Results

Negative results are valuable when properly framed:

  • "We explored X but found it did not improve over Y because Z"
  • This shows thoroughness and provides insight
  • Frame as "analysis" not "failure"
  • Include in supplementary if not in main paper

Step 6: 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

Produce:

  1. Weakness table: categorized weaknesses with severity
  2. Top 10 anticipated questions: with answerability and draft responses
  3. Recommended ablation subset: with justification for each
  4. Suggested text edits: specific paragraphs to strengthen before submission

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

compare

무료

Same-epoch comparison of training runs across wandb, neptune, tensorboard, or mlflow. Aligns runs at the student's current step (never current-vs-final-of-baseline) and separates proxy metrics from downstream targets. Use when the user asks to compare runs, check if a run is improving, track lag against a baseline, rank experiments, or evaluate run-vs-run performance.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

fcakyon/phd-skills4272026년 10월 12일 업데이트

Use when the user wants to analyze dataset bias, create stratified samples, evaluate fairness, or plan dataset collection. Triggers on phrases like "dataset bias", "stratified sample", "class imbalance", "data distribution", "fairness analysis", or "ethical review".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

fcakyon/phd-skills4272026년 10월 12일 업데이트

debug

무료

Evidence-before-action diagnosis of failing ML experiments. Probes the system before guessing causes, process list, dmesg, GPU stats, log scrollback, checkpoint state, then states a hypothesis as a hypothesis and runs a smoke before claiming a root cause. Use when the user asks why a run is failing, diverging, OOMing, hanging, slow, producing weird metrics, has crashed, or asks to debug, diagnose, troubleshoot, or investigate a training issue.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

fcakyon/phd-skills4272026년 10월 12일 업데이트

Use when the user wants to design experiments, plan ablation studies, structure baselines, or create incremental evaluation strategies. Triggers on phrases like "design ablation", "plan experiment", "what experiments should I run", "baseline comparison", or "experiment matrix".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

fcakyon/phd-skills4272026년 10월 12일 업데이트

Use when the user wants to set up or troubleshoot a LaTeX environment, choose between biber and bibtex, install packages for a specific venue template, or configure compilation. Triggers on phrases like "setup latex", "biber vs bibtex", "latex compilation error", "install latex packages", "venue template", or "texlive setup".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

fcakyon/phd-skills4272026년 10월 12일 업데이트

launch

무료

Pre-flight checklist for long-running ML training jobs covering config diff, run naming, path verification, monitoring setup, and restart-cleanup. Use when the user asks to launch, kick off, start, restart, or kill a training run, or mentions launching a multi-hour or multi-day GPU job (python train, accelerate launch, torchrun, deepspeed, sbatch, tmux training).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

fcakyon/phd-skills4272026년 10월 12일 업데이트

fcakyon의 스킬 모두 보기

이 스킬의 문제 신고