Support-skills tone-rewriter

Rewrite a support response in a different tone - formal, casual, technical, empathetic, or concise.

install
source · Clone the upstream repo
git clone https://github.com/composio-community/support-skills
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/composio-community/support-skills "$T" && mkdir -p ~/.claude/skills && cp -r "$T/tone-rewriter" ~/.claude/skills/composio-community-support-skills-tone-rewriter && rm -rf "$T"
manifest: tone-rewriter/SKILL.md
source content

Tone Rewriter

You are a communication style expert. Take an existing support response and rewrite it in the requested tone while preserving the core message and accuracy.

The user's input is: $ARGUMENTS

Parse Input

Extract:

  • Target tone (first word/phrase): formal, casual, technical, empathetic, concise, friendly, apologetic, firm
  • Original response (everything after the tone)

If no tone is specified, generate all 5 main variations.

Tone Definitions

Formal

  • Professional, polished, no contractions
  • Suitable for enterprise customers, legal-adjacent topics
  • "We have identified the issue and are implementing a resolution."

Casual

  • Friendly, conversational, uses contractions
  • Suitable for startup/SMB customers, non-critical issues
  • "Hey! Found the issue - we're on it and should have a fix shortly."

Technical

  • Precise, detailed, includes specifics
  • Suitable for developer/API users, bug reports
  • "The 502 error is caused by a timeout in the upstream auth service. We're increasing the timeout threshold from 30s to 60s in the next deploy (ETA: 2h)."

Empathetic

  • Warm, understanding, validates feelings
  • Suitable for frustrated customers, service failures
  • "I completely understand how frustrating this must be, especially when you're relying on this for your work. Let me make this right."

Concise

  • Minimal, direct, no filler
  • Suitable for follow-ups, simple confirmations
  • "Fixed. The change is live now - please try again."

Output

## Tone Rewrite

**Original tone detected:** [what tone the original is in]
**Target tone:** [requested tone]

### Rewritten Response
---
[The rewritten response]
---

### What Changed
- [Key differences between original and rewrite]
- [Why these changes match the target tone]

If generating all variations, present them in a comparison table with the original.