Summary

• New inno-rebuttal skill with 6-stage workflow for drafting academic rebuttals across 20+ AI/CS conferences
• Absorbs best practices from two community rebuttal tools: review-response (templates/cases) and wanshuiyin/rebuttal (safety gates/issue board), with attribution in Design Influences section
• Registers the skill in catalog, tag mapping, stage map, and taxonomy overrides

Key Features

• Issue Board: structured concern tracking with severity classification (Major-Blocking/Major-Addressable/Minor/Misunderstanding) and reviewer stance analysis (Champion/Persuadable/Entrenched)
• 6 response strategies with combo patterns and detailed templates in references/response_strategies.md
• Safety gates: provenance (no fabrication), commitment (no empty promises), coverage (no missed concerns)
• Venue routing: 20+ venues with specific artifact formats, revision policies, and constraints in references/venue_rule_matrix.md
• Character budgeting and dual output (paste-ready + extended version)
• Multi-round follow-up support for threaded discussion venues (ICLR, NeurIPS, ICML 2026, etc.)
• scripts/count_limits.sh: automated venue limit verification

File Structure

skills/inno-rebuttal/
├── SKILL.md                          [308 lines]
├── references/
│   ├── venue_rule_matrix.md          [139 lines]
│   ├── writing_principles.md         [177 lines]
│   ├── platforms_and_policies.md     [95 lines]
│   ├── response_strategies.md        [196 lines]
│   └── issue_board_guide.md          [100 lines]
└── scripts/
    └── count_limits.sh               [94 lines]

Test plan

• Verify skill triggers correctly for English and Chinese rebuttal requests
• Test with a sample 3-reviewer scenario (ICML format)
• Verify count_limits.sh works for character and word counting
• Confirm all cross-references in SKILL.md resolve to existing files

🤖 Generated with Claude Code