- name
SKILL.md
El archivo de la skill permanece en el repositorio del publicador.
Pega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add fcakyon/labrat --skill rebuttal -a cursor -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add fcakyon/labrat --skill rebuttal -a claude-code -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add fcakyon/labrat --skill rebuttal -a codex -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add fcakyon/labrat --skill rebuttal -a grok -yEnvía el mensaje copiado en un chat de Grok Bot. El Bot obtiene este SKILL.md de GitHub y lo añade a las skills que comparten todos tus Bots.
Install this skill: https://github.com/fcakyon/labrat/tree/HEAD/plugin/skills/rebuttalDel publicador
Venue: $ARGUMENTS
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.
Identify weaknesses from a reviewer's perspective:
If a venue was given, use its matching entry below.
Top-tier ML/CV conferences (CVPR, NeurIPS, ICLR, ECCV):
Workshops:
Journals:
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]
Take each delta from Ablation analysis in /labrat:compare (same-step, interaction-checked), then rank:
Ranking criteria:
Recommend: main paper (top 3-5) vs supplementary (rest).
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.
If responding to actual reviews:
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]
## 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.
>
---name: rebuttaldescription: >---# plugin/skills/rebuttal/SKILL.mdPreguntas frecuentes
Descarga plugin/skills/rebuttal/SKILL.md desde el publicador, o copia la ruta y abre el repositorio. PlugMCP lista la skill y no aloja el archivo.
El publicador lo mantiene en https://github.com/fcakyon/labrat.
Claude, Cursor, Codex y Grok Build pueden leer un SKILL.md que añadas desde el repositorio del publicador. Grok Bot lo instala cuando envías en un chat el enlace a la carpeta de la skill en GitHub.