clarify

Rewrite unclear UI text into actionable, audience-appropriate copy across interfaces.

Updated Apr 29, 2026
One-click install
npx skills add https://github.com/jean-sotil/presskitpro-webapp --skill clarify-jean-sotil
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clarify
Source: https://github.com/jean-sotil/presskitpro-webapp/tree/main/.agents/skills/clarify
Command: npx skills add https://github.com/jean-sotil/presskitpro-webapp --skill clarify-jean-sotil

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It improves unclear product text so users understand what’s happening and what to do next, even when they’re stressed by errors or unsure about forms and labels.

Core Features & Use Cases

  • Unclear copy diagnosis: Identifies causes like jargon, ambiguity, missing context, bad tone, poor length, and passive voice so the message matches the user’s real mental model.
  • Targeted rewriting across UI surfaces: Refines error messages, form labels/instructions, CTA and button text, help/tooltips, empty states, success messages, loading states, and confirmations.
  • Clarity-first writing rules: Uses active voice, avoids blame, provides actionable guidance with examples when helpful, and keeps wording concise and consistent.

Use cases include rewriting a confusing validation error into a specific fix with an example, converting vague button text into an action-oriented CTA, and updating empty-state messaging to explain why nothing is present and what to do next.

Quick Start

Invoke this skill to improve the confusing UI text shown to you, then rewrite it with clear labels, helpful instructions, and actionable error guidance.

Frequently Asked Questions about clarify

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

FAQPage Schema
How do I rewrite confusing UX microcopy to improve product usability?

To rewrite confusing UX microcopy, you diagnose unclear text for jargon, ambiguity, and passive voice, then apply active voice and actionable guidance to produce specific, tone-appropriate copy improvements that users understand immediately.

How do I fix confusing error messages and form labels in a user interface?

Fix confusing error messages and form labels by identifying causes like bad tone or missing context, then rewriting the text with specific fixes, helpful examples, and concise wording that matches the user's mental model.

What is the best way to write clear empty states and loading states for apps?

The best way to write clear empty states and loading states is to explain why content is absent or loading and provide actionable next steps, ensuring the messaging is concise, consistent, and free of jargon.

How do I convert vague button text into an action-oriented CTA?

Convert vague button text into an action-oriented CTA by assessing the instruction design context, removing ambiguity, and rewriting the label with clear, active voice that tells users exactly what happens upon clicking.

Can I use a systematic protocol to diagnose tone and clarity issues across UI surfaces?

Yes, you can use a systematic clarity assessment protocol to diagnose tone and clarity issues across UI surfaces, identifying missing context and poor length to refine tooltips, confirmations, and success messages.