Polish (rephrase) a rebuttal message template for clarity and professionalism while preserving the original structure, tone, and intent.
SkillScore86Maintained
Automatic
◆Writing & Editing pack
Last verified 8/27/2026
What it changes
Passed 19 of 22 test cases with the skill, and 15 of 22 without it.
Without skill68%
With skill86%
Checks it passed that the model alone missed
The JSON object contains the top-level key 'text'.
The output retains the original greeting phrase 'Hi R3'.
The polished output removes the redundant repetition of completing experiments.
and 1 more in the full report
4 fixed15 passed either way3 still failing0 broke
Pass-rate lift
+18 pp
Tokens
+46%
Agent turns
0%
Response time
+7%
Model gemini-3.6-flashMeasured 8/27/2026v119 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 4 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 4
Prompt
Polish this update to AAAI chairs: 'We have finished the re-experiments and we completed the experiments again.' Return JSON with key 'text'.
What was checked, without and with the skill
Checked
Without skill
With skill
The polished output removes the redundant repetition of completing experiments.
Missed
Passed
case-13 · gemini-3.6-flash · 8/27/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md34 linessingle file
Template Polish Skill
Rephrase a rebuttal-related message (e.g. nudge email, status update) so it reads naturally and clearly.
Core Principles
Preserve original structure: Keep the same paragraph order, greeting, sign-off, and line breaks. Do not merge or split paragraphs.
Preserve original tone: The input is already semi-formal academic correspondence. Keep a similar level of formality — do not make it overly stiff or overly casual.
Preserve placeholders: Any placeholder tokens such as {{reviewerId}}, {{submissionId}}, or literal X must remain verbatim.
Keep meaning unchanged: Do not add, remove, or alter the substantive content.
Light touch: Only rephrase for clarity, conciseness, and naturalness. Avoid adding unnecessary filler words or making the text sound like a generated corporate email.
What to improve
Fix grammar or awkward phrasing.
Reduce redundancy (e.g. two sentences saying the same thing).
Improve word choice where a simpler or more precise word exists.
Smooth transitions between sentences.
What NOT to do
Do not change the greeting or sign-off style.
Do not rewrite from scratch.
Do not make it sound overly formal or "written by AI".
Do not remove any substantive point the author made.
Do not add new content or sentiments not present in the original.
Output format
Return JSON only (no markdown fences) with this schema: