glossary

Add terms and definitions to a centralized glossary with markdown links.

9|8|Updated Jun 28, 2024
One-click install
npx skills add https://github.com/MetaMask/ocap-kernel --skill glossary-metamask
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: glossary
Source: https://github.com/MetaMask/ocap-kernel/tree/main/.claude/skills/glossary
Command: npx skills add https://github.com/MetaMask/ocap-kernel --skill glossary-metamask

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams maintain a centralized glossary of terms, ensuring consistent definitions across docs and code.

Core Features & Use Cases

  • Governance of terminology: add, update, and link terms
  • Cross-referencing with related docs and code
  • Use Case: when introducing a new term, add an entry with links to related implementation files or documentation

Quick Start

Edit the SKILL.md frontmatter to include the new term name and its definition, and optionally add links to related files in the body.

Frequently Asked Questions about glossary

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

FAQPage Schema
How do I maintain consistent terminology across project documentation and code?

To maintain consistent terminology, add terms and definitions to a centralized glossary, linking entries to related files so contributors can cross-reference definitions across docs and code.

What is the best way to add a new term to a collaborative knowledge base?

The best way to add a new term to a collaborative knowledge base is to edit the SKILL.md file, including the term name and definition in the YAML frontmatter, and optionally add markdown links to related documentation.

How do I cross-reference related implementation files when introducing new project terms?

You cross-reference related implementation files by adding markdown links within the body of your glossary entry, connecting the new terminology directly to relevant code and documentation files.

Do I need YAML frontmatter to manage a project glossary?

Yes, you need YAML frontmatter within SKILL.md to define the term name and description, structuring your glossary entries and ensuring definitions are properly formatted for collaborative documentation workflows.

Can I link glossary terms to both docs and code files?

Yes, you can link glossary terms to both docs and code files using markdown links in the entry body, enabling cross-referencing across your entire project knowledge base.