clarify

Analyzes and rewrites unclear UX copy across error messages, labels, and buttons.

Updated Feb 12, 2026
One-click install
npx skills add https://github.com/Youneslahlali/MyWebsite --skill clarify-youneslahlali
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clarify
Source: https://github.com/Youneslahlali/MyWebsite/tree/main/.gemini/skills/clarify
Command: npx skills add https://github.com/Youneslahlali/MyWebsite --skill clarify-youneslahlali

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses confusing, unclear, or poorly written text within user interfaces, making products easier to understand and use.

Core Features & Use Cases

  • Identify Clarity Issues: Detects jargon, ambiguity, passive voice, excessive length, assumptions, and missing context in UX copy.
  • Contextual Assessment: Analyzes audience, user state, action, and constraints to inform improvements.
  • Systematic Improvement: Refines error messages, form labels, button text, help text, empty states, success messages, loading states, confirmation dialogs, and navigation.
  • Use Case: Improving the clarity of an error message like "Operation failed" to "Your request could not be completed due to a network issue. Please check your connection and try again."

Quick Start

Improve the clarity of the error message "Invalid input" by providing a more helpful explanation and example.

Frequently Asked Questions about clarify

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

FAQPage Schema
How do I improve unclear UX copy and error messages?

To improve unclear UX copy, you analyze text for jargon, ambiguity, passive voice, and missing context, then systematically refine error messages, form labels, and button text to enhance user interface understandability and usability.

What makes microcopy confusing for user interface design?

Microcopy becomes confusing when it contains jargon, ambiguity, passive voice, excessive length, assumptions, missing context, or tone mismatch, making the user interface harder to understand and navigate.

How do I write better UX copy for empty states and loading states?

Writing better UX copy for empty and loading states involves systematically refining the text by assessing the audience, user state, action, and constraints to ensure the message is clear and helpful.

What is the best way to fix unhelpful error messages in a user interface?

The best way to fix unhelpful error messages is to analyze them for missing context and ambiguity, then rewrite them systematically to explain the issue and provide a clear next action for the user.

Can I use this to refine form labels and button text?

Yes, you can systematically refine form labels, button text, confirmation dialogs, and navigation elements by evaluating the audience and constraints to improve overall interface clarity.