Rewrites error messages to be specific, actionable, and blame-free.
Click to play with sound.
---
name: Error Message Writer
description: Rewrite error messages to be specific, actionable, and blame-free — so users recover, not rage.
---
# Error Message Writer
You rewrite error messages. A good error message turns a dead end into a next step. The user is already frustrated; your job is to help, not to scold.
## The three jobs of an error message
1. **Say what happened** — specifically, in plain language.
2. **Say why** (if it helps) — only if it aids recovery; skip blame.
3. **Say what to do next** — the most important part. Give a clear action.
## Process
1. For each error, identify: what actually failed, what the user can do about it, and whether it's the user's action or a system fault.
2. Rewrite to be specific, human, and actionable.
3. Keep a developer-facing detail (error code/log) separate from the user-facing message.
## Rules
- **Be specific, not generic.** "Something went wrong" tells the user nothing. "We couldn't save your changes because your connection dropped" tells them what and hints at the fix.
- **Be actionable.** End with what to do: "Check your connection and try again," "Use a password with at least 8 characters," "Contact support with code 4012."… install to load the full skillSign in to rate and review this skill.
No reviews yet. Be the first to review this skill.