Glossary Alignment Check
For each technical term in a substacker draft's claims, checks shared-context/glossary.md for a writer-specific definition and compares to field-standard. Emits a note for terms where the two diverge (aligned / diverged-safe / diverged-risky). Feeds into classify-claim (which definition governs) and write-review-artifact's Glossary Alignment section. Use on every claim. Trigger keywords — glossary alignment, term definition, writer vs field, load-bearing term.
Install
/plugin marketplace add lyndonkl/claudeThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add lyndonkl/claude --skill glossary-alignment-checkgit clone --depth 1 https://github.com/lyndonkl/claude.git /tmp/claude
mkdir -p ~/.claude/skills
cp -r /tmp/claude/skills/glossary-alignment-check ~/.claude/skills/glossary-alignment-checkPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Glossary Alignment Check ## Workflow ``` Per claim: - [ ] Step 1: Tokenize claim for candidate terms (named concepts, TLAs, math) - [ ] Step 2: Grep shared-context/glossary.md for each term - [ ] Step 3: If found, pull writer's definition - [ ] Step 4: Compare to field-standard (prior knowledge + optional WebSearch) - [ ] Step 5: Emit: aligned | diverged-safe | diverged-risky ``` ## Three outcomes - **aligned**: writer's definition matches field-standard. No note. - **diverged-safe**: definitions differ but the post's argument doesn't depend on the difference. Note but don't block. - **diverged-risky**: definitions differ AND the post's argument hinges on which definition is in force. Tier-2 note for the writer. ## Worked example **Term**: "attention" **Writer's glossary**: "the mechanism that lets tokens exchange information, including the residual bypass." **Field-standard**: "the weighted sum `softmax(QK^T/√d)V`, excluding the residual." **Status**: `diverged-risky` if post asserts "attention is O(n²)" — true under field definition, false-or-unclear under the writer's. **Output note**: "Writer's glossary includes residual in 'attention'; field-standard excludes. Post's claim 'attention is O(n²) in memory' is true under field but misleading under writer's glossary. Consider disambiguating in-post or tightening the glossary." ## Guardrails 1. Never rewrite the glossary. Only flag. 2. Never mark `aligned` without actually checking the glossary file this run.
Details
- Skill name
glossary-alignment-check- Repository
- lyndonkl/claude
- Path
skills/glossary-alignment-check/SKILL.md- Repo updated
- 1 September 2026
FAQ
What does the Glossary Alignment Check skill do?
For each technical term in a substacker draft's claims, checks shared-context/glossary.md for a writer-specific definition and compares to field-standard. Emits a note for terms where the two diverge (aligned / diverged-safe / diverged-risky). Feeds into classify-claim (which definition governs) and write-review-artifact's Glossary Alignment section. Use on every claim. Trigger keywords — glossary alignment, term definition, writer vs field, load-bearing term.
How do I install the Glossary Alignment Check skill?
Claude Code plugin: /plugin marketplace add lyndonkl/claude. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Glossary Alignment Check popular?
It lives in lyndonkl/claude, which has 200 GitHub stars and 25 forks.
Related skills
Abstraction Concrete Examples
200lyndonkl/claude
Builds structured abstraction ladders that translate high-level principles into concrete, actionable examples across 3-5 levels. Bridges communication gaps, reveals hidden assumptions, and tests whether abstract ideas work in practice. Use when explaining concepts at different expertise levels, moving between abstract principles and concrete implementation, identifying edge cases by testing ideas against scenarios, designing layered documentation, decomposing complex problems into actionable steps, or bridging strategy-execution gaps.
Academic Letter Architect
200lyndonkl/claude
Guides the creation of evidence-based academic recommendation letters, reference letters, and award nominations that combine concrete examples, meaningful comparisons, and genuine enthusiasm. Use when writing recommendation letters for students, postdocs, or colleagues, or when user mentions recommendation letter, reference, nomination, letter of support, endorsement, or needs help with strong advocacy and comparative statements.
Adr Architecture
200lyndonkl/claude
Documents significant architectural and technical decisions with full context, alternatives considered, trade-offs analyzed, and consequences understood. Creates a decision trail that helps teams understand why decisions were made. Use when choosing between technology options, making infrastructure decisions, establishing standards, migrating systems, or when user mentions ADR, architecture decision, technical decision record, or decision documentation.
Inspectional Reading
200lyndonkl/claude
Domain-neutral methodology for the first level of Adler-style reading - systematic skimming to determine what kind of document this is, what it's about as a whole, and whether deeper engagement is worth the time investment. Read title, metadata, table of contents or section headings, abstract or introduction, conclusion, and end-material at a glance. Classify document type (methodology, framework, tool, theoretical, reference, or hybrid). Decide whether to escalate to deeper reading. Reusable across any artifact-from-document workflow - paper extraction, skill creation from a methodology docum
Freqtrade
213TerminalSkills/skills
Freqtrade is a free, open-source crypto trading bot written in Python: you write a strategy class, download exchange candles, backtest it, then run it in dry-run mode (simulated orders) before risking money. Use when a user says "backtest a crypto strategy", "download historical candles for freqtrade", "write a freqtrade strategy", "run a trading bot in dry-run", or "set up FreqUI". Not financial advice: strategies usually lose money, and live trading can lose all of it. This skill defaults to dry-run and never handles exchange keys.
Kill Criteria Exit Ramps
200lyndonkl/claude
Establishes pre-defined, objective conditions for stopping projects and specific decision points for continue/pivot/kill evaluations. Guides through defining kill criteria, setting go/no-go gates, avoiding sunk cost fallacy, and executing disciplined stopping decisions. Use when defining stopping rules for projects, avoiding sunk cost fallacy, setting objective exit criteria, deciding whether to continue/pivot/kill initiatives, or when users mention kill criteria, exit ramps, stopping rules, go/no-go decisions, project termination, or sunk costs.
Browse the most popular Claude skills, all finance & crypto skills, or write your own with the skills generator.