Response Tone Polisher

Polishes response letters to peer reviewers by softening harsh or defensive language while preserving the author's position and scientific integrity.

Overview

This skill analyzes author draft responses to reviewer comments and transforms confrontational or defensive phrasing into professional, diplomatic academic language. It helps researchers maintain positive relationships with reviewers while standing firm on scientifically justified positions.

Key Features

• - Tone Analysis: Identifies defensive, confrontational, or overly direct language
• Polite Transformation: Converts harsh statements into courteous academic prose
• Position Preservation: Maintains the author's scientific stance while improving delivery
• Context Awareness: Adapts based on response type (acceptance, partial acceptance, respectful decline)
• Academic Expression Library: Built-in collection of polished academic phrasings

When to Use

• - Before submitting response letters to journal editors
• When reviewer feedback triggers emotional or defensive reactions
• For authors whose first language is not English
• When revising rejected manuscripts for resubmission
• To ensure diplomatic handling of disagreements with reviewers

Usage Examples

Basic Usage

CODEBLOCK0

Defensive Language Transformation

Original (Defensive)	Polished (Professional)
"I will not change this."	"We have carefully considered this suggestion and respectfully maintain our original approach because..."
"The reviewer is wrong."

"We respectfully offer a different interpretation..." | | "This is unnecessary." | "We appreciate this suggestion; however, we believe the current presentation adequately addresses this point." | | "We already explained this." | "We have expanded our explanation to enhance clarity (Page X, Lines Y-Z)." | | "That's not our fault." | "We acknowledge this limitation and have added appropriate caveats to the Discussion." |

Input Parameters

Parameter	Type	Required	Description
INLINECODE0	str	Yes	The reviewer's original comment or criticism
INLINECODE1

str | Yes | Author's initial draft response (may contain harsh/defensive language) | | response_type | str | No | One of: accept, partial, decline (default: auto-detect) | | polish_level | str | No | light, moderate, heavy (default: moderate) | | preserve_meaning | bool | No | Ensure scientific position is preserved (default: true) |

Output Format

CODEBLOCK1

Tone Patterns Detected

The skill identifies and transforms:

1. Direct Refusals

• - "No" / "We won't" → "We respectfully decline to..."
• "We can't" → "We are unable to..."

2. Defensive Statements

• - "But we already..." → "We have now clarified..."
• "This is not correct" → "We respectfully note that..."

3. Blame Shifting

• - "The reviewer misunderstood" → "We apologize for the lack of clarity; we have revised..."
• "This is standard" → "This approach aligns with established conventions..."

4. Emotional Language

• - "Unfortunately" (overused) → [removed or softened]
• "Obviously" → [removed]
• "Clearly" → [removed or context-dependent]

Polite Academic Expressions

Acknowledging Reviewers

• - "We thank the reviewer for this insightful observation."
• "We appreciate the reviewer's careful attention to this detail."
• "We are grateful for this constructive feedback."
• "This is an excellent point."

Expressing Disagreement Diplomatically

• - "We respectfully offer an alternative interpretation..."
• "Upon careful reconsideration, we believe..."
• "While we appreciate this perspective, we note that..."
• "We respectfully maintain our position that..."

Explaining Limitations

• - "We acknowledge this limitation and have addressed it by..."
• "This constraint reflects the trade-off between..."
• "We have added appropriate caveats regarding this limitation."

Describing Changes

• - "We have revised the manuscript to clarify..."
• "We have expanded the relevant section to include..."
• "We have incorporated this suggestion by..."

Workflow

1. 1. Input Analysis: Parse reviewer comment and draft response
2. Tone Assessment: Score defensiveness and identify problematic phrases
3. Pattern Matching: Find harsh expressions in the transformation library
4. Reconstruction: Rewrite maintaining scientific accuracy
5. Quality Check: Verify politeness and clarity

Command Line Usage

CODEBLOCK2

Python API

CODEBLOCK3

References

• - references/polite_expressions.json - Curated library of academic polite expressions
• INLINECODE12 - Common defensive patterns and their transformations
• INLINECODE13 - Before/after polishing examples

Limitations

• - Does not verify scientific accuracy of responses
• Requires human review for complex nuanced disagreements
• May over-soften; authors should verify position is still clear
• Best for English-language responses

Quality Checklist

After polishing, verify:

• - [ ] Original scientific position is preserved
• [ ] No confrontational language remains
• [ ] Professional tone throughout
• [ ] Clear acknowledgment of reviewer's effort
• [ ] Specific changes are still referenced
• [ ] Response directly addresses the comment

Risk Assessment

Risk Indicator	Assessment	Level
Code Execution	Python/R scripts executed locally	Medium
Network Access

No external API calls | Low | | File System Access | Read input files, write output files | Medium | | Instruction Tampering | Standard prompt guidelines | Low | | Data Exposure | Output files saved to workspace | Low |

Security Checklist

• - [ ] No hardcoded credentials or API keys
• [ ] No unauthorized file system access (../)
• [ ] Output does not expose sensitive information
• [ ] Prompt injection protections in place
• [ ] Input file paths validated (no ../ traversal)
• [ ] Output directory restricted to workspace
• [ ] Script execution in sandboxed environment
• [ ] Error messages sanitized (no stack traces exposed)
• [ ] Dependencies audited

Prerequisites

CODEBLOCK4

Evaluation Criteria

Success Metrics

• - [ ] Successfully executes main functionality
• [ ] Output meets quality standards
• [ ] Handles edge cases gracefully
• [ ] Performance is acceptable

Test Cases

1. 1. Basic Functionality: Standard input → Expected output
2. Edge Case: Invalid input → Graceful error handling
3. Performance: Large dataset → Acceptable processing time

Lifecycle Status

• - Current Stage: Draft
• Next Review Date: 2026-03-06
• Known Issues: None
• Planned Improvements:

- Performance optimization - Additional feature support