clarify

Analyzes UI text and recommends actionable rewrites for clarity and tone.

1|Updated Oct 27, 2025
One-click install
npx skills add https://github.com/sandrasocial/sselfie-9g --skill clarify-sandrasocial
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clarify
Source: https://github.com/sandrasocial/sselfie-9g/tree/main/.agents/skills/clarify
Command: npx skills add https://github.com/sandrasocial/sselfie-9g --skill clarify-sandrasocial

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Interfaces with unclear copy create user confusion, errors, and extra support load. This Skill identifies jargon, ambiguity, passive constructions, missing context, and tone mismatches, then recommends concise, user-focused rewrites so users know what happened and what to do next.

Core Features & Use Cases

  • Systematic assessment: Diagnose clarity problems like jargon, ambiguity, wrong tone, assumptions, and missing context.
  • Strategic planning: Define the primary message, required user action, appropriate tone, and constraints (length, localization).
  • Targeted rewrites: Produce actionable improvements for error messages, form labels, CTAs, tooltips, empty states, loading and confirmation dialogs, and success notices.
  • Use case: Convert a vague error ("Invalid input") into a helpful message that explains the problem and gives a specific example or next step.

Quick Start

Improve the following interface text for clarity, tone, and the next actionable step: paste the UI string and any context (audience level, device, and space constraints).

Frequently Asked Questions about clarify

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

FAQPage Schema
How do I write clearer UX microcopy for confusing error messages?

To improve unclear UX microcopy for error messages, diagnose the text for jargon and missing context, gather user constraints, and apply concise rewrites with tone suggestions that explain the problem and offer actionable next steps.

What makes a good form label versus a confusing one in interface design?

A good form label uses active language and avoids assumptions, whereas a confusing one relies on jargon or ambiguity. Assessing user intent and layout constraints allows you to rewrite labels for better user comprehension and reduced support friction.

How do I fix vague UI text like invalid input for mobile app onboarding?

Fixing vague UI text like invalid input involves replacing the generic message with a helpful explanation of the problem and providing a specific actionable next step tailored to the user's mental state and device constraints.

Can I use this approach to rewrite empty states and navigation tooltips with character limits?

Yes, you can rewrite empty states and navigation tooltips with character limits by defining the primary message, applying layout constraints, and generating concise, actionable rewrites that maintain user comprehension within restricted space.

When should I adjust tone guidelines for web and mobile confirmation dialogs?

Adjust tone guidelines for confirmation dialogs when there is a tone mismatch with the user's mental state. Defining the appropriate tone before rewriting ensures the success notice or confirmation reduces user friction and aligns with action intent.