clarify

Identify ambiguity, jargon, and tone mismatches in user interface copy.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Clarify fixes unclear interface copy—like confusing labels, weak instructions, and unhelpful error messages—so users can understand what’s happening and what to do next.

Core Features & Use Cases

  • Assess copy clarity: Identify ambiguity, jargon, tone mismatch, missing context, passive voice, and length issues.
  • Plan and rewrite systematically: Produce a clearer primary message, next action, appropriate tone, and constraint-aware wording.
  • Improve key UX writing moments: Error messages, form labels and instructions, CTAs, help text, empty states, success/loading states, confirmations, and navigation/wayfinding.
  • Use-case: When a user reports “I don’t know what this button does” or “the error doesn’t tell me how to fix it,” rewrite the relevant copy to reduce confusion and support tickets.

Quick Start

Use the clarify skill to rewrite the confusing UI text described by the user and provide clearer labels, instructions, and error messaging.

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 my application interface?

Rewriting error messages involves assessing copy for ambiguity, jargon, and tone mismatch, then applying constraints on brevity and active voice. This produces clear, actionable feedback that tells users exactly what happened and how to resolve the issue.

What is the best way to improve unclear UX microcopy and form labels?

Improving UX microcopy requires assessing labels and instructions for ambiguity and tone mismatch, then applying a rewriting plan with constraints on brevity and active voice. This ensures consistent terminology and clear next-step guidance for user comprehension.

How do I fix confusing CTA and navigation labels to improve user comprehension?

Fix confusing CTA and navigation labels by assessing them for ambiguity, tone mismatch, and length issues, then rewriting with brevity and active voice constraints. This produces clear, actionable primary messages that guide users to their next step.

Can I systematically rewrite empty states and success messages for better clarity?

Yes, you can systematically rewrite empty states and success messages by following a copy-clarity assessment plan. This identifies missing context and applies constraint-aware wording to ensure the interface copy is instantly understandable and actionable.

Why does my interface copy confuse users and increase support tickets?

Interface copy confuses users and drives support tickets when it contains jargon, passive voice, or missing context. Assessing the text for tone mismatch and ambiguity allows you to rewrite it with actionable, clear guidance that reduces user confusion.