glossary SKILL.md skillA

glossary from xobotyi/cc-foundry is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add xobotyi/cc-foundry/glossary@git:20260602.b17a8a2

Pins git:20260602.b17a8a2 in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
xobotyi/cc-foundry
Path
plugins/the-blueprint/skills/glossary/SKILL.md
Versions recorded
5
Latest version
git:20260602.b17a8a2, committed Jun 2, 2026
First version recorded
May 11, 2026
Size
14,843 bytes
Repository stars
23
License
MIT

Project glossary for consistent domain terminology. Invoke whenever task involves creating, updating, or referencing a glossary, defining domain terms, establishing ubiquitous language, or when inconsistent naming causes confusion in code or planning artifacts.

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

# Glossary

A glossary prevents naming drift on the small set of terms where drift is likely. It is **not** a project dictionary —
not every domain concept belongs. The highest-leverage element of each entry is the **rationale on the `Avoid` line**:
what plausible-but-wrong name would a reviewer or agent reach for, and why is it a trap? Without that rationale, the
entry teaches nothing.

LLMs are amplifiers — give them a clear vocabulary and they generate coherent structure; give them a codebase where the
same concept has four names, and they'll invent a fifth. The glossary makes the choice for them.

A glossary's real failure mode is disuse. If it isn't the document a reviewer reaches for during naming disagreements,
no amount of format polish saves it. Every rule below — the trap test, rationale-bearing `Avoid` lines, the CLAUDE.md
pointer — exists to make the glossary worth opening.

## Scope

Decide how many glossaries the project needs:

- **Single glossary** — one domain, one team, no terms with double meanings across the codebase.
- **Per-bounded-context** — the same word means different things in different parts of the system (e.g., `Order` in
…

Read the whole file at its exact version.

How to install

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_7f2sgd6fxm7smq3u/83db7fa4a2130dc6cb233c919379f0ac793c03c26a8bf47dd11670c4a68bff4f.json

Then /plugin install glossary@markdownregistry-7f2sgd6fxm7smq3u in Claude Code. It installs git:20260602.b17a8a2, the one graded A here, pinned to the commit it was graded at, and leaves it there.

The exact contents, by fingerprint
mdr add xobotyi/cc-foundry/glossary@sha256:83db7fa4a2130dc6

The line at the top of this page pins the label git:20260602.b17a8a2, 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.

Badge

mdr badge

[![mdr](https://markdownregistry.com/badge/art_7f2sgd6fxm7smq3u.svg)](https://markdownregistry.com/a/art_7f2sgd6fxm7smq3u)

2 badge image fetches in 30 days. What the badge shows.

Ask from your agent
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry

Then ask it: what changed in xobotyi/cc-foundry/glossary since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.

Got a copy of glossary from somewhere else? Ask it: where did my glossary come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.

Versions

The registry has recorded 5 versions of this file, between May 11, 2026 and Jun 2, 2026, about one every 6 days.

Watch this file (sign in, one email per new version)

versioncommittedcommitsizeaudit
git:20260602.b17a8a2 latest2026-06-02 b17a8a2 14,843 BA view · diff
git:20260515.f0f7caf2026-05-15 f0f7caf 13,838 BA view · diff
git:20260514.f4c27cf2026-05-14 f4c27cf 13,534 BA view · diff
git:20260511.513500e2026-05-11 513500e 6,091 BA view · diff
git:20260511.ebc65042026-05-11 ebc6504 5,607 BA view
Keep it current by itself, install once

Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

Install on GitHub

It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.

Keep it current by itself

Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml

It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.

Check a whole project

From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies

In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies

No sha256sum on your machine? shasum -a 256 prints the same lines.

Audit of the latest version

A  17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
  • pass: Frontmatter block present
  • pass: Frontmatter declares a name
  • pass: Frontmatter declares a description
  • pass: Size between 200 bytes and 200 KB (14843 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

GitHub

xobotyi/cc-foundry · 23 stars · license MIT · pushed 2026-11-13 · branch master

API

GET https://markdownregistry.com/api/v1/artifacts/art_7f2sgd6fxm7smq3u
GET https://markdownregistry.com/api/v1/resolve?ref=xobotyi/cc-foundry/glossary
GET https://markdownregistry.com/api/v1/blob/83db7fa4a2130dc6cb233c919379f0ac793c03c26a8bf47dd11670c4a68bff4f

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.

More from xobotyi/cc-foundry

release SKILL.md skill
xobotyi/cc-foundry · .claude/skills/release/SKILL.md · GitHub release creation for cc-foundry plugins: per-plugin tags, release notes as the changelog, post-merge publishing…
git:20261107.2754602 · audit A · 23 stars
CLAUDE.md CLAUDE.md file
xobotyi/cc-foundry · CLAUDE.md
git:20261111.edc23d5 · audit A · 23 stars
CLAUDE.md@plugins/ai-helpers CLAUDE.md file
xobotyi/cc-foundry · plugins/ai-helpers/CLAUDE.md
git:20261026.441701b · audit A · 23 stars
output-style-engineering SKILL.md skill
xobotyi/cc-foundry · plugins/ai-helpers/skills/output-style-engineering/SKILL.md · Design and maintain Claude Code output styles: choosing the mechanism, setting the frontmatter, and writing the role…
git:20260829.245c665 · audit A · 23 stars
prompt-engineering SKILL.md skill
xobotyi/cc-foundry · plugins/ai-helpers/skills/prompt-engineering/SKILL.md · Write and debug instruction text on any surface: requests, standing context such as CLAUDE.md, tool and schema…
git:20260828.1bf32f2 · audit A · 23 stars
prompt-terser SKILL.md skill
xobotyi/cc-foundry · plugins/ai-helpers/skills/prompt-terser/SKILL.md · Run a phased terseness pass over an existing prompt or skill and return a diff-proposal: mechanical wording and format…
git:20260828.1bf32f2 · audit A · 23 stars
skill-engineering SKILL.md skill
xobotyi/cc-foundry · plugins/ai-helpers/skills/skill-engineering/SKILL.md · Author and maintain Agent Skills: routing metadata, body content, bundled references and scripts, evaluation, and…
git:20260828.4127f54 · audit A · 23 stars
subagent-engineering SKILL.md skill
xobotyi/cc-foundry · plugins/ai-helpers/skills/subagent-engineering/SKILL.md · Design and maintain Claude Code subagents: the delegation decision, the frontmatter that governs a run, and the system…
git:20261029.ffe0c27 · audit A · 23 stars
CLAUDE.md@plugins/backend CLAUDE.md file
xobotyi/cc-foundry · plugins/backend/CLAUDE.md
git:20260830.16ec660 · audit A · 23 stars
observability SKILL.md skill
xobotyi/cc-foundry · plugins/backend/skills/observability/SKILL.md · Observability discipline: structured logging, metrics instrumentation, distributed tracing, and signal correlation…
git:20261107.2754602 · audit A · 23 stars
otel-tracing SKILL.md skill
xobotyi/cc-foundry · plugins/backend/skills/otel-tracing/SKILL.md · OpenTelemetry tracing discipline: correct spans, propagation, and semantic conventions produce useful traces. Invoke…
git:20261107.2754602 · audit A · 23 stars
prometheus SKILL.md skill
xobotyi/cc-foundry · plugins/backend/skills/prometheus/SKILL.md · Prometheus instrumentation discipline: right metric type, right name, right labels. Invoke whenever task involves any…
git:20260517.e6c4538 · audit A · 23 stars

Every file in xobotyi/cc-foundry

Other files named glossary

glossary SKILL.md skill
intent-driven-dev/intent-driven-template · .agents/skills/glossary/SKILL.md · Use when authoring or reviewing specs, requirements, design docs, ADRs, tasks, glossary entries, domain terms…
git:20260704.35d2195 · audit A · 201 stars
glossary SKILL.md skill
tdimino/claude-code-minoan · skills/core-development/glossary/SKILL.md · Build or update a CONTEXT.md domain glossary for the current project. Establishes shared vocabulary with term…
git:20260501.8349812 · audit A · 41 stars
glossary SKILL.md skill
ddd-ts-kit/ddd-ts-kit · plugin/skills/glossary/SKILL.md · Use when a business term is missing, ambiguous or has two meanings, when the generator or language/glossary-term…
git:20261029.b929ced · audit A · 24 stars
glossary SKILL.md skill
gbourgeat/ddd-ts-kit · plugin/skills/glossary/SKILL.md · Use when a business term is missing, ambiguous or has two meanings, when the generator or language/glossary-term…
git:20261029.b929ced · audit A · 22 stars
glossary SKILL.md skill
frank-masciopinto/ironheights · bench/corpus/benign/glossary/SKILL.md · Keep a glossary of project terms in glossary.md.
git:20261009.95e95d1 · audit B · 4 stars

Browse by kind, by grade A, or by owner.