architect SKILL.md skillA
architect 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/architect@git:20261007.3aa314dPins git:20261007.3aa314d in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- uze-sh/uze
- Path
plugins/uze/skills/architect/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261007.3aa314d, committed Oct 7, 2026
- First version recorded
- Sep 29, 2026
- Size
- 6,642 bytes
- Repository stars
- 3
- License
- Apache-2.0
Writing and changing the Mermaid diagrams a project keeps under `workspace.artifacts` — choosing which diagram and which level a change belongs in, naming it so it reads where a reader expects, and proving it still draws with `uze agent artifacts check`, which needs no workspace. Use when adding or editing a `.mmd`/`.mermaid` file, when asked to diagram or document an architecture, when a diagram does not draw, or when setting up where a project keeps its architecture.
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
# UZE — a project's architecture, as files somebody wrote A project tells UZE where its architecture lives: ```yaml # agents.yaml workspace: artifacts: docs/architecture # or a list: [docs, design] ``` Every `.mmd` or `.mermaid` file under those directories is one **artifact**; anything else there is ignored, so diagrams can live beside other docs. The same places are where the workspace's spec surface finds decision records (ADRs), by their shape, so a decision a diagram depends on can sit beside it in `docs/adr/` without anything else declared. `uze agent artifacts check` draws each one the way the workspace would and fails on one that does not draw, with or without the workspace running; the workspace's architect surface, when it is used, draws them in terminal cells to read and walk. Nothing lists the files and nothing registers them: adding a file is the whole act of adding a diagram, and an index beside them would be the one document that is wrong the moment somebody adds the next one. That is also the boundary of what belongs here. These diagrams are what somebody **wrote down**. What a project *is* — where its lines are, which …
Read the whole file at its exact version.
How to install
mdr add uze-sh/uze/architect@sha256:652c451aa3a07a0dThe line at the top of this page pins the label git:20261007.3aa314d, 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_bk4fg2j5ikszbw2w)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Sep 29, 2026 and Oct 7, 2026, about one every 2 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261007.3aa314d latest | 2026-10-07 | 3aa314d | 6,642 B | A | view · diff |
| git:20261005.3bf25bc | 2026-10-05 | 3bf25bc | 6,694 B | A | view · diff |
| git:20261005.7965baf | 2026-10-05 | 7965baf | 6,492 B | A | view · diff |
| git:20260930.ae58e9f | 2026-09-30 | ae58e9f | 6,351 B | A | view · diff |
| git:20260929.10e5878 | 2026-09-29 | 10e5878 | 6,190 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 (6642 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_bk4fg2j5ikszbw2w GET https://markdownregistry.com/api/v1/resolve?ref=uze-sh/uze/architect GET https://markdownregistry.com/api/v1/blob/652c451aa3a07a0d0609f04a4ddeb3971ab64a0866672729b998cef402c1f7f3
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.