error-message-writer
/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.
- Author
- SkillMedev ↗
- Repository
- skills ↗
- Licence
- MIT
- Last repository change
- 13.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 13.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
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.
Triggers from the description
Original author description
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.
How it works
- The three jobs of an error message
- Process
- Rules
- Tone calibration
- Structure of a message
- Examples of the rewrite
- Anti-patterns
- Output
SKILL.md preview
--- name: error-message-writer description: 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. metadata: title: "Error Message Writer" --- # 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." - **Be blame-free.** Avoid "you" + accusation. Not "You entered an invalid email." Better: "That email address doesn't look right - check for typos." Passive or shared blame de-escalates. - **Plain language.** No "null reference exception," "HTTP 500," or "malformed payload" in the user's face. Translate. - **Match severity to tone.** A failed payment is serious; a wrong password is routine. Don't alarm over trivia, don't joke during data loss. - **No dead ends.** Every error offers a path: retry, edit, go back, get help. - **Preserve the user's work.** Tell them their input is saved, if it is. Losing a long form to a vague error is the worst case. ## Tone calibration - Routine validation: light, helpful, even friendly. - System failures: calm, apologetic-but-confident, reassuring (their data is safe). - Security/destructive: clear and serious, no humor. ## Structure of a message - **Title/lead**: what happened, in 3-8 words. - **Body**: the recovery action, one or two sentences. - **Optional**: a link to help, or an error code for support (small, secondary). ## Examples of the rewrite - Before: "Error 403." After: "You don't have access to this page. Ask an admin to grant you permission, or switch to an account that does." - Before: "Invalid input." After: "Phone numbers need 10 digits. Example: 555-123-4567." - Before: "Upload failed." After: "That file is too large to upload (max 25 MB). Try compressing it or choosing a smaller file." ## Anti-patterns - Humor during data loss or security errors. - Jargon, codes, or stack traces shown to end users. - "Please try again later" with no other guidance. - Blaming the user. ## Output Deliver the rewritten message(s). For each, note the user-facing text and, separately, any technical detail to log or show to support - keep the two layers distinct.
Versions
The database has no other skills named error-message-writer.
Database snapshot: 13.11.2026 · package version e7689c93dc68 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100writing-error-messages
Use when writing, reviewing, or rewriting user-facing error messages, validation messages, form errors, empty/error states, auth errors, failure notifications, retry/support copy, CLI errors, or API errors humans will read. Helps make errors specific, actionable, non-blaming,… - 100error-handling-recovery
Audit and implement an app's error UX end-to-end: rewrite error messages, place them correctly, add recovery actions, and build error states for validation, network, permission, system, and 404 failures. Use when the user says 'improve my error handling', 'my error messages… - 100ux-writer
Use this skill when crafting microcopy, UI text, or in-product writing—error messages, tooltips, button labels, empty states, onboarding flows, and confirmation dialogs. Trigger phrases: ''write microcopy for'', ''write UI copy'', ''write error messages'', ''write onboarding… - 100copy-write
Write UX copy for a feature, flow, or component — buttons, errors, empty states, tooltips. Use when asked to "write the copy for this flow", "word this error message", or "write empty state copy". - 100ux-writing-audit
Audits an existing corpus of product copy - buttons, labels, errors, empty states, toasts, tooltips - against clarity, consistency, voice, and actionability heuristics, and delivers a scored findings table with rewrites plus a reusable glossary. Use when someone asks "audit our… - 100impeccable-clarify
Improve UX copy, labels, error messages, and microcopy in a user interface. Use when interface text is unclear, ambiguous, jargon-heavy, or inconsistent — rewrite it so users understand what happened, what matters, and what to do next.