clarify

Diagnose unclear UX copy and provide concise rewritten alternatives with rationale.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Unclear or poorly written interface text causes user confusion, errors, and increased support load; this Skill identifies clarity issues and produces concise, actionable rewrites so users understand what to do and why.

Core Features & Use Cases

  • Diagnose clarity problems: Detect jargon, ambiguity, passive voice, missing context, and tone mismatches in labels, error messages, CTAs, and instructions.
  • Rewrite and rationalize: Provide concise alternative copy, explain what was unclear, and recommend tone and action-oriented phrasing.
  • Use Case: During a design review, paste onboarding microcopy or an error message and receive rewritten lines, a short explanation of the issue, and guidance for implementation and localization.

Quick Start

Improve the following UI text by rewriting each line to be clearer, stating what was unclear, and suggesting the appropriate tone and next action.

Frequently Asked Questions about clarify

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

FAQPage Schema
How do I rewrite unclear UX copy for error messages and CTAs?

Rewrite unclear UX copy by identifying ambiguity, jargon, and tone mismatches, then generating concise alternative text with a brief rationale, recommended tone, and suggested next action. This approach applies to UI labels, error messages, CTAs, tooltips, and empty or loading states during design reviews.

How do I fix jargon and tone mismatches in microcopy during a design review?

Fix microcopy jargon and tone mismatches by diagnosing the text for passive voice and missing context, then applying concise rewritten alternatives that provide action-oriented phrasing and implementation guidance tailored for localization.

Does UX copy editing handle accessibility and length constraints for mobile interfaces?

UX copy editing handles accessibility and length constraints by respecting localization limits and clarity requirements across web and mobile interfaces. Rewritten alternatives ensure labels, form instructions, and tooltips remain actionable and clear for all users.

What is the best way to improve onboarding text and empty state instructions?

Improve onboarding text and empty state instructions by diagnosing clarity issues and producing concise, actionable rewrites. The process explains what was unclear, recommends an appropriate tone, and suggests the next action to reduce user confusion and support load.

Why does unclear interface text increase support load and how can copy editing help?

Unclear interface text increases support load by causing user confusion and errors through ambiguity, jargon, and missing context. Copy editing helps by providing concise rewritten alternatives with a rationale and tone guidance, ensuring users understand what to do.

Can I use automated copy editing for tooltips and form instructions in QA workflows?

Automated copy editing can be used for tooltips and form instructions in QA workflows to identify tone mismatches and ambiguity. It produces rewritten lines with a short explanation of the issue and guidance for implementation and localization.