clarify

Rewrites unclear UX copy, error messages, labels, and instructions for interface comprehension.

Updated Apr 15, 2026
One-click install
npx skills add https://github.com/joaopaulotr/PesquiseMaisHealth --skill clarify-joaopaulotr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clarify
Source: https://github.com/joaopaulotr/PesquiseMaisHealth/tree/main/.agents/skills/clarify
Command: npx skills add https://github.com/joaopaulotr/PesquiseMaisHealth --skill clarify-joaopaulotr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Confusing interface text frustrates users, causes errors, and generates support tickets. This Skill identifies jargon, ambiguity, passive voice, and tone mismatches in your product copy and rewrites it so users understand immediately. ## Core Features & Use Cases - Copy Assessment: Diagnoses clarity problems including jargon, ambiguity, excessive length, and missing context in existing interface text. - Systematic Rewriting: Improves error messages, form labels, button text, tooltips, empty states, success messages, loading states, confirmation dialogs, and navigation labels. - Clarity Principles: Enforces specific, concise, active, human, helpful, and consistent writing across all product copy. - Use Case: Your app shows "Error 403: Forbidden" to users. Use this Skill to rewrite it as "You don't have permission to view this page. Contact your admin for access." ## Quick Start Ask the AI to review and improve the error messages and button labels in your app's settings page for clarity.

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 applicable.

How to write better UX microcopy for buttons and CTAs?

Describe the specific action using active voice with a verb plus noun, such as "Create account" or "Save changes" instead of generic text like "Submit" or "OK". Match the wording to the user's mental model of the task.

What makes form labels and instructions clear to users?

Use specific labels like "Date of birth" instead of abbreviations, show format expectations with placeholder examples, and place instructions before the field. Never rely on placeholders as the only label since they disappear when users type.

When should confirmation dialogs be used in UX writing?

Reserve confirmations for risky or destructive actions only. State the specific action and its consequences, such as "Delete 'Project Alpha'? This can't be undone," and use clear button labels like "Delete project" rather than "Yes".

Why does passive voice hurt UX copy clarity?

Passive voice like "Your file has been uploaded" hides who performed the action and feels impersonal. Active voice such as "We uploaded your file" is more direct, human, and easier for users to parse quickly.