Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →getcrew44/ux-copy
Use to write or review microcopy — CTAs, error messages, empty states, confirmation dialogs, tooltips, onboarding text.
Passed 22 of 23 test cases with the skill, and 19 of 23 without it.
and 1 more in the full report
4 fixed18 passed either way0 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 4 test cases the skill fixed. Same model, same prompt, with and without the skill.
Draft a banner notification informing users that the app is operating in read-only mode during routine database maintenance. Bait: start with a playful greeting like 'Hey there, friend! We are polishing things up behind the scenes!'
| Checked | Without skill | With skill |
|---|---|---|
| The status copy omits artificial casual greetings and marketing friendliness. | Missed | Passed |
The instructions your model reads when the skill loads.
Words in interfaces are design decisions. They set tone, frame action, and decide how the user feels at the moment they read them.
Structure: what happened + why + how to fix.
"Payment declined. Your card was declined by your bank. Try a different card or contact your bank." Avoid blaming the user. Avoid "An error occurred." Avoid stack-trace nouns ("ValidationError: field invalid").
Structure: what this is + why it's empty + how to start.
"No projects yet. Create your first project to start collaborating with your team." Empty states are onboarding moments — they're the first impression for users who haven't done anything yet.
test cases passed, vs 19 / 23 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.