clarify

Rewrite unclear interface copy and error messages for web and mobile interfaces.

5|Updated Apr 18, 2026
One-click install
npx skills add https://github.com/russosalv/NONoise --skill clarify-russosalv
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clarify
Source: https://github.com/russosalv/NONoise/tree/main/packages/skills/vendor/impeccable/clarify
Command: npx skills add https://github.com/russosalv/NONoise --skill clarify-russosalv

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Unclear or poorly written interface text — error messages, labels, CTAs, help text, and instructions — causes user confusion, mistakes, and support load; this Skill identifies those problems and produces clearer, more actionable copy tailored to the user context.

Core Features & Use Cases

  • Assess clarity: Detect jargon, ambiguity, passive voice, missing context, tone mismatches, and length problems in existing microcopy.
  • Context-aware rewriting: Recommend replacements that respect audience technical level, user mental state, action intent, and constraints such as character limits or localization.
  • Area coverage: Improve error messages, form labels, CTAs, help text/tooltips, empty/loading/success states, and confirmation dialogs.
  • Use case: During a design review, feed form labels and error flows to the Skill to get concise replacements, suggested tones, and actionable next steps that reduce user errors and support tickets.

Quick Start

Clarify this error message "Error 403: Forbidden" into a friendly, actionable message that explains why access is denied and how the user can request or obtain access.

Frequently Asked Questions about clarify

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

FAQPage Schema
How do I rewrite error messages to make them clear and actionable for users?

Rewriting error messages requires analyzing the audience's technical level and mental state, then replacing jargon with concise text that explains the issue and provides actionable next steps to resolve the access denial or input failure.

What is the best way to improve unclear microcopy and form labels during a design review?

Improving microcopy during a design review involves detecting passive voice, length issues, and tone mismatches in form labels, then proposing context-aware replacements that respect character limits and intended user actions.

How does context-aware UX writing handle localization and character limits for help text?

Context-aware UX writing handles localization by evaluating existing design principles and constraints, ensuring help text and tooltips remain concise and translatable while maintaining clarity for the target audience's technical proficiency.

Can I use this approach to refine CTAs and empty states for both web and mobile interfaces?

Yes, you can refine CTAs, empty states, loading screens, and confirmation dialogs across web and mobile interfaces by evaluating user mental states and applying tailored, actionable copy replacements.

Why do my interface instructions and tooltips cause user confusion and increased support tickets?

Interface instructions cause user confusion and support load when they contain ambiguity, missing context, or tone mismatches, failing to guide users effectively through the intended actions or error resolution steps.