ux-copy

Write or review UX copy — microcopy, error messages, empty states, CTAs. Trigger with "write copy for", "what should this button say?", "review this error message", or when naming a CTA, wording a confirmation dialog, filling an empty state, or writing onboarding text.

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

81%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-organized, actionable instruction-only skill with concrete copy examples, tone guidance, and a clear output contract. Its weaknesses are minor: a few vague pattern one-liners (Tooltips, Loading States) that lack examples, and an unresolved boilerplate reference outside the bundle.

Suggestions

Give Tooltips and Loading States the same treatment as the other patterns: a concrete structure plus one example line of copy (e.g. 'Tooltip: Add a card — Use this card as your default for future payments').

Trim or merge the Principles and Voice and Tone sections — much of that guidance (be clear, be human, match tone) is inferable, and the tone matrix already encodes the useful part.

Remove or verify the [CONNECTORS.md](../../CONNECTORS.md) reference — it points outside the skill bundle; if it is guaranteed boilerplate fine, otherwise it is a dangling pointer.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean, task-specific guidance, but the Principles list ('Clear', 'Concise', 'Consistent', 'Useful', 'Human') and vague one-liners like 'Tooltips: Concise, helpful, never obvious' and 'Loading States: Set expectations, reduce anxiety' are padding Claude could infer.	4 / 5
Actionability	Concrete example copy ('Payment declined. Your card was declined by your bank. Try a different card or contact your bank.'), structural formulas ('What happened + Why + How to fix'), and a fully specified output template make the guidance executable; however Tooltips and Loading States lack any example, leaving minor gaps.	4 / 5
Workflow Clarity	As a simple, single-purpose skill the flow is unambiguous: gather inputs ('What I Need From You'), apply the copy patterns, and produce the defined 'Output' template; no destructive or batch operations require validation checkpoints.	5 / 5
Progressive Disclosure	All content sits appropriately in one well-sectioned file with nothing that belongs in a separate reference; the only reference ([CONNECTORS.md](../../CONNECTORS.md)) is boilerplate pointing outside the bundle and cannot be verified, a minor organization gap.	4 / 5
	Total	17 / 20 Passed

Description

95%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: third-person, concise, with an explicit trigger clause and natural user phrases spanning the domain. The only weakness is that the action vocabulary is limited to 'write or review' rather than a broader set of distinct capabilities.

Dimension	Reasoning	Score
Specificity	The description names the domain and enumerates concrete deliverables ('microcopy, error messages, empty states, CTAs'), but the only action verbs are 'Write or review', leaving minor coverage gaps relative to the comprehensive anchor.	4 / 5
Completeness	It explicitly answers both what ('Write or review UX copy — microcopy, error messages, empty states, CTAs') and when ('Trigger with... or when naming a CTA...') with concrete trigger phrases, matching the top anchor's structure.	5 / 5
Trigger Term Quality	Natural quoted phrases ('write copy for', 'what should this button say?', 'review this error message') plus gerund triggers ('naming a CTA', 'wording a confirmation dialog', 'filling an empty state', 'writing onboarding text') comprehensively cover the domain with synonym-level variation.	5 / 5
Distinctiveness Conflict Risk	'UX copy / microcopy' is a clear niche with distinct, unlikely-to-collide triggers; conflict risk with adjacent writing skills is minimal.	5 / 5
	Total	19 / 20 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 1 suspicious	Warning

	Total	14 / 16 Passed

Repository: anthropics/knowledge-work-plugins
Path: design/skills/ux-copy/SKILL.md
Commit: 8444efc

Reviewed: 6 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.