runtsang/RebuttalStudio / skills/stage1/arr
stage1-arr-breakdown
VerifiedBreak down full ARR (ACL Rolling Review) reviewer responses into structured rebuttal units. Use when input contains ARR reviewer fields (Paper Summary, Strengths, Weaknesses, Comments/Suggestions) and numeric scores (Confidence, Soundness, Excitement, Overall Assessment, Reproducibility). Splits weaknesses and comments/suggestions into granular response items while preserving original wording for quoted issues.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 1.8 KB |
SKILL.md
View on GitHub---
name: stage1-arr-breakdown
description: Break down full ARR (ACL Rolling Review) reviewer responses into structured rebuttal units. Use when input contains ARR reviewer fields (Paper Summary, Strengths, Weaknesses, Comments/Suggestions) and numeric scores (Confidence, Soundness, Excitement, Overall Assessment, Reproducibility). Splits weaknesses and comments/suggestions into granular response items while preserving original wording for quoted issues.
---
# Stage 1 · ARR Breakdown Skill (Template Extension)
Apply the shared template first:
- `skills/stage1/template/SKILL.md`
Then apply only the ARR-specific overrides below.
## ARR overrides
### Score mapping (required keys)
Extract exactly these five keys (numbers only, decimals allowed):
- `confidence` <- ARR `Confidence`
- `soundness` <- ARR `Soundness`
- `excitement` <- ARR `Excitement`
- `assessment` <- ARR `Overall Assessment` (number before `=` sign)
- `reproducibility` <- ARR `Reproducibility` (number before `=` sign)
### Preserved section mapping
- `summary` <- `Paper Summary`
- `strength` <- `Summary Of Strengths`
### Atomic issue source mapping
- weakness-type source <- `Summary Of Weaknesses`
- question-type source <- `Comments Suggestions And Typos` (label as `suggestion`)
### Output header and score block
- Header must be exactly: `# Stage1 ARR Breakdown`
- `## Scores` must contain exactly the five keys above.
## ARR notes
- ARR scores may include decimals (e.g. `2.5`, `3.5`). Extract only the numeric part before any `=` or description text.
- The `Ethical Concerns`, `Datasets`, `Software`, `Knowledge Of Paper`, and certification fields are irrelevant — ignore them.
- Map `Comments Suggestions And Typos` to the `suggestion` section and split it into atomic issues just as weaknesses are split.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| add-product-e2e-evalpaperclipai/paperclipAdd or extend a Paperclip full-stack runner E2E workflow, fixture, matcher, or report evidence path for local or Daytona execution. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| add-runner-evalpaperclipai/paperclipAdd or extend a Paperclip Runner protocol evaluation definition, roster, assertion, or report fixture with provenance and narrow validation. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| diagnose-why-work-stoppedpaperclipai/paperclipCompatibility entry point for failed, stalled, looping, or over-recovered Paperclip work. Use fix-failed-paperclip-run for the full diagnosis, regression, repair, real verification, and green-PR workflow; honor an explicitly requested diagnosis-only scope. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| fix-failed-paperclip-runpaperclipai/paperclipDiagnose and fix failed, stuck, slow, or incorrectly blocked Paperclip tasks and runs. Use with a task/run URL or failure report to trace the root cause, prove a regression red then green, check second-order effects, verify the real workflow, and deliver a PR with passing checks. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |