from claude-code-plugins-plus-skills2,145
Step-by-step migration guide and tooling for moving translations from Crowdin/Phrase/POEditor into Lokalise, including transforms, uploads and validation.
This skill provides a practical, end-to-end migration workflow for moving translation data from other TMS platforms (Crowdin, Phrase, POEditor) into Lokalise. It covers export strategies, key/variable transforms, bulk uploads (CLI/API), conflict handling, and post-import validation.
Use during a replatforming or migration to Lokalise where you need reliable, repeatable steps to export source translations, normalize key naming and interpolation, and import with coverage validation and conflict reporting. Suitable for migrations of small to large key counts.
Designed for agent runtimes that can run shell/Node.js workflows and call external CLIs (lokalise2, curl, jq, node). Explicitly lists compatibility with claude-code and codex in frontmatter.
A Lokalise TMS migration guide covering export from Crowdin/Phrase/POEditor, key transformation, bulk upload via CLI/API, validation, and conflict handling. Well-structured with clear steps, error handling table, and examples. No bundled scripts — all code is inline in SKILL.md as bash snippets and a JS transform script. Niche audience (teams migrating translation platforms) but thorough for that use case.
No security concerns — all API calls use env vars for tokens, no hardcoded credentials, no suspicious network calls. The skill is purely instructional with code samples. Architecture is decent (clear steps, error table, examples) but everything is inline with no script separation. Usefulness is niche — only relevant during a TMS migration project, which is an infrequent task for most teams.
