riscv-spec skillA
riscv-spec is agent-read markdown (skill) from openxiangshan/xiangshanlab: Look up RISC-V ISA specification details using the local riscv-unified-db (UDB) repository. Activate when answering questions about RISC-V extensions, instructions, encodings, assembly syntax, CSR fields, architectural parameters (hardware configuration knobs), profile requirements (RVA20/22/23, RVB23, etc.), or any ISA-level spec claim. Also use for verifying RISC-V spec claims before stating them - including claims in patches, commit messages, or upstream discussions about spec compliance. For.
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
# RISC-V Spec Lookup ## Rule Never state RISC-V spec claims without verifying against UDB or upstream spec sources. If UDB doesn't cover it, say so explicitly. ## Local Database Path: `~/repos/riscv-unified-db/` If the directory does not exist, **ask the user for confirmation before cloning** (~200MB). Do not clone silently. ### Keeping UDB Fresh After cloning or fetching, record the date in `<skill_dir>/.last-update` (same directory as this SKILL.md). On each activation, check the file. If older than 7 days (or missing), run: ```bash cd ~/repos/riscv-unified-db && git fetch origin && git merge --ff-only origin/main ``` Then update the timestamp. ## Lookup Procedure ### Extensions ``` spec/std/isa/ext/<Name>.yaml ``` Key fields: `name`, `long_name`, `description`, `versions[]` (state, ratification_date), `requirements` If unsure of exact name: `find spec/std/isa/ext/ -iname '*keyword*'` ### Instructions ``` spec/std/isa/inst/<Ext>/<name>.yaml ``` Key fields: `name`, `long_name`, `description`, `assembly` (syntax), `encoding.match` (bitmask), `encoding.variables[]` (operand bit locations), `access` (s/u/vs/vu permissions), `definedBy`, `operation()` …
Read the whole file at its exact version.
How to install
mdr add openxiangshan/xiangshanlab/riscv-spec@git:20260920.b781a6dmdr add openxiangshan/xiangshanlab/riscv-spec@sha256:20f903e194348b67Pin 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_sbpn4tjjx4woqjme)
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 (5461 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
openxiangshan/xiangshanlab · 41 stars · license none · pushed 2026-09-22 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_sbpn4tjjx4woqjme GET https://markdownregistry.com/api/v1/resolve?ref=openxiangshan/xiangshanlab/riscv-spec GET https://markdownregistry.com/api/v1/blob/20f903e194348b67f4b5c2a132e67378026b14965c4a53ec0a623793a1827c92
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.