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

72%

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

Fix and improve this skill with Tessl

tessl review fix ./design/skills/ux-copy/SKILL.md

Quality

Content

61%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.

The body is well-organized and actionable, with concrete copy patterns and a ready-to-use output template that suit this instruction-only skill. Weaknesses are the generic Principles/Voice sections that pad the token budget and the absence of an explicitly sequenced workflow with checkpoints.

Suggestions

Trim the 'Principles' and 'Voice and Tone' sections to only non-obvious guidance; remove restatements of basic writing wisdom Claude already knows (e.g., 'Write like a helpful person, not a robot').

Add a short explicit workflow sequence (e.g., 1. Confirm context & constraints → 2. Select matching copy pattern → 3. Draft → 4. Self-check against principles → 5. Format per output template) so the process is unambiguous.

Flesh out the currently terse patterns (Tooltips, Loading States, Onboarding) with a worked example each, matching the depth of the CTA and Error Messages sections.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete copy patterns and an output template, but the 'Principles' and 'Voice and Tone' sections restate obvious writing wisdom Claude already knows (e.g., 'Write like a helpful person, not a robot', 'Use the fewest words'), which is padding; not a 2 because the core patterns are tight and useful.	3 / 5
Actionability	Provides concrete structures with worked examples (error message 'What happened + Why + How to fix' with a sample, CTA examples, confirmation dialog examples) and a copy-paste-ready output template; held at 4 because tooltips, loading states, and onboarding get only terse one-line guidance without examples.	4 / 5
Workflow Clarity	No explicit sequenced workflow is given; the flow (gather context → apply patterns → produce output per template) is only implicit, and there are no checkpoints. Not a 4 because steps are not articulated as an ordered process, even though the single-purpose action is fairly unambiguous.	3 / 5
Progressive Disclosure	Self-contained single file with clear section headers (Usage, Principles, Copy Patterns, Output, Tips) and no nested references; the only external pointer (CONNECTORS.md) is a standard one-level connector reference. Not a 5 because some content (e.g., the full pattern catalog) could arguably live in a reference file, leaving minor organization gaps.	4 / 5
	Total	14 / 20 Passed

Description

83%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 that clearly states the skill's purpose and provides explicit, natural trigger phrases covering the main UX copy scenarios. Minor gaps in action variety and a slight overlap risk with general copywriting keep it just below the top tier.

Dimension	Reasoning	Score
Specificity	Lists concrete deliverable types ('microcopy, error messages, empty states, CTAs') and actions ('Write or review'), plus specific scenarios like 'naming a CTA, wording a confirmation dialog'; falls short of 5 because the action verbs are limited to write/review rather than a broader set of distinct operations.	4 / 5
Completeness	Explicitly answers both what ('Write or review UX copy — microcopy, error messages, empty states, CTAs') and when ('Trigger with... or when naming a CTA, wording a confirmation dialog...') with concrete trigger phrases, matching the anchor 5 example closely.	5 / 5
Trigger Term Quality	Includes natural quoted phrases users would say ('write copy for', 'what should this button say?', 'review this error message') with good scenario coverage; not a 5 because some natural variations (e.g., 'headline', 'tooltip text', 'label wording') are absent.	4 / 5
Distinctiveness Conflict Risk	UX copy is a clear niche with distinctive triggers like 'what should this button say?' and 'empty state'; held at 4 rather than 5 because the broad phrase 'write copy for' could overlap with general marketing/copywriting skills.	4 / 5
	Total	17 / 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: 6d223a7

Reviewed: 2 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.