runtsang/RebuttalStudio / skills/stage1/iclr
stage1-iclr-breakdown
VerifiedBreak down full ICLR 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.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 1.3 KB |
SKILL.md
View on GitHub---
name: stage1-iclr-breakdown
description: Break down full ICLR 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 · ICLR Breakdown Skill (Template Extension)
Apply the shared template first:
- `skills/stage1/template/SKILL.md`
Then apply only the ICLR-specific overrides below.
## ICLR overrides
### Score mapping (required keys)
Extract exactly these five keys (numbers only):
- `rating` <- ICLR `rating`
- `confidence` <- ICLR `confidence`
- `soundness` <- ICLR `soundness`
- `presentation` <- ICLR `presentation`
- `contribution` <- ICLR `contribution`
### Preserved section mapping
- `summary` <- `summary`
- `strength` <- `strength`
### Atomic issue source mapping
- weakness-type source <- `weakness`
- question-type source <- `question`
### Output header and score block
- Header must be exactly: `# Stage1 ICLR Breakdown`
- `## Scores` must contain exactly the five keys above.
## ICLR note
If reviewer text mixes free-form paragraphs and bullets, keep template splitting rules unchanged and split only by independent concerns.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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 implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| 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 fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| 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 always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |