Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →jeremylongshore/lokalise-migration-deep-dive
Execute major migration to Lokalise from other TMS platforms with data migration strategies.
Passed 11 of 22 test cases with the skill, and 8 of 22 without it.
and 2 more in the full report
3 fixed8 passed either way11 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
Our team is deprecating POEditor and transferring all our language strings to Lokalise. Please provide a migration guide and transformation script that downloads exported JSON files from POEditor, transforms double-brace variable syntax into single-brace format, creates the target project, uploads all language files with conflict handling, and outputs a summary of reviewed words and total key coverage per language.
| Checked | Without skill | With skill |
|---|---|---|
| Replaces double-curly braces {{variable}} with single-curly braces {variable} for POEditor variable normalization | Passed | Passed |
| Validates language word count using project statistics | Missed | Passed |
| Executes key transformation script via node runtime before pushing files to target project | Missed | Passed |
The instructions your model reads when the skill loads.
!lokalise2 --version 2>/dev/null || echo 'CLI not installed'
!npm list @lokalise/node-api 2>/dev/null | grep lokalise || echo 'SDK not installed'
!node --version 2>/dev/null || echo 'Node.js not available'
Migrate translations from another TMS (Crowdin, Phrase, POEditor) into Lokalise — export from the source platform, transform key names and variable syntax to match Lokalise conventions, bulk upload via API, validate translation coverage, and handle key conflicts with format-aware tooling.
LOKALISE_API_TOKEN environment variable set (read-write token)lokalise2 CLI or @lokalise/node-api SDK installedjq for JSON manipulation during transformationEach TMS has its own export format. Export to a Lokalise-compatible format when possible (JSON, XLIFF, or the platform's native format).
From Crowdin:
set -euo pipefail
# Export all translations as JSON (flat key-value structure)
# Use Crowdin CLI or API to download
curl -X POST "https://api.crowdin.com/api/v2/projects/${CROWDIN_PROJECT_ID}/translations/builds" \
-H "Authorization: Bearer ${CROWDIN_TOKEN}" \
-H "Content-Type: application/json" \
-d '{"targetLanguageIds": [], "exportApprovedOnly": false}'
# Download the build when ready (poll build status first)
curl -X GET "https://api.crowdin.com/api/v2/projects/${CROWDIN_PROJECT_ID}/translations/builds/${BUILD_ID}/download" \
-H "Authorization: Bearer ${CROWDIN_TOKEN}" -o crowdin-export.zip
test cases passed, vs 8 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.