Skip to content

runtsang/RebuttalStudio / skills/stage1/icml

stage1-icml-breakdown

Verified

Break down full ICML reviewer responses into structured rebuttal units. Use when input contains reviewer summary/presentation/contribution/strength/weakness/question text and the goal is to split weaknesses/questions into granular R-style response items while preserving original wording for quoted issues.

FileKindSize
SKILL.mdskill md1.5 KB
---
name: stage1-icml-breakdown
description: Break down full ICML reviewer responses into structured rebuttal units. Use when input contains reviewer summary/presentation/contribution/strength/weakness/question text and the goal is to split weaknesses/questions into granular R-style response items while preserving original wording for quoted issues.
---

# Stage 1 · ICML Breakdown Skill (Template Extension)

Apply the shared template first:

- `skills/stage1/template/SKILL.md`

Then apply only the ICML-specific overrides below.

## ICML overrides

### Score mapping (required keys)

Extract exactly these six keys (numbers only):

- `rating` <- `Overall Recommendation`
- `confidence` <- `Confidence`
- `soundness` <- `Soundness`
- `presentation` <- `Presentation`
- `significance` <- `Significance`
- `originality` <- `Originality`

### Preserved section mapping

- `summary` <- `Summary`
- `strength` <- `Limitations` (keep compatibility with shared output key naming)

### Atomic issue source mapping

- weakness-type source <- `Strengths And Weaknesses` (extract only concern/criticism parts)
- question-type source <- `Key Questions For Authors`

### Output header and score block

- Header must be exactly: `# Stage1 ICML Breakdown`
- `## Scores` must contain exactly the six keys above.

## ICML note

If "Strengths And Weaknesses" mixes praise and criticism in one bullet, keep praise in preserved context and split only actionable weakness concerns into atomic issues.
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall