error-message-writer
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.
npx skills add mohitagw15856/pm-claude-skills --skill error-message-writer --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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** — s
- Working from a brief
- Required Inputs
- Output Format
- Error Message: [scenario]
- Quality Checks
- Anti-Patterns
- Based On
What does the error-message-writer skill do?
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.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill error-message-writer --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.