runtsang/RebuttalStudio / skills/utility/stage/text-condense
text-condense
VerifiedCondense rebuttal prose into fewer words without changing the original meaning. Use when a response block, paragraph, or selected passage is too long but all technical content, citations, and commitments must stay intact. Supports academic English.
Text Condense for Rebuttal Prose
RebuttalStudio Utility Apply this skill when a selected passage is too long and needs to be tighter without changing what it says.
Condense the text by removing redundancy, filler, and repeated phrasing while preserving the original meaning, evidence, and technical content.
Goal
Produce a shorter version of the selected text that says the same thing more efficiently.
Rules
- Preserve the original meaning exactly.
- Remove filler, repetition, and unnecessary hedging.
- Preserve all technical claims, numbers, citations, equations, named entities, and placeholder tokens.
- Preserve reviewer quotations and structural labels if they appear.
- Do not add new information, interpretations, promises, or evidence.
- Do not change stance, polarity, or confidence level.
- Keep the original paragraph, list, and markdown structure whenever possible.
- If the text is already concise, make only minimal edits.
Output
Return strict JSON:
{ "text": "..." }
Good Use Cases
- A Stage 2 response that repeats the same defense twice
- A Stage 3 response block that is clear but too long
- A Stage 4 follow-up answer that can be made tighter before submission
- A Stage 5 summary paragraph that needs a shorter version
What Not to Change
- Technical substance
- Numerical values
- Citations
- Placeholder tokens such as
{{reviewerId}} - Reviewer comment labels such as
> **Reviewer's Comment**:and**Response**:
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: 321k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 321k | 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: 321k | 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: 321k | Updated | Claude CodeCodex | Verified | Install |