When external reviews land and you need to write a conference rebuttal, this workflow parses the feedback, atomizes every concern into a tracked issue board, and drafts a venue-compliant response with strict provenance gates. It supports both single-document rebuttals (ICML style) and per-reviewer threads (OpenReview), enforces character limits, and stress-tests your draft against a simulated reviewer before you submit. The safety model is rigid: every claim needs a source (paper, review, or user-confirmed result), every promise needs approval, and every issue gets explicitly answered or deferred. It won't run new experiments or fabricate results, but if you bring approved evidence it will weave it in. Quick mode stops after strategy planning if you just want to see what reviewers are asking for.
npx -y skills add wanshuiyin/auto-claude-code-research-in-sleep --skill rebuttal --agent claude-codeInstalls into .claude/skills of the current project.
Select a file.
sickn33/antigravity-awesome-skills