glossary — Claude Code skill: what it does, how to install
A per-project dictionary in GLOSSARY.md covering definitions, abbreviations and command phrases the agent carries out on a single word.
no license ★ 165 updated 2026-08-21
npx skills add aspi6246/Claude-Code-Skills-for-Academics --skill glossary -a claude-codeWhat glossary does
The skill keeps one project's vocabulary in GLOSSARY.md at the repo root. Three sections live there: definitions for variables and datasets, abbreviations, and command phrases that stand for an action. The skill file is global, the entries belong to the project.
/spin-up reads that file when a session starts, though not all of it. Command phrases come in full right away, because the bare word alone never triggers the skill. For definitions and abbreviations only the headwords are loaded, and the gloss gets looked up once the term actually appears in conversation or code. Under 25 entries the whole file is read. A term earns its place only if it stays useful next month, isn't obvious from its name, keeps coming up, and is specific to this project.
An alias is permission to act, not permission to skip safety. Pushing to a public repo still goes through a scan of staged files for keys and usernames in paths, while delete and force-push ask for a one-line confirmation first.
What it helps with
- capture a project term in
GLOSSARY.md - look up what an in-house acronym stands for
- turn a short phrase into a repeatable action
- list the glossary by section with entry counts
- drop an entry that no longer applies
Example prompts for the agent
- Add to the glossary:
retis the monthly stock return - What does
WRDSstand for in this project? - Show the glossary
How to install glossary
1Skills CLI (Vercel)
npx skills add aspi6246/Claude-Code-Skills-for-Academics --skill glossary -a claude-code2Manually: put the files in place
~/.claude/skills/glossary/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/glossary/
1Skills CLI (Vercel)
npx skills add aspi6246/Claude-Code-Skills-for-Academics --skill glossary -a codex2Manually: put the files in place
.agents/skills/glossary/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add aspi6246/Claude-Code-Skills-for-Academics --skill glossary -a cursor2Manually: put the files in place
.cursor/skills/glossary/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install aspi6246/Claude-Code-Skills-for-Academics glossary2Manually: put the files in place
.github/skills/glossary/SKILL.md1Skills CLI (Vercel)
npx skills add aspi6246/Claude-Code-Skills-for-Academics --skill glossary -a gemini-cli2Platform CLI
gemini skills install https://github.com/aspi6246/Claude-Code-Skills-for-Academics --path glossaryManually: put the files in place
.devin/skills/glossary/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about glossary
How do I install glossary in Claude Code?
Run npx skills add aspi6246/Claude-Code-Skills-for-Academics --skill glossary -a claude-code. The skill file lands at ~/.claude/skills/glossary/SKILL.md.
What does glossary do?
It maintains a project dictionary in GLOSSARY.md, answers questions from it, and runs the action behind a command phrase. It offers to record a term you mention in passing instead of writing it unasked.
Does the whole glossary load into context?
Command phrases do, in full, at session start via /spin-up. Definitions and abbreviations load on demand, when the term comes up. With fewer than 25 entries the file is read whole.