clarify

Rewrites unclear UX copy, error messages, labels, and microcopy for clearer interfaces.

Updated May 4, 2026

Search Tags:#clarity #microcopy #copywriting #usability #ux writing #error messages #interface text

Ready to run

npx skills add https://github.com/Gito125/gideon_portfolio --skill clarify-gito125

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: clarify
Source: https://github.com/Gito125/gideon_portfolio/tree/main/.github/skills/clarify
Command: npx skills add https://github.com/Gito125/gideon_portfolio --skill clarify-gito125

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Confusing interface text causes user errors, frustration, and support tickets. This Skill identifies jargon, ambiguity, passive voice, and tone mismatches in product copy and rewrites it so users immediately understand what happened and what to do next. ## Core Features & Use Cases - Copy Assessment: Diagnoses clarity problems in existing text, including jargon, ambiguity, wrong length, and missing context, while factoring in audience technical level and user mental state. - Systematic Rewriting: Improves error messages, form labels, button text, tooltips, empty states, success messages, loading states, confirmation dialogs, and navigation labels using before/after patterns. - Clarity Verification: Checks rewritten copy for comprehension, actionability, brevity, consistency, and appropriate tone. - Use Case: A developer ships a form showing "Invalid input" on failure. Use this Skill to rewrite it as "Email addresses need an @ symbol. Try: [email protected]" and apply the same principles across the rest of the product. ## Quick Start Ask the assistant to review and rewrite the error messages and button labels in your app for clarity.

Frequently Asked Questions about clarify

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I write better error messages for my app?▼

Explain what went wrong in plain language, suggest how to fix it, and avoid blaming the user. Replace codes like "Error 403: Forbidden" with "You don't have permission to view this page. Contact your admin for access."

How to improve UX writing and microcopy in a product?▼

Audit copy for jargon, ambiguity, passive voice, and missing context, then rewrite each element to state one clear message and next action. Apply consistent terminology across error messages, labels, buttons, and empty states.

What makes a good button label or CTA text?▼

Good button labels describe the specific action using active voice, such as "Create account" or "Save changes" instead of "Submit" or "OK". Match the user's mental model and be specific about the outcome.

Should confirmation dialogs be used for every action?▼

No, confirmations should be reserved for risky or destructive actions. State the specific action and consequences, like "Delete 'Project Alpha'? This can't be undone", and use clear button labels such as "Delete project" instead of "Yes".

Why is passive voice bad in UX copy?▼

Passive voice hides who did what, making messages harder to parse. "We uploaded your file" is clearer than "Your file has been uploaded" because it states the actor and action directly.