clarify

Identify and rewrite unclear interface text across web and app interfaces.

1|Updated May 6, 2026

Search Tags:#clarity #microcopy #usability #labels #error-messages #copyediting #ux-writing

Ready to run

npx skills add https://github.com/yckkkk/reo --skill clarify-yckkkk

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: clarify
Source: https://github.com/yckkkk/reo/tree/main/.agents/skills/clarify
Command: npx skills add https://github.com/yckkkk/reo --skill clarify-yckkkk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify and improve unclear, confusing, or poorly written interface text to make the product easier to understand and use.

Core Features & Use Cases

Clarity audit of UI copy: Identify jargon, ambiguity, passive voice, length, assumptions, missing context, tone mismatches.
Improvement plan & execution: Define primary message, tone, constraints; propose rewritten copy for labels, error messages, and CTAs.
Consistent application across UI: Apply changes to common areas (errors, forms, buttons, help text, empty states, loading, confirmations, navigation) with a practical example.

Quick Start

Analyze the provided UX copy, identify clarity issues, and return a rewritten version with concrete, actionable improvements.

Frequently Asked Questions about clarify

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

FAQPage Schema

How do I improve unclear interface text and make UX copy more usable?▼

UX copy clarity audits identify jargon, ambiguity, passive voice, and tone mismatches across interface text. By evaluating labels, error messages, and empty states, you can pinpoint missing context and confusing language that prevents users from understanding how to navigate your product effectively.

How do I write clear error messages and form labels for web and app interfaces?▼

Improving UX copy involves analyzing existing interface text to identify clarity issues like jargon and ambiguity, then returning a rewritten version with concrete, actionable improvements. You provide the current copy, and the analysis outputs rewritten labels, error messages, and CTAs following clarity principles.

What is the best way to audit UI copy for consistency across empty states and navigation labels?▼

The best way to audit UI copy for consistency is to systematically review common areas like empty states, loading indicators, and navigation labels against established clarity principles. This ensures consistent terminology and actionable improvements are applied uniformly across the entire product interface.

Can I fix poorly written button texts and loading indicators for both web and mobile apps?▼

Yes, you can fix poorly written button texts and loading indicators for both web and mobile apps. The process applies clarity principles to identify tone mismatches and length issues, proposing rewritten copy that maintains consistent terminology and actionable guidance across all app interfaces.

When should I review microcopy for clarity principles and consistent terminology?▼

You should review microcopy for clarity principles and consistent terminology whenever users struggle with confusing interface text, encounter jargon, or face error states lacking context. Regular audits ensure help text, confirmations, and CTAs remain actionable and aligned with user expectations.