clarify

Rewrite unclear UX copy into clear, actionable text across interfaces.

Updated Jan 30, 2026
One-click install
npx skills add https://github.com/teegin-g/Slopcast --skill clarify-teegin-g
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clarify
Source: https://github.com/teegin-g/Slopcast/tree/main/.cursor/skills/clarify
Command: npx skills add https://github.com/teegin-g/Slopcast --skill clarify-teegin-g

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Unclear UX copy leads to user confusion, mistakes, and support overhead. This Skill provides a structured approach to identify ambiguity in interface text and deliver clear, actionable copy that improves comprehension and reduces friction.

Core Features & Use Cases

  • UX Copy Audit: Detect jargon, ambiguity, passive voice, and missing context across error messages, labels, placeholders, tooltips, and help text.
  • Copy Improvement Plan: Propose specific rewrites, tone adjustments, and consistency fixes aligned with brand voice and accessibility guidelines.
  • Use Case: For a confusing onboarding screen, generate a set of concise, action-oriented alternatives and rationale to guide implementation.

Quick Start

Provide a concise rewrite for a UI screen's primary copy to improve clarity and user comprehension.

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 form labels?

Audit interface text for missing context and passive voice, then generate specific rewrites. Propose concise, action-oriented alternatives with rationale to improve comprehension, reduce support overhead, and eliminate user friction.

What is the best way to improve microcopy clarity for onboarding flows?

Improve microcopy clarity by detecting ambiguity and passive voice in onboarding screens. Provide structured copy improvement plans proposing tone adjustments and consistency fixes aligned with brand voice to deliver clear, actionable text.

Why does confusing interface text lead to higher support overhead?

Confusing interface text increases support overhead because unclear UX copy causes user mistakes and friction. Rewriting ambiguous error messages and tooltips into clear, actionable text improves comprehension and reduces support requests.

Can I audit tooltips and empty states for accessibility and tone consistency?

Yes, you can audit tooltips and empty states for accessibility and tone consistency. Identify passive voice and missing context, then apply specific rewrites and tone adjustments aligned with brand voice and accessibility guidelines.

How do I fix passive voice and jargon in UX writing?

Fix passive voice and jargon in UX writing by auditing interface text to detect ambiguity. Rewrite to clear, actionable text ensuring changes adhere to consistent tone, brevity, directness, and accessibility guidelines.