blueprint-glossary-apply SKILL.md skillA
blueprint-glossary-apply from receptron/mulmoterminal is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add receptron/mulmoterminal/blueprint-glossary-apply@git:20260930.8ef4742Pins git:20260930.8ef4742 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- receptron/mulmoterminal
- Path
blueprints/glossary/skills/apply/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260930.8ef4742, committed Sep 30, 2026
- First version recorded
- Sep 30, 2026
- Size
- 2,960 bytes
- Repository stars
- 261
- License
- MIT
When the person asked, put the glossary's spellings and jargon into the folder's chaff.yaml without losing what it had; then write the glossary up for them.
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
# Put it into chaff.yaml, and report
`.blueprint/glossary.json` is the glossary the person approved. The documents stay exactly as they are.
## chaff.yaml — only when `write` is 「このフォルダの chaff.yaml に入れる」
Add to the folder's `chaff.yaml` (create it if there is none, with the documents' `language`, and a `genre` from
`chaff genres`):
```yaml
prefer: # the spelling not to use: the one to use
サーバ: サーバー
ユーザ: ユーザー
jargon: # words only understood inside
- 横展開
rules:
preferred-term: normal
```
- One `prefer` line for every spelling of a term other than its `preferred`.
- `jargon` lists every term marked `jargon: true`.
- `preferred-term` is experimental: it runs only when named under `rules`.
- **Creating the file for documents of different kinds** (a policy and its guide), give each kind its genre: the
kind most documents are goes in `genre`, and each other document gets its own under `by_path`, so a guide is not
measured as a policy:
```yaml
genre: legal/statute
by_path:
- files: ["tebiki.md"]
genre: docs/manual
```
…Read the whole file at its exact version.
How to install
mdr add receptron/mulmoterminal/blueprint-glossary-apply@sha256:74d0952e152b00a4The line at the top of this page pins the label git:20260930.8ef4742, 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_6te66k6vepg6uudo)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, all committed on Sep 30, 2026.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260930.8ef4742 latest | 2026-09-30 | 8ef4742 | 2,960 B | A | view · diff |
| git:20260930.246e0bc | 2026-09-30 | 246e0bc | 2,488 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 (2960 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
receptron/mulmoterminal · 261 stars · license MIT · pushed 2026-11-05 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_6te66k6vepg6uudo GET https://markdownregistry.com/api/v1/resolve?ref=receptron/mulmoterminal/blueprint-glossary-apply GET https://markdownregistry.com/api/v1/blob/74d0952e152b00a4aef4aade85923f90a72506dd820de0f2b0e3d88c65d03c0e
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.