skills.rest
OmOc3
OmOc3COMMUNITY
Explore all skills by this author →
GitHub

clarify

Improves unclear interface text and UX copy across web and mobile platforms.

Updated Aug 27, 2026
Search Tags:#tone#clarity#microcopy#user-experience#error-messages#copy-editing#ux-writing
One-click install
npx skills add https://github.com/OmOc3/physica --skill clarify-omoc3
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: clarify
Source: https://github.com/OmOc3/physica/tree/main/.codex/skills/clarify
Command: npx skills add https://github.com/OmOc3/physica --skill clarify-omoc3

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Unclear interface text — error messages, labels, buttons, instructions, and microcopy — confuses users, causes errors, and increases support load. This Skill helps identify clarity problems and produce concise, actionable rewrites so users immediately understand what happened and what to do next.

Core Features & Use Cases

  • Diagnose clarity issues: Detect jargon, ambiguity, passive voice, missing context, tone mismatches, and length problems.
  • Targeted rewrites: Produce clear alternatives for error messages, form labels, CTAs, help text, empty and loading states, and confirmation dialogs with suggested fixes and examples.
  • Practical use case: Turn a vague "Invalid input" error into a friendly, actionable message that explains the problem and provides a concrete correction.

Quick Start

Ask the assistant to "Revise the error message 'Invalid input' into a concise, user-friendly message that explains the problem and how to fix it."

Frequently Asked Questions about clarify

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

FAQPage Schema
How do I rewrite UX copy to make error messages clear and actionable?▼

To rewrite UX copy and make error messages clear, you need to diagnose jargon and passive voice, then produce concise alternatives explaining what happened and what the user should do next. This targets interface text across web and mobile platforms.

What is the best way to improve unclear microcopy for empty and loading states?▼

Improving unclear microcopy for empty and loading states involves detecting tone mismatches and missing context, then generating concise, actionable instructional text. The rewritten copy respects length and localization constraints for web and mobile interfaces.

Does this approach work for fixing vague form labels and button text?▼

Yes, fixing vague form labels and button text is supported by diagnosing clarity issues like ambiguity and length problems. It produces targeted rewrites that transform unhelpful interface text into action-oriented, user-friendly microcopy.

Can I use this to fix "Invalid input" errors into user-friendly messages?▼

Yes, you can fix "Invalid input" errors by applying targeted rewrites that explain the specific problem and provide a concrete correction. This turns vague errors into friendly, actionable messages that guide the user on what to do next.

How do I ensure my UI copy revisions respect localization constraints?▼

To ensure UI copy revisions respect localization constraints, the rewriting process explicitly accounts for length limits and tone appropriateness. This guarantees the concise, actionable alternatives remain suitable for translation across different languages.

Related Skills

Explore More Design & Creative Skills→
byonk19-svgbyonk19-svg

clarify

Identify unclear UX copy and provide structured rewrite guidance for interface text.

Community
Advanced
loklaanloklaan

coding-error-messages

Rewrite raw error messages with context and suggested fixes.

Community
Basic
yeshan333yeshan333
94

clarify

Rewrite user interface copy for clarity and usability.

Community
Intermediate
a554b554a554b554
53

proofread

Correct grammar, spelling, and punctuation errors in text while respecting scope modifiers.

Community
Basic