agentsclimarketplace

Glossary definition generator

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

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.From its SKILL.md

Install
npx -y skills add WesleySmits/agent-skills --skill glossary-definition-generator

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 6 stars6 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

8.3 KB, ~1.8k tokens by cl100k_base, as published. Nobody here has run it

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:

SourceMethod
Product documentationExtract technical terms
Customer support ticketsFind confusing jargon
Competitor glossariesIdentify industry standards
Search queriesCheck what users search
Internal teamCollect tribal knowledge

Create a term inventory:

## 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:

## [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:

TypeFormulaExample
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:

## What is [Term]?

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

Keyword Integration

ElementOptimization
H1/H2"What is [Term]?" or "[Term] Definition"
First sentenceInclude 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

{
  "@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:

## 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:

## 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

# [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

# 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

# [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

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

Output Format

# 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

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 326,758. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.