Polish Text
Take the user's raw text input and polish it into a well-structured, clear message.
Input
The user provides raw text after the slash command, e.g.:
/writing:polish-text Hey Lukas, ich wollte mal fragen ob...
If no text is provided, read the input from the clipboard: pbpaste on macOS,
wl-paste or xclip -selection clipboard -o on Linux, powershell Get-Clipboard
on Windows. Echo the first line back before polishing so the user can confirm you
picked up the right thing. If the clipboard is empty, or its contents are clearly
not prose (a URL, a file path, a credential, a code snippet), ask the user for the
text instead of polishing it.
If clipboard access is unavailable, ask for text only when none was supplied.
Otherwise polish the supplied text and return it for manual copying. Do not claim
to have read or changed the clipboard without a successful tool result.
Instructions
- Detect the language of the input and keep the output in the same language.
- Polish the text while preserving the original intent, tone, and meaning:
- Fix grammar, spelling, and punctuation
- Fix sentences the transcription broke
- Add paragraph breaks for readability
- Do not use markdown emphasis (
**bold**, _italic_). The output is usually
pasted into Teams or Slack, which render the markers literally instead of
formatting them. Carry emphasis through structure instead: short paragraphs,
one idea per line, key term at the front of the line. If the user asks to
"keep the markdown" (for Notion, GitHub, a doc), use it as normal.
- Convert lists or options into numbered/bulleted lists
- Remove filler words, false starts, and verbal tics (common in voice transcripts).
Keep phrasing the author uses on purpose, like "whatever" or "That's it."
- Keep the author's voice. The text is already theirs, so change only what is
broken.
- No em-dashes in the output. Do not introduce en-dashes, semicolons, or
phrasing like "not just X, but Y".
- Do NOT add new information, change the meaning, or remove important content.
- Output the polished text to the user so they can review it.
- Copy to clipboard:
pbcopy on macOS, wl-copy or xclip -selection clipboard
on Linux, clip on Windows.
- Confirm copying only after the clipboard command succeeds. If it fails,
leave the polished text available and state that it needs manual copying.
1---2name: polish-text3description: Polish and structure a text message while keeping the original language and intent, then copy the result to the clipboard. Use when the user says "polish this text", "clean up this message", "structure this", "polish my clipboard", or "/polish-text". The user provides raw text (e.g. voice memo transcript, draft message), or provides nothing and the text is taken from the clipboard, and gets back a polished version copied to the clipboard when local clipboard access is available.4---56# Polish Text78Take the user's raw text input and polish it into a well-structured, clear message.910## Input1112The user provides raw text after the slash command, e.g.:1314```15/writing:polish-text Hey Lukas, ich wollte mal fragen ob...16```1718If no text is provided, read the input from the clipboard: `pbpaste` on macOS,19`wl-paste` or `xclip -selection clipboard -o` on Linux, `powershell Get-Clipboard`20on Windows. Echo the first line back before polishing so the user can confirm you21picked up the right thing. If the clipboard is empty, or its contents are clearly22not prose (a URL, a file path, a credential, a code snippet), ask the user for the23text instead of polishing it.2425If clipboard access is unavailable, ask for text only when none was supplied.26Otherwise polish the supplied text and return it for manual copying. Do not claim27to have read or changed the clipboard without a successful tool result.2829## Instructions30311. **Detect the language** of the input and keep the output in the same language.322. **Polish the text** while preserving the original intent, tone, and meaning:33 - Fix grammar, spelling, and punctuation34 - Fix sentences the transcription broke35 - Add paragraph breaks for readability36 - Do not use markdown emphasis (`**bold**`, `_italic_`). The output is usually37 pasted into Teams or Slack, which render the markers literally instead of38 formatting them. Carry emphasis through structure instead: short paragraphs,39 one idea per line, key term at the front of the line. If the user asks to40 "keep the markdown" (for Notion, GitHub, a doc), use it as normal.41 - Convert lists or options into numbered/bulleted lists42 - Remove filler words, false starts, and verbal tics (common in voice transcripts).43 Keep phrasing the author uses on purpose, like "whatever" or "That's it."44 - Keep the author's voice. The text is already theirs, so change only what is45 broken.46 - No em-dashes in the output. Do not introduce en-dashes, semicolons, or47 phrasing like "not just X, but Y".483. **Do NOT** add new information, change the meaning, or remove important content.494. **Output the polished text** to the user so they can review it.505. **Copy to clipboard**: `pbcopy` on macOS, `wl-copy` or `xclip -selection clipboard`51 on Linux, `clip` on Windows.526. Confirm copying only after the clipboard command succeeds. If it fails,53 leave the polished text available and state that it needs manual copying.
alexoberneyer