skills.rest
shuretokki
shuretokkiCOMMUNITY
Explore all skills by this author →
GitHub

clarify

Rewrite unclear interface text into concise, actionable microcopy.

Updated Aug 23, 2026
Search Tags:#tone#clarity#microcopy#usability#error-messages#copy-editing#ux-writing
One-click install
npx skills add https://github.com/shuretokki/void --skill clarify-shuretokki
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: clarify
Source: https://github.com/shuretokki/void/tree/main/.agents/skills/clarify
Command: npx skills add https://github.com/shuretokki/void --skill clarify-shuretokki

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Improve unclear, confusing, or poorly written interface text so users understand what happened and what to do next, reducing errors, frustration, and support load.

Core Features & Use Cases

  • Diagnose clarity issues: Identify jargon, ambiguity, passive voice, missing context, and tone mismatches in error messages, labels, buttons, tooltips, and instructions.
  • Strategic rewrites: Define the primary message, required action, tone, and constraints, then produce concise, actionable copy that fits UI constraints and localization needs.
  • Practical examples: Turn terse errors like "Invalid input" into "Please enter a valid email address, for example [email protected]" and change generic CTAs like "Submit" into "Create account".

Quick Start

Improve the error message "Error 403: Forbidden" into a clear, user-friendly message that explains why access is denied and what steps the user can take next.

Frequently Asked Questions about clarify

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

FAQPage Schema
How do I rewrite confusing error messages into clear UX microcopy?▼

To rewrite confusing error messages, you replace jargon and passive voice with concise, actionable UX microcopy. This clarifies what happened and guides users on immediate next steps, reducing task abandonment and support load.

What makes good UX writing for form labels and buttons?▼

Good UX writing for form labels and buttons uses clear, specific action verbs like "Create account" instead of generic terms like "Submit." This ensures users instantly understand the required action and expected input without ambiguity.

How do I improve UI text for different audience technical levels?▼

Improving UI text requires gathering design context about the users' mental state and technical level. This context helps tailor microcopy to their comprehension, ensuring the rewritten message fits UI constraints and localization needs.

Can I use this approach to fix empty states and onboarding instructions?▼

Yes, you can fix empty states and onboarding instructions by diagnosing missing context and tone mismatches. This produces strategic rewrites that explain the current state and provide actionable guidance across web and mobile interfaces.

What is the best way to turn generic CTAs into actionable microcopy?▼

The best way to turn generic CTAs into actionable microcopy is to define the primary message and required action first. This produces specific button text like "Create account" instead of "Submit," directly increasing task completion rates.

Related Skills

Explore More Design & Creative Skills→
jcdiv47jcdiv47

clarify

Rewrite unclear UI microcopy into concise, actionable, localization-ready text.

Community
Intermediate
soeiroosoeiroo

ux-writing

Generate concise UI copy for microcopy, error messages, and onboarding flows.

Community
Basic
CatsofsufferingCatsofsuffering
5

clarify

Analyze and rewrite unclear interface text for comprehension and actionability.

Community
Intermediate
bfree-trainerbfree-trainer
60

clarify

Rewrite unclear UI copy to reduce jargon and ambiguity.

Official
Intermediate