Prioritize documentation translations

Decide whether and how to translate your developer docs

This skill helps you decide, one language at a time, whether translating your developer documentation is worth it. It uses traffic, browser-language and market evidence to pick languages, compares machine, LLM, human and community translation, and chooses which pages to translate first and which never. It also covers pinning each translation to a source commit, spotting outdated pages, fallbacks, naming an owner per language and retiring a locale. You get a locale plan for your team.