Skip to content

WesleySmits/agent-skills / .agent/skills/glossary-definition-generator

generating-glossaries-and-definitions

Verified

Builds product and industry glossaries with SEO-optimized definitions. Use when the user asks about glossary creation, term definitions, jargon explanations, knowledge bases, or terminology documentation.

FileKindSize
SKILL.mdskill md8.3 KB
---
name: generating-glossaries-and-definitions
description: Builds product and industry glossaries with SEO-optimized definitions. Use when the user asks about glossary creation, term definitions, jargon explanations, knowledge bases, or terminology documentation.
---

# Glossary & Definition Generator

## When to use this skill

- User asks to create a glossary
- User needs term definitions
- User wants to explain jargon
- User mentions terminology documentation
- User needs a knowledge base of terms

## Workflow

- [ ] Identify terms to define
- [ ] Research accurate definitions
- [ ] Write SEO-optimized entries
- [ ] Link related terms
- [ ] Format for target output
- [ ] Validate completeness

## Instructions

### Step 1: Term Collection

Gather terms from these sources:

| Source                   | Method                      |
| ------------------------ | --------------------------- |
| Product documentation    | Extract technical terms     |
| Customer support tickets | Find confusing jargon       |
| Competitor glossaries    | Identify industry standards |
| Search queries           | Check what users search     |
| Internal team            | Collect tribal knowledge    |

Create a term inventory:

```markdown
## Term Inventory

| Term   | Category   | Priority     | Status   |
| ------ | ---------- | ------------ | -------- |
| [Term] | [Category] | High/Med/Low | To write |
| [Term] | [Category] | High/Med/Low | Draft    |
```

**Prioritization criteria:**

- High: Core product/industry terms users must understand
- Medium: Common terms that appear frequently
- Low: Advanced/niche terms for power users

### Step 2: Definition Structure

Each glossary entry should include:

```markdown
## [Term]

**Definition:** [Clear, concise explanation in 1-2 sentences]

**Example:** [Real-world usage or context]

**Related terms:** [Link to connected entries]

**Also known as:** [Synonyms or abbreviations]
```

### Step 3: Writing Definitions

**Definition formulas:**

| Type       | Formula                                                   | Example                                                                                   |
| ---------- | --------------------------------------------------------- | ----------------------------------------------------------------------------------------- |
| Simple     | "[Term] is [category] that [function]."                   | "An API is a set of protocols that allows software applications to communicate."          |
| Technical  | "[Term] refers to [technical description]. It [purpose]." | "Latency refers to the delay between a request and response. It affects user experience." |
| Comparison | "[Term] is similar to [known concept], but [difference]." | "A CMS is similar to a word processor, but designed for web content."                     |

**Writing guidelines:**

- Lead with the simplest explanation
- Avoid circular definitions (don't use the term to define itself)
- Include the "why it matters" context
- Target 50-150 words per definition
- Write for the least technical reader

### Step 4: SEO Optimization

#### Featured Snippet Targeting

Structure definitions for position zero:

```markdown
## What is [Term]?

[Term] is [40-60 word definition that directly answers the question].
```

#### Keyword Integration

| Element          | Optimization                                                                                             |
| ---------------- | -------------------------------------------------------------------------------------------------------- |
| H1/H2            | "What is [Term]?" or "[Term] Definition"                                                                 |
| First sentence   | Include term within first 10 words                                                                       |
| Meta title       | "[Term]: Definition, Examples & Guide"                                                                   |
| Meta description | "Learn what [term] means, why it matters, and see examples. Simple explanation of [term] for beginners." |
| URL              | `/glossary/[term-slug]`                                                                                  |

#### Schema Markup

```json
{
  "@context": "https://schema.org",
  "@type": "DefinedTerm",
  "name": "[Term]",
  "description": "[Definition]",
  "inDefinedTermSet": {
    "@type": "DefinedTermSet",
    "name": "[Company] Glossary"
  }
}
```

### Step 5: Related Term Linking

Create a relationship map:

```markdown
## Term Relationships

### [Term A]

- **Parent:** [Broader concept]
- **Children:** [More specific terms]
- **Siblings:** [Related same-level terms]
- **See also:** [Loosely related terms]
```

**Linking rules:**

- Link on first mention of related term
- 3-5 related terms per entry
- Ensure bidirectional links
- Group related terms in categories

### Step 6: Category Organization

Structure glossary by topic:

```markdown
## Glossary Categories

### Getting Started

- [Basic term 1]
- [Basic term 2]

### [Product Feature]

- [Feature term 1]
- [Feature term 2]

### Technical

- [Technical term 1]
- [Technical term 2]

### Industry

- [Industry term 1]
- [Industry term 2]
```

### Step 7: Output Formats

#### Website Glossary Page

```markdown
# [Industry/Product] Glossary

A comprehensive guide to [industry] terminology.

## A

### [Term starting with A]

[Definition]
**Related:** [Links]

## B

### [Term starting with B]

[Definition]
**Related:** [Links]

[Continue A-Z structure]
```

#### Individual Term Pages

```markdown
# What is [Term]?

[Definition paragraph - 50-100 words]

## How [Term] Works

[Explanation with examples - 100-200 words]

## Why [Term] Matters

[Business/practical context - 50-100 words]

## [Term] Examples

- **Example 1:** [Description]
- **Example 2:** [Description]

## Related Terms

- [[Related Term 1]](/glossary/related-term-1)
- [[Related Term 2]](/glossary/related-term-2)

## FAQ

**Q: [Common question about term]?**
A: [Answer]
```

#### Downloadable Resource

```markdown
# [Industry] Terminology Guide

## Introduction

[Brief overview of why this glossary exists]

## Quick Reference

| Term     | Definition         |
| -------- | ------------------ |
| [Term 1] | [Brief definition] |
| [Term 2] | [Brief definition] |

## Full Definitions

### [Term 1]

[Complete definition with examples]

### [Term 2]

[Complete definition with examples]

## Index

[Alphabetical list with page numbers]
```

#### Widget/Tooltip Format

```json
{
  "terms": [
    {
      "term": "[Term]",
      "definition": "[Short definition - max 100 chars]",
      "url": "/glossary/[term-slug]"
    }
  ]
}
```

## Output Format

```markdown
# Glossary: [Industry/Product]

## Overview

**Total terms:** [#]
**Categories:** [List]
**Target audience:** [Audience]

---

## Terms

### [Term 1]

**Definition:** [Clear explanation]

**Example:** [Usage example]

**Related terms:** [Term 2], [Term 3]

**Also known as:** [Synonyms]

---

### [Term 2]

**Definition:** [Clear explanation]

**Example:** [Usage example]

**Related terms:** [Term 1], [Term 4]

---

## Category Index

### [Category 1]

- [Term]
- [Term]

### [Category 2]

- [Term]
- [Term]

---

## SEO Metadata

| Term     | Meta Title | Meta Description |
| -------- | ---------- | ---------------- |
| [Term 1] | [Title]    | [Description]    |
| [Term 2] | [Title]    | [Description]    |
```

## Validation

Before completing:

- [ ] All priority terms defined
- [ ] Definitions are clear and accurate
- [ ] No circular definitions
- [ ] Related terms linked bidirectionally
- [ ] Categories logically organized
- [ ] SEO elements included
- [ ] Consistent formatting throughout
- [ ] Spelling and grammar checked

## Error Handling

- **Term already exists**: Check for duplicates; merge or differentiate entries.
- **Definition too technical**: Simplify language; add "in other words" explanation.
- **No related terms**: Review category; every term should connect to at least one other.
- **Conflicting definitions**: Research authoritative sources; note if term has multiple meanings.

## Resources

- [Schema.org DefinedTerm](https://schema.org/DefinedTerm) - Structured data reference
- [Google Search Central](https://developers.google.com/search/docs/appearance/structured-data) - SEO guidance
- [Merriam-Webster](https://www.merriam-webster.com/) - Definition style reference
- [Hemingway Editor](https://hemingwayapp.com/) - Readability checking
rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file).Stars: 198kUpdated Claude CodeCodexUnverifiedInstall
doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.Stars: 198kUpdated Claude CodeCodexVerifiedInstall