clarify

Identify and rewrite unclear UX copy across web and mobile interfaces.

Updated Feb 5, 2026
One-click install
npx skills add https://github.com/mheers/opencode-sandbox --skill clarify-mheers
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clarify
Source: https://github.com/mheers/opencode-sandbox/tree/main/skills/clarify
Command: npx skills add https://github.com/mheers/opencode-sandbox --skill clarify-mheers

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Clear, concise copy often remains unclear, causing user confusion, errors, and support tickets. This Skill teaches how to identify and fix unclear UX copy to improve usability.

Core Features & Use Cases

  • Identify clarity problems (jargon, ambiguity, passive voice, length, assumptions, missing context, tone mismatch).
  • Plan and implement clear copy changes based on a structured clarity framework.
  • Use Case: When onboarding copy or error messages confuse users, rewrite for clarity to reduce support tickets and increase conversion.

Quick Start

Identify unclear copy in your UI and rewrite it 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 UX copy in my interface?

Rewriting unclear UX copy involves identifying jargon, passive voice, and missing context, then applying a structured clarity framework to revise onboarding text and microcopy for improved user comprehension.

What makes error messages confusing and how do I fix them?

Confusing error messages usually contain jargon, ambiguity, or tone mismatches. You fix them by evaluating the text against a clarity framework and rewriting it to provide missing context and reduce support tickets.

Do I need a style guide to rewrite onboarding microcopy for clarity?

Yes, a style guide is required to generate and validate clearer copy. It provides the standards needed to systematically plan and implement microcopy changes across web and mobile interfaces.

What is the best way to identify clarity problems in on-screen labels?

The best way to identify clarity problems in on-screen labels is to review them for jargon, ambiguity, passive voice, length, assumptions, missing context, and tone mismatch using a structured clarity framework.

Can I use this approach for both web and mobile onboarding text?

Yes, identifying and improving unclear UX copy applies to onboarding text and microcopy across both web and mobile interfaces, ensuring consistent usability and clarity on all platforms.