ux-writing skillA
ux-writing is agent-read markdown (skill) from nahid-sparktales/agent-dispatcher: Write or repair the words inside an interface — button labels, empty states, error messages, confirmation dialogs, form hints, success and loading text — so a reader knows what just happened and what to do next. Use when a screen's copy is being written or reviewed, when an error says something unhelpful, when a confirmation is vague about what it will do, or when users hesitate at a control. Not for marketing or landing-page copy, not for documentation, and not for deciding layout or visual des.
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# UX writing Interface copy is read mid-task by someone who did not come to read. Every word is either doing work — naming an outcome, removing a doubt, offering the next move — or it is in the way. ## When this fires A screen's strings are being written, reviewed or translated; an error, empty state or confirmation is unclear; a control's label does not match what it does. It does not fire for prose the user chose to read: docs, marketing pages, release notes. ## Procedure 1. **Collect the actual strings.** Grep the component, route or feature for every user-visible string, including the ones not on screen right now — error branches, empty results, disabled reasons, toast text. Copy you never saw is copy you never fixed. 2. **Name the reader and the moment.** What were they doing one action ago, what do they already know, and what do they need to decide next. Write to that person, not to a persona. 3. **Fix labels first.** A label names the outcome in the reader's words, not the mechanism in yours: "Save changes", not "Submit"; "Delete project", not "Confirm". Avoid Yes/No button …
Read the whole file at its exact version.
How to install
mdr add nahid-sparktales/agent-dispatcher/ux-writing@git:20260919.a0d4f55mdr add nahid-sparktales/agent-dispatcher/ux-writing@sha256:22e3a68d0e7dfad3Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_whkr7jlzpvlg6ggd)
1 badge views in 30 days
Versions
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (5265 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
nahid-sparktales/agent-dispatcher · 49 stars · license MIT · pushed 2026-09-23 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_whkr7jlzpvlg6ggd GET https://markdownregistry.com/api/v1/resolve?ref=nahid-sparktales/agent-dispatcher/ux-writing GET https://markdownregistry.com/api/v1/blob/22e3a68d0e7dfad34da7cb35e0b20f7f139881646b0da66b5a58b2c7dfe6c175
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
More from nahid-sparktales/agent-dispatcher
Every file in nahid-sparktales/agent-dispatcher