skills.rest
Gyanano
GyananoCOMMUNITY
Explore all skills by this author →
GitHub

clarify

Rewrite unclear UX copy into concise, actionable interface instructions.

5|Updated Mar 27, 2026
Search Tags:#clarity#microcopy#error-messages#copy-editing#tone-guidance#ux-writing
One-click install
npx skills add https://github.com/Gyanano/Bower --skill clarify-gyanano
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: clarify
Source: https://github.com/Gyanano/Bower/tree/main/.agents/skills/clarify
Command: npx skills add https://github.com/Gyanano/Bower --skill clarify-gyanano

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Skill removes ambiguity from error messages, labels, microcopy, and instructions so every interface cue becomes actionable and confidence-building. It prevents frustrated clicks, stalled workflows, and support tickets caused by unclear wording and vague calls to action.

Core Features & Use Cases

  • Context gathering first: Follow the /frontend-design protocol and, when needed, launch /teach-impeccable so you understand the audience technical level and users’ mental state before rewriting.
  • Targeted copy repair: Audit jargon, passive phrasing, missing context, and tone mismatch, then craft concise, active, and empathetic replacements across buttons, tooltips, empty states, confirmations, and success banners.
  • Use case: When an onboarding error message keeps users guessing, analyze the expectation mismatch, clarify the primary action, and deliver an improved message that says what happened, why it matters, and what to do next.

Quick Start

Ask clarify to assess the confusing form label and rewrite it into a specific, user-ready instruction that matches the desired tone.

Frequently Asked Questions about clarify

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

FAQPage Schema
How do I rewrite confusing UX copy into clear microcopy?▼

To rewrite confusing UX copy into clear microcopy, you must first gather audience context and mental-state data, then audit jargon and passive phrasing to craft concise, active replacement text for buttons and tooltips.

What is the best way to fix unclear error messages in an interface?▼

Fixing unclear error messages requires analyzing the user expectation mismatch, clarifying the required primary action, and delivering text that explicitly states what happened, why it matters, and what to do next.

How do I improve labels and instructions for empty states and tooltips?▼

Improving labels and instructions for empty states and tooltips involves auditing existing copy for tone mismatch and missing context, then generating targeted, empathetic replacements that build user confidence.

Do I need audience technical level context before rewriting UX microcopy?▼

Yes, gathering audience technical level context and user mental-state information is required before rewriting UX microcopy, ensuring the revised interface instructions match user expectations and comprehension levels.

Why does vague microcopy cause stalled workflows and support tickets?▼

Vague microcopy causes stalled workflows and support tickets because ambiguous wording and missing context prevent users from understanding interface intent, leading to frustrated clicks and failed required actions.

Related Skills

Explore More Design & Creative Skills→
CertChain-IUHCertChain-IUH

clarify

Identify and improve unclear UX copy in web and mobile interfaces.

Official
Intermediate
vobasevobase
59

clarify

Rewrite unclear interface text into concise, actionable UX copy.

Official
Intermediate
wasintohwasintoh
90

design-excellence

Polish AI-built UI with color, typography, spacing, and motion guidelines.

Community
Basic
JiaxuanZou0714JiaxuanZou0714
5

clarify

Analyze UX copy for jargon, ambiguity, and passive voice, then refine it.

Community
Intermediate