When the user wants to create, optimize, or audit glossary page content and structure. Also use when the user mentions "glossary," "definitions," "terminology," "industry terms," "glossary page," "term definitions," "vocabulary," "glossary SEO," or "definition page." For definitions at scale, use programmatic-seo.
Guides glossary page structure, content, and internal linking for SEO.
When invoking: On first use, if helpful, open with 1-2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for industry terms and customer language.
Identify:
| Element | Purpose | |---------|---------| | Alphabetical index | A-Z or by category | | Term + definition | Clear, concise explanation | | Related terms | Cross-links within glossary | | Internal links | Link to relevant blog/content | | Search | Help users find terms |
Copy a source-pinned command for your client. You run it yourself.
Destination: .claude/skills/glossary · pinned to the source commit
git clone https://github.com/kostja94/marketing-skills.git
cd marketing-skills
git checkout 70987bad4ebe9dce1f74858c1c64f3f8810f18e4
mkdir -p ".claude/skills/glossary"
cp -r "skills/pages/content/glossary" ".claude/skills/glossary"Review the source before running. This copies files into your project; it is not a one-click install and does not verify runtime safety.
Scanner static-checks@0.1.0 · commit 70987bad4ebe. Static checks cannot prove runtime safety – review the source and the exact diff before installing. How checks work.
No static rules matched. This is not a safety guarantee.