Error Message Writer Skill
An error is a moment of friction; a good error message turns it into a recovery. The formula is simple and
rarely followed: say what happened, in plain language, and what to do next — without blaming the user or
exposing a stack trace. This skill writes error copy that helps people get unstuck and keeps trust intact.
Working from a brief
Given "the payment failed" or a raw system error, write the message anyway — infer the likely cause and the
recovery path, and label assumptions. Where the real cause is unknown to the user, focus on the next action.
Never hand back a question instead of the copy; never surface internal/technical detail to end users.
Required Inputs
Ask for these only if they aren't already provided (else infer and label):
- What failed — the action or system, and the likely cause(s).
- The surface — inline field, toast/snackbar, modal, or full-page error.
- Recovery — what the user can actually do (retry, fix input, wait, contact support).
- Voice & constraints — tone, length limits, and whether a support/error code is needed.
Output Format
Error Message: [scenario]
- Recommended message — structured as:
- What happened — plainly, in the user's terms ("We couldn't process your payment").
- Why / what to check — only if it helps them act ("Your card was declined — check the details or try another card").
- Next step — the clear action (a button label or instruction).
- By surface — short variants for inline validation, toast, and full-page where relevant.
- Tone notes — blame-free, calm, human; matched to severity (a wrong field ≠ a data-loss event).
- For developers — a note on what to log vs. what to show (keep stack traces and codes out of the user message; offer a support reference if needed).
Quality Checks
Anti-Patterns
Based On
UX writing practice — plain-language, blame-free error messages with clear recovery, surface-appropriate variants, and log-vs-show separation.
Example Trigger Phrases
- "Write an error message."
- "Write validation text for this form."
- "Rewrite this cryptic system error."
- "Make our error messages less blaming."
1---2name: error-message-writer3description: "Write clear, helpful error messages that tell users what happened and how to fix it. Use when asked to write an error message, validation text, a failure/empty-error state, or to rewrite a cryptic system error. Produces human, blame-free error copy — what went wrong, why (if useful), and the next step — with options per surface (inline, toast, full page) and the related success/empty states."4disable-model-invocation: true # skill-optimizer5metadata:6 source: https://skillmd.com/skills/slipcast-dev/error-message-writer7---89# Error Message Writer Skill1011An error is a moment of friction; a good error message turns it into a recovery. The formula is simple and12rarely followed: say **what happened**, in plain language, and **what to do next** — without blaming the user or13exposing a stack trace. This skill writes error copy that helps people get unstuck and keeps trust intact.1415## Working from a brief1617Given "the payment failed" or a raw system error, **write the message anyway** — infer the likely cause and the18recovery path, and label assumptions. Where the real cause is unknown to the user, focus on the next action.19Never hand back a question instead of the copy; never surface internal/technical detail to end users.2021## Required Inputs2223Ask for these only if they aren't already provided (else infer and label):2425- **What failed** — the action or system, and the likely cause(s).26- **The surface** — inline field, toast/snackbar, modal, or full-page error.27- **Recovery** — what the user can actually do (retry, fix input, wait, contact support).28- **Voice & constraints** — tone, length limits, and whether a support/error code is needed.2930## Output Format3132### Error Message: [scenario]3334- **Recommended message** — structured as:35 - **What happened** — plainly, in the user's terms ("We couldn't process your payment").36 - **Why / what to check** — only if it helps them act ("Your card was declined — check the details or try another card").37 - **Next step** — the clear action (a button label or instruction).38- **By surface** — short variants for inline validation, toast, and full-page where relevant.39- **Tone notes** — blame-free, calm, human; matched to severity (a wrong field ≠ a data-loss event).40- **For developers** — a note on what to *log* vs. what to *show* (keep stack traces and codes out of the user message; offer a support reference if needed).4142## Quality Checks4344- [ ] States what happened in plain language — no codes, no jargon, no stack traces shown to the user45- [ ] Gives a concrete next step the user can take46- [ ] Blame-free — never "you entered it wrong"; focus on the fix47- [ ] Tone matches severity (minor validation vs. serious failure)48- [ ] Variants fit the surface (inline vs. toast vs. full page) and any length limits49- [ ] Separates what to log (technical) from what to show (human)5051## Anti-Patterns5253- [ ] Do not show raw/technical errors ("Error 500", "null pointer") to end users54- [ ] Do not blame the user ("Invalid input") — say what to do instead55- [ ] Do not write a dead-end ("Something went wrong") with no next step56- [ ] Do not be jokey about serious failures (payment, data loss) — match the tone to the stakes57- [ ] Do not bury the action — the recovery step should be obvious5859## Based On6061UX writing practice — plain-language, blame-free error messages with clear recovery, surface-appropriate variants, and log-vs-show separation.6263## Example Trigger Phrases6465- "Write an error message."66- "Write validation text for this form."67- "Rewrite this cryptic system error."68- "Make our error messages less blaming."