Glossary terms extraction

Translators meet a product's vocabulary one string at a time, with no way to tell which words are the product's own. A glossary is where a term gets decided once - translated one way everywhere, or not translated at all. This skill finds the terms worth deciding in the user's real content and adds them only after the user has reviewed them.

There is no target size. Mine for terms a translator would otherwise get wrong, and stop when the candidates get weaker: when you notice you are reaching for filler, say so and let the user choose between more material and stopping. A short, sharp glossary beats a long, padded one. A padded glossary gets ignored or deleted wholesale, taking its good entries with it, and a wrong entry teaches every translator the wrong answer. When in doubt, leave the term out.

Pick the path

How terms are read and written depends on what this session has:

• Crowdin connector tools - list_glossaries, add_term and the rest of the Crowdin MCP server, as in the assistant built into Crowdin or any assistant with the Crowdin connector. Read and write through them, and review in rounds: follow references/connector.md.
• A shell with the Crowdin CLI and a crowdin.yml, or a calling workflow that hands over a source catalog path (i18n-setup does). Draft a CSV, review it as a whole, and upload it with crowdin glossary upload: follow references/cli.md.

With both available, take the connector path unless the user or a calling workflow asked for the file. With neither, draft the reviewed list in the conversation and name both ways to add it.

Everything below holds on both paths.

Material to mine