yuen SKILL.md skillA
yuen from i2y/ritsu is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add i2y/ritsu/yuen@git:20261105.54d3620Pins git:20261105.54d3620 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- i2y/ritsu
- Path
skills/yuen/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261105.54d3620, committed Nov 5, 2026
- First version recorded
- Oct 4, 2026
- Size
- 12,429 bytes
- Repository stars
- 3
- License
- Apache-2.0
Write and check yuen files (`.req`), which say where each requirement comes from — an article of a law (e-Gov or the eCFR), a requirement of an OpenSpec spec, a file, or a person's decision — who owns it, what meets it (a rulec rule, a koyomi date, a chobo account or transfer, a dandori workflow, a `.proto`, a file of code) and what checks it (a geas or koyomi claim, a tool's own check), with each link recorded under the hashes of its two ends when a person looked. Use when a requirement and…
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
## When this applies The job is **where a requirement comes from, and whether what meets it is still what a person looked at**. A requirement read from an article of a law, or decided by someone, is met by a rule's table, a calendar's date, an account of a book or a file of code, and checked by a claim. yuen writes those links in a `.req`, records under each the hashes of both ends when a person looked, and stops the check when either end moves: an article amended, a rule rewritten, a line of code changed. It does not apply to what the rule, the date or the code says: that is rulec, koyomi, chobo, dandori or the code itself. yuen never reads what a requirement means. A project that keeps its behavior in **OpenSpec** (`openspec/specs/<capability>/spec.md`, changes under `openspec/changes/`) reads each OpenSpec requirement as a source: `source greeting = openspec "openspec/specs/greeting/spec.md"`, a pin line per requirement, and `from @greeting "Greeting by name"` in the requirement that reads it. OpenSpec is where people agree on what to change; yuen is where the links from those requirements to the rules, workflows, code and claims are recorded and …
Read the whole file at its exact version.
How to install
mdr add i2y/ritsu/yuen@sha256:43d988496abe4f1dThe line at the top of this page pins the label git:20261105.54d3620, 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_xfsi2imjgcduiean)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Oct 4, 2026 and Nov 5, 2026, about one every 8 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261105.54d3620 latest | 2026-11-05 | 54d3620 | 12,429 B | A | view · diff |
| git:20261006.922bf71 | 2026-10-06 | 922bf71 | 12,286 B | A | view · diff |
| git:20261005.cc21e44 | 2026-10-05 | cc21e44 | 11,966 B | A | view · diff |
| git:20261004.634440d | 2026-10-04 | 634440d | 10,411 B | A | view · diff |
| git:20261004.d3273b2 | 2026-10-04 | d3273b2 | 9,900 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 (12429 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
i2y/ritsu · 3 stars · license Apache-2.0 · pushed 2026-11-07 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_xfsi2imjgcduiean GET https://markdownregistry.com/api/v1/resolve?ref=i2y/ritsu/yuen GET https://markdownregistry.com/api/v1/blob/43d988496abe4f1deacd12f26a5157dba828910e50fdc8eb6fa0be1d73b69779
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.