glossary

Maintain project-specific definitions and command-phrases in GLOSSARY.md.

148|30|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/aspi6246/Claude-Code-Skills-for-Academics --skill glossary-aspi6246
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: glossary
Source: https://github.com/aspi6246/Claude-Code-Skills-for-Academics/tree/main/glossary
Command: npx skills add https://github.com/aspi6246/Claude-Code-Skills-for-Academics --skill glossary-aspi6246

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents confusion and inconsistency by keeping project-specific meanings and action-phrases in one place, so the assistant can interpret terms correctly and follow the user’s intended workflows.

Core Features & Use Cases

  • Per-project glossary in GLOSSARY.md: store definitions, abbreviations, and command-phrases tied to the current project root.
  • On-demand term lookup: answer “what does X mean here”, “what does X stand for”, and “what’s in our glossary” by reading the glossary file rather than guessing.
  • Eager command-phrase activation: keep behavioral phrases available from session start (loaded adaptively by /spin-up), and map them to the correct actions with safety preflights for sensitive operations.
  • Manageable growth discipline: supports adding, showing, updating, removing entries while keeping the glossary small and high-signal.

Quick Start

Ask the assistant: “From now on, ‘WellDatabase’ means the licensed well-level production dataset for this project.”

Frequently Asked Questions about glossary

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I maintain a project glossary for academic research workflows?

A project glossary stores definitions, abbreviations, and command-phrases in a GLOSSARY.md file at the project root to resolve ambiguity. This ensures the assistant interprets project-specific terms and acronyms consistently across research sessions.

How do command-phrases work to trigger actions in a research project?

Command-phrases are behavioral phrases loaded eagerly from session start and mapped to specific actions. The system performs safety preflights before executing sensitive operations like pushing to public repositories, ensuring controlled workflow triggers.

What's the best way to resolve acronym ambiguity during research collaboration?

Resolving acronym ambiguity involves storing variable names, dataset names, and definitions in a centralized per-project dictionary. The assistant reads this glossary file on demand to provide accurate lookups rather than guessing the meaning.

Does the glossary system support adding and updating project-specific definitions?

Yes, the glossary system supports adding, showing, updating, and removing entries while keeping the glossary small and high-signal. This manageable growth discipline ensures the project dictionary remains useful as research workflows evolve.

Why does the assistant need YAML frontmatter for glossary definitions?

YAML frontmatter provides the required name and description fields that identify the glossary skill within the project. This metadata enables the system to load command-phrases adaptively at session start and perform lazy definition lookups when queried.