skills.rest
l0lxl0lw
l0lxl0lwCOMMUNITY
Explore all skills by this author →
GitHub

clarify

Rewrites unclear UX copy, error messages, labels, and microcopy for interface clarity.

Updated Dec 18, 2025
Search Tags:#microcopy#usability#ux writing#content design#error messages#interface text#copy clarity
One-click install
npx skills add https://github.com/l0lxl0lw/dotfiles --skill clarify-l0lxl0lw
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: clarify
Source: https://github.com/l0lxl0lw/dotfiles/tree/main/ai/shared/skills/impeccable/clarify
Command: npx skills add https://github.com/l0lxl0lw/dotfiles --skill clarify-l0lxl0lw

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 UX copy and rewrites it so users immediately understand what happened and what to do next. ## Core Features & Use Cases - Copy Assessment: Diagnoses clarity problems including jargon, ambiguity, excessive length, wrong assumptions, and tone mismatches based on audience 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 with before/after patterns. - Clarity Verification: Checks rewritten copy for comprehension, actionability, brevity, consistency, and appropriate tone. - Use Case: A settings page shows "Error 403: Forbidden" and a generic "Submit" button. The Skill rewrites these as "You don't have permission to view this page. Contact your admin for access." and "Save changes". ## Quick Start Ask the AI to review and improve the unclear copy in a specific feature or component, such as the error messages on your checkout form.

Frequently Asked Questions about clarify

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

FAQPage Schema
How do I improve unclear error messages in my app?▼

Explain what went wrong in plain language, suggest how to fix it, and avoid blaming the user. For example, replace "Invalid input" with "Email addresses need an @ symbol. Try: [email protected]" and link to help resources when relevant.

How to write better button and CTA text for interfaces?▼

Describe the specific action using active voice with a verb and noun, such as "Create account" or "Save changes" instead of "Submit" or "OK". Match the user's mental model and be specific about the outcome.

What makes UX copy unclear or confusing?▼

Common problems include jargon users don't understand, ambiguous phrasing, passive voice, excessive length, assumed knowledge, missing context, and tone mismatches. Assessment should consider audience technical level and the user's mental state in context.

Should confirmation dialogs be used for every action?▼

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

When should placeholder text not be used as form labels?▼

Placeholders should never be the only labels because they disappear when users type. Use clear, specific labels above the field and reserve placeholders for showing format examples, putting instructions before the field rather than after.

Related Skills

Explore More Design & Creative Skills→
mahou-labsmahou-labs
1

clarify

Rewrite unclear UX copy into clear, actionable language for interfaces.

Official
Intermediate
StartaleGroupStartaleGroup
3

clarify

Rewrite unclear UX copy across web and mobile app interfaces.

Official
Advanced
acabreragnzacabreragnz

accessibility-compliance

Audit web interfaces for WCAG 2.2 accessibility compliance and implement ARIA patterns.

Community
Advanced
gilinachumgilinachum
3

panel-interview

Plan multi-speaker sessions including panel discussions, fireside chats, and podcast interviews.

Community
Intermediate