clarify

Rewrite unclear interface copy into concise, active, and empathetic wording.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/FairladyZ625/Obsidian-Brain-OS --skill clarify-fairladyz625
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clarify
Source: https://github.com/FairladyZ625/Obsidian-Brain-OS/tree/main/skills/recommended/clarify
Command: npx skills add https://github.com/FairladyZ625/Obsidian-Brain-OS --skill clarify-fairladyz625

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Unclear, ambiguous, or jargon‑filled interface text confuses users, increases errors, and damages the product experience.

Core Features & Use Cases

  • Systematic analysis of copy to detect jargon, ambiguity, passive voice, length issues, and tone mismatches.
  • Structured improvement guide covering error messages, form labels, buttons, tooltips, empty states, success messages, loading states, confirmations, and navigation.
  • Real‑world use: refine a login error prompt from “Invalid credentials” to a friendly explanation with remediation steps.

Quick Start

Ask the clarify skill to improve the wording of a button label like “Submit”.

Frequently Asked Questions about clarify

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

FAQPage Schema
How do I write better error messages for UX?

To write better UX error messages, replace vague copy like "Invalid credentials" with friendly explanations that include remediation steps, maintaining an empathetic tone and active voice.

How do I improve unclear interface text and microcopy?

Improve unclear interface text by systematically analyzing microcopy to detect jargon, ambiguity, and passive voice, then generating concise, active, and user-friendly wording tailored to the audience.

Can I refine button labels and tooltips for a web app?

Yes, you can refine button labels and tooltips by applying copy clarity principles to web or app products, ensuring text is concise, active, and matches the user's mental state and technical level.

What is the best way to fix confusing form labels and empty states?

The best way to fix confusing form labels and empty states is to apply structured design guidelines that detect tone mismatches and length issues, producing clear and empathetic interface wording.

How do I make UI copy crystal clear for non-technical users?

Make UI copy crystal clear by adjusting the wording based on the audience's technical level, removing jargon and ambiguous phrasing while following design principles for navigation and success messages.