Individual skill

spk-charter-glossary

Curate and apply Spec Kitty glossary terminology, aliases, conflicts, semantic drift checks, and domain-model pressure-tests across missions. Triggers: "update the glossary", "use canonical terms", "check terminology", "add a term", "fix term drift", "glossary conflicts", "resolve ambiguity", "review terminology consistency", "shape a domain model's terms", "validate domain language against code". Does NOT handle: runtime loop advancement, setup or repair requests, agent configuration, or direct code implementation tasks.

src/charter/offering/skills/spk-charter-glossary/SKILL.md

Read pinned source

Source commit 25b7cd4fbc8f42ec71219408e2b5d76e7dae38b4

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,717
Repository last updated
Nov 7, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# spk-charter-glossary

Maintain semantic integrity by curating the project glossary, detecting term
drift, and ensuring that all mission artifacts use canonical terminology.

Use this skill when the user asks about canonical terms, glossary updates,
terminology drift, or domain language consistency. Do not use it for purely
operational tasks like advancing the runtime loop or repairing an
installation.

## Flow

1. Locate active glossary context.
2. Check conflicts and strictness before changing anything.