Glossary Builder

What it does

Scans published posts to find domain-specific terms, jargon, and acronyms the site actually uses repeatedly, then drafts a short definition for each grounded in how the site itself uses the term, rather than pulling generic dictionary definitions. It links each glossary entry back to the posts where the term appears in context.

Install

This skill isn't packaged in an installable registry. It's a plain SKILL.md file you can copy directly. Copy it from the SKILL.md tab and save it at the path for your assistant:

Use it in your AI assistant

Claude Code

.claude/skills/glossary-builder/ (or ~/.claude/skills/glossary-builder/ for all projects)

GitHub Copilot (VS Code)

.github/skills/glossary-builder/

OpenAI Codex

.codex/skills/glossary-builder/

Cursor

.cursor/skills/glossary-builder/ (or ~/.cursor/skills/glossary-builder/ globally)

Compatibility

Any WordPress site with a body of published posts to scan. No special plugin required; works with a standard page for the glossary output.

The complete SKILL.md for this skill:

---
name: glossary-builder
description: Use when a user wants a glossary page built from terms the site actually uses, or asks to define jargon that shows up across posts. Triggers on "build a glossary page", "define the terms we use", or "make a jargon page for readers".
---

# Glossary Builder

## When to use
The site has accumulated domain-specific terms or acronyms across its posts, and readers would benefit from a single glossary page defining them in the site's own context.

## Procedure
1. Scan a representative set of published posts to extract terms and acronyms that recur across multiple posts, rather than appearing once in passing.
2. For each term, write a definition grounded in how the site actually uses it (check 2 to 3 usage examples across posts) rather than a generic dictionary definition that might not match the site's specific meaning.
3. Order terms alphabetically and group any that are closely related (a term and its acronym) into a single entry rather than two separate near-duplicate ones.
4. Link each glossary entry to one or two posts where the term is used in real context, so readers can see it applied.
5. Present the drafted glossary as a page for review, since some entries may need a subject-matter expert's confirmation before publishing.

## Guardrails
- Do not include a term used only once across the whole site; a glossary should cover recurring vocabulary, not every technical word that ever appeared.
- Do not invent a definition when the site's own usage is ambiguous or inconsistent across posts; flag the inconsistency for the user instead of picking one arbitrarily.