clarify

Analyze UI copy and generate improvement plans for clarity.

Updated Feb 23, 2026
One-click install
npx skills add https://github.com/mkloz/teamforge-frontend --skill clarify-mkloz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clarify
Source: https://github.com/mkloz/teamforge-frontend/tree/main/.agents/skills/clarify
Command: npx skills add https://github.com/mkloz/teamforge-frontend --skill clarify-mkloz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The clarify Skill tackles unclear, confusing, or poorly written interface text, enhancing the overall user experience and reducing user frustration.

Core Features & Use Cases

  • Copy Assessment: Analyze and pinpoint issues in text, including jargon, ambiguity, and passive voice.
  • Copy Improvement Plan: Develop strategies for clearer communication, focusing on primary messages, action items, and appropriate tones.
  • Systematic Improvement: Refine error messages, form labels, CTAs, help texts, empty states, success messages, loading states, confirmation dialogs, and navigation labels.
  • Clarity Principles: Apply specific rules for copy, such as specificity, conciseness, active voice, and helpfulness.
  • Verification: Test comprehension, actionability, brevity, consistency, and tone to ensure improvements are effective.

Quick Start

Analyze and improve unclear copy in your application using the clarify Skill and provide the targeted text for review.

Frequently Asked Questions about clarify

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

FAQPage Schema
How do I improve unclear UX writing and interface text in my application?

To improve unclear UX writing, analyze your interface text to identify jargon, ambiguity, and passive voice, then apply clarity principles like specificity, conciseness, and active voice to make the copy understandable and actionable.

What is the best way to write clear error messages and form labels for user interfaces?

Writing clear error messages and form labels requires systematic refinement to ensure text is helpful, concise, and consistent. You should verify comprehension and actionability so users easily understand and resolve interface issues.

How do I fix confusing microcopy in empty states and confirmation dialogs?

Fixing confusing microcopy involves developing a structured improvement plan for empty states and confirmation dialogs that focuses on primary messages, action items, and appropriate tones to enhance overall application usability.

Does this approach work for evaluating CTA and navigation label clarity?

Yes, this approach evaluates CTA and navigation label clarity by testing specificity, active voice, and helpfulness, ensuring the interface text remains appropriate and easily understood by the target audience.

When should I use a systematic copy assessment for interface text?

Use a systematic copy assessment when user frustration arises from poorly written interface text, allowing you to pinpoint issues in microcopy, success messages, and loading states to verify brevity and consistency.