mimi-rephrase · git:20261016.ac634ff · 2026-10-16 · sha256 d804ac6f8cffc778

mimi-rephrase git:20261016.ac634ffA

Immutable. This exact content never changes and is served at /api/v1/blob/d804ac6f8cffc778.

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_wggp7cit2ofhv35u/d804ac6f8cffc778d9ce271a2b0976b931ecf8f2cfd127c8ea4974b508fe0aad.json

Then /plugin install mimi-rephrase@markdownregistry-wggp7cit2ofhv35u in Claude Code. It installs this exact version, the one graded A here, pinned to the commit it was graded at, and leaves it there.

---
name: mimi-rephrase
description: Guide the user on how to say or write the same idea in different tones, registers and for different audiences, in writing or out loud (meetings, conversations, presentations, difficult conversations). Use for requests like "say this differently", "other ways to put this", "how do I tell X", "make this more formal / casual / diplomatic", "how would I say this out loud", or any rewrite with a social or tonal dimension.
---

# Tone & Delivery Guide

## Steps

1. Identify the **core intent**: what I actually want to say or achieve.
2. Identify the **audience** and **channel**: written (email, message, document) or spoken (meeting, call, conversation, presentation). Infer from context; ask only if it changes the answer.
3. Note the **tone signals** already present (formal, casual, assertive, hesitant, etc.).
4. Write alternatives in the styles below, preserving my meaning; skip a style if it does not suit the situation.
5. Recommend the style that best fits the audience and my original voice.

## Styles

- **Direct / Assertive** — confident, no filler, gets to the point.
- **Casual / Friendly** — conversational, warm, people-first.
- **Formal / Polished** — professional, precise, contemporary.
- **Analytical / Precise** — structured, evidence-led, detail-oriented.
- **Diplomatic / Softened** — considerate, hedged, conflict-aware.
- **Creative / Expressive** — distinctive voice, unexpected framing.

## Spoken Delivery

When the channel is spoken:
- Use shorter sentences, natural contractions and plain words that are easy to say and hear.
- Lead with the main point; avoid long subordinate clauses.
- Add brief delivery tips: what to emphasise, where to pause, and phrases or habits to avoid (fillers, over-apologising, excessive hedging).

## Response Template

**Intent detected:** [one-sentence summary of what I want to convey]
**Audience / channel:** [who, and written or spoken]

**Alternatives:**
- **Direct / Assertive** — [rewrite]
- **Casual / Friendly** — [rewrite]
- **Formal / Polished** — [rewrite]
- **Analytical / Precise** — [rewrite]
- **Diplomatic / Softened** — [rewrite]
- **Creative / Expressive** — [rewrite]

**Recommended:** [style] — [one-line reason]

**Delivery tips:** [only for spoken situations]