What problem does it solve? After editing a multilingual RAG glossary, there is no guarantee that Polish or German queries actually expand to the intended English term or that both the Python and .NET retrieval servers picked up the change. This Skill provides a repeatable verification procedure that catches glossary drift, missing preprocessor registration, and over-broad term mappings before they silently degrade search quality. ## Core Features & Use Cases - Dual-server verification: Restarts both the Python (:3002) and .NET (:3001) HTTP servers and confirms each returns the expected canonical English document in its top-k results. - Drift and misconfiguration diagnosis: Checks that the canonical glossary and its .NET mirror are byte-identical, inspects container mounts and logs, and confirms the GlossaryExpansionPreprocessor is registered. - Regression checking: Runs the full multilingual eval slice (ML-pl-* / ML-de-* queries) to detect when a new entry breaks previously passing queries. - Use Case: After adding a Polish term like "refresh tokeny" to multilingual-glossary.yaml, run this Skill to confirm both servers return the IAM refresh token ADR as the top result and that no existing German queries regressed. ## Quick Start Verify that my new glossary entry expands the query "Jak są obsługiwane refresh tokeny w IAM?" to the expected English document on both RAG servers.