clarify

Rewrites unclear UX copy, error messages, labels, and microcopy for interface comprehension.

Updated Apr 20, 2026
One-click install
npx skills add https://github.com/ShyamRavidath/oscc-detection-v2 --skill clarify-shyamravidath
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clarify
Source: https://github.com/ShyamRavidath/oscc-detection-v2/tree/main/.agents/skills/clarify
Command: npx skills add https://github.com/ShyamRavidath/oscc-detection-v2 --skill clarify-shyamravidath

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Confusing interface text—vague error messages, jargon-heavy labels, and ambiguous instructions—frustrates users, causes errors, and generates support tickets. This Skill systematically identifies and rewrites unclear UX copy so users understand what happened and what to do next. ## Core Features & Use Cases - Copy Auditing: Detects jargon, ambiguity, passive voice, wrong tone, and missing context in existing interface text. - Pattern-Based Rewrites: Provides before/after guidance for error messages, form labels, buttons, tooltips, empty states, success messages, loading states, confirmation dialogs, and navigation labels. - Clarity Principles: Enforces rules like being specific, active, concise, and consistent, with an explicit list of anti-patterns to avoid. - Use Case: A developer ships a form showing "Invalid input" on failure. Use this Skill to rewrite it as "Email addresses need an @ symbol. Try: [email protected]" and apply the same treatment across all form states. ## Quick Start Ask the AI to review and improve the error messages and button labels in your app's settings page using the clarify skill.

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 app?

Explain what went wrong in plain language, suggest how to fix it, and avoid blaming the user. Replace codes like "Error 403" with "You don't have permission to view this page. Contact your admin for access."

How to improve confusing form labels and placeholder text?

Use specific labels like "Date of birth" instead of abbreviations, show format expectations with examples, and never rely on placeholders as the only label since they disappear when users type.

What makes good button and CTA text in UX writing?

Describe the specific action with active voice, such as "Save changes" or "Create account" instead of generic "Submit" or "OK". Match the user's mental model of what happens next.

When should I use confirmation dialogs in a UI?

Reserve confirmations for risky or destructive actions only. State the specific action and consequence, like "Delete 'Project Alpha'? This can't be undone," with a clear button label such as "Delete project."

What are common UX writing mistakes to avoid?

Avoid unexplained jargon, blaming users, vague messages like "Something went wrong," unnecessary passive voice, humor in error states, and inconsistent terminology across the interface.