Individual skill

error-message-writer

Rewrites error messages to be specific, actionable, and blame-free - what happened, why it helps to know, and what to do next - with tone calibrated to severity and developer-facing detail kept separate from the user-facing text. Use when someone asks "rewrite this error message", "our app just says something went wrong", "make this validation message less hostile", or is auditing error states before launch. Do NOT use for reviewing all in-product copy beyond errors - use ux-writing-audit instead; for the copy users see during first-run setup, use onboarding-copy.

skills/error-message-writer/SKILL.md

Read pinned source

Source commit 97a13607d669157a4a16d5ba79b77f208319f7b9

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
24
Repository last updated
Oct 13, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# 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.