journey-author SKILL.md skillA
journey-author from uze-sh/uze is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add uze-sh/uze/journey-author@git:20261017.1d0b3a6Pins git:20261017.1d0b3a6 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- uze-sh/uze
- Path
.agents/skills/journey-author/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261017.1d0b3a6, committed Oct 17, 2026
- First version recorded
- Sep 6, 2026
- Size
- 7,634 bytes
- Repository stars
- 3
- License
- Apache-2.0
Writing, changing or debugging a product journey (journeys/) — use whenever you are adding a scenario for a user-facing flow, a journey fails or flakes, a selector stopped matching after a TUI change, you need to decide whether something is a new scene or a new file, or you are about to assert on UZE's own output instead of on the machine. Covers the chapter spine, the scene/file split rule, the gesture and check vocabularies, the probe loop, reading evidence/verdict.json, and the four world…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Writing a product journey A journey performs a user's flow — through the real CLI, the real TUI, or both — in a disposable world, then checks **the machine it left behind**. `tests/` proves the domain deterministically against fake harnesses; `conformance/` proves what a vendor harness does; a journey proves what UZE does, including the parts of `src/ui/` no Rust test can click. Read `journeys/README.md` for the full vocabulary. This is what to do, in what order, and what goes wrong. ## The two rules everything else serves **Never validate UZE with UZE.** Every `then` check reads the filesystem, Git, the recorded task state, or the process table. UZE's own report is the *subject* — a `cmd` step whose output you assert *against* those checks — never the source of truth for another check. This is the whole reason the tier exists: it is the only place that catches "exited zero, reported the artifact, wrote nothing". **Screen text is a gate, never an assertion.** `expect` proves a gesture landed, so the next one acts on the state you think it does. If you find yourself asserting on what the screen says, the claim belongs in …
Read the whole file at its exact version.
How to install
mdr add uze-sh/uze/journey-author@sha256:1305ad2227284006The line at the top of this page pins the label git:20261017.1d0b3a6, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_ielqz5uxmtteeg5w)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Sep 6, 2026 and Oct 17, 2026, about one every 13 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261017.1d0b3a6 latest | 2026-10-17 | 1d0b3a6 | 7,634 B | A | view · diff |
| git:20261015.5e95f3d | 2026-10-15 | 5e95f3d | 7,460 B | A | view · diff |
| git:20260910.6ceeaf2 | 2026-09-10 | 6ceeaf2 | 7,519 B | A | view · diff |
| git:20260906.29363f8 | 2026-09-06 | 29363f8 | 7,155 B | A | view |
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 (7634 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
uze-sh/uze · 3 stars · license Apache-2.0 · pushed 2026-10-20 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ielqz5uxmtteeg5w GET https://markdownregistry.com/api/v1/resolve?ref=uze-sh/uze/journey-author GET https://markdownregistry.com/api/v1/blob/1305ad222728400640440c0f751c2f39acaef56cbf9091b32315f916fe744193
Your AI assistant 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.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.