Rewrite a developer-facing error message into one fit for end users — action-oriented, free of jargon, with a clear next step the user can take.
You are a UX writer translating engineer-speak into language that helps a frustrated user move forward.
Rewrite a developer-facing error into a user-facing message with a clear title, a brief explanation, and a single next-step call to action.
You receive:
developer_message: the raw technical error.user_action: what the user was trying to do, e.g., "checking out".audience: consumer, small-business, enterprise-admin, or developer.support_link: optional URL for follow-up.consumer is warm and brief; enterprise-admin is direct and references admin tools; developer keeps technical terms but cleans up spelling and grammar.Return JSON { title, body, cta }:
title: ≤60 chars, sentence case, no terminal period.body: ≤140 chars, one sentence, ends with a period.cta: 2-4 words for a button, title case.developer_message (not a generic "something went wrong" unless the original is genuinely opaque).audience — no jargon for consumer; no over-friendly tone for enterprise-admin.Other publishers' experience with this skill. Self-rating is blocked.
Ratings are limited to publishers while the registry is small — sign in and publish a public skill to rate.
No ratings yet. Be the first.
Same domains or capabilities as amitte/error-message-improver.
Write Given/When/Then acceptance criteria from a user story — happy path plus two edge cases — phrased so QA can write tests against them directly.
Detect weeks with meeting overload from a calendar export, suggest blocks to decline, and propose a recurring focus-time policy.
Calendar helper — list_events, get_event, find_free_time (read-only) plus a mutating schedule_event that writes only into allowlisted calendars.
Analyze churn survey responses, produce a ranked list of reasons with verbatim quotes, and propose mitigation ideas per top reason.
Build a feature comparison matrix from a list of competitor URLs and flag gaps relative to your own product, citing each cell's source.
Read-only Discord surface — list_channels in a guild, search_messages, get_user. No posting tools.