- name
SKILL.md
Le fichier du skill reste dans le dépôt de l'éditeur.
Collez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add fcakyon/labrat --skill rebuttal -a cursor -yCollez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add fcakyon/labrat --skill rebuttal -a claude-code -yCollez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add fcakyon/labrat --skill rebuttal -a codex -yCollez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add fcakyon/labrat --skill rebuttal -a grok -yEnvoyez le message copié dans un chat Grok Bot. Le Bot récupère ce SKILL.md sur GitHub et l'ajoute aux skills que partagent tous vos Bots.
Install this skill: https://github.com/fcakyon/labrat/tree/HEAD/plugin/skills/rebuttalDe l'éditeur
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.mdFAQ
Téléchargez plugin/skills/rebuttal/SKILL.md auprès de l'éditeur, ou copiez le chemin et ouvrez le dépôt. PlugMCP répertorie le skill et n'héberge pas le fichier.
L'éditeur le maintient sur https://github.com/fcakyon/labrat.
Claude, Cursor, Codex et Grok Build peuvent lire un SKILL.md que vous ajoutez depuis le dépôt de l'éditeur. Grok Bot l'installe lorsque vous envoyez dans un chat le lien du dossier GitHub du skill.